Is there anything wrong with mstsc?

Hi All,

I have a customer set up to remotely log into his
Windows 7 Pro computer with MSTSC.exe (M$ Terminal
Service Connector) from his Windows 10 Pro laptop.

Problem: when he tries to log in, he gets a black
screen. It takes several attempt to get it.

He seems to have no issue logging in with wfreerdp,
but tell me he can't run Quickbooks with it.

I have no issues whatsoever logging in with xfreerdp
(Fedora Linux 29).

Is there something wrong with mstsc.exe in Windows 10?
Any fixes?


Many thanks,
-T

On 13/03/2019 00:30, T wrote:
Hi All,

I have a customer set up

you are a rogue trader so just **** off from here. We can't help you
defrauding customers who won't know that you are a convicted fraudster
who should be locked up forever.







--
With over 950 million devices now running Windows 10, customer
satisfaction is higher than any previous version of windows.

On 3/12/19 5:30 PM, T wrote:
Hi All,

I have a customer set up to remotely log into his
Windows 7 Pro computer with MSTSC.exe (M$ Terminal
Service Connector) from his Windows 10 Pro laptop.

Problem: when he tries to log in, he gets a black
screen.Â* It takes several attempt to get it.

He seems to have no issue logging in with wfreerdp,
but tell me he can't run Quickbooks with it.

I have no issues whatsoever logging in with xfreerdp
(Fedora Linux 29).

Is there something wrong with mstsc.exe in Windows 10?
Any fixes?


Many thanks,
-T

I logged into the client computer and gave it a speed check
with speedof.me. Seems a little spotty. He is using his
iPhone 3G hot spot. I had him change to his wife's iPhone
4G hot spot. Got a lot better. wfreerdp is working
perfectly now too.

Seems this is an Internet connection issue. Verizon's 3G
got so bad around these parts that I had to get a new
cell phone. Verizon is no longer maintaining 3G equipment
around these parts as they are upgrading all their towers
to 4G. But the customer is on AT&T. Maybe them too ...

T wrote:
Hi All,

I have a customer set up to remotely log into his
Windows 7 Pro computer with MSTSC.exe (M$ Terminal
Service Connector) from his Windows 10 Pro laptop.

Problem: when he tries to log in, he gets a black
screen. It takes several attempt to get it.

He seems to have no issue logging in with wfreerdp,
but tell me he can't run Quickbooks with it.

I have no issues whatsoever logging in with xfreerdp
(Fedora Linux 29).

Is there something wrong with mstsc.exe in Windows 10?
Any fixes?


Many thanks,
-T

Working normally here.

Win10 17134 (barely in support video) -- Win7 SP1 supported video card (Geforce10 series)
Win10 17763 (barely in support video) -- Win7 SP1 supported video card (Geforce10 series)

Both worked fine. Win10 complained
about "certificates" it was offered by
the Win7 Sp1 machine, but that's understandably
due to the patch level of the Win7 setup.

It helps for the session to be "up" on the Win7 machine,
with user account logged in, versus other possible states.
I noticed some performance anomalies in other states,
when the connection was made.

I expect you know all these curve balls by now.

For anyone playing along at home, on the Win7 box you
go to System control panel, and there is a remote item
on the left. I expect when you "enable" it, it also
tells the Firewall to enable two items to allow the
connection to be made. When you switch off from
the System Control Panel, the Firewall items are
closed too.

Paul

In article , wrote:

Seems this is an Internet connection issue. Verizon's 3G
got so bad around these parts that I had to get a new
cell phone. Verizon is no longer maintaining 3G equipment
around these parts as they are upgrading all their towers
to 4G. But the customer is on AT&T. Maybe them too ...

you're out of date. verizon upgraded their network to lte long ago and
now starting to upgrade it to 5g. cdma continues to work as it always
has (and in some cases, it is still required) but it will be shuttered
by year's end. at that point, old cdma-only phones will no longer work
and anything that doesn't support volte won't work for voice (but will
for data).

at&t shuttered 2g two years ago and continues to support 3g hspa,
however, they are calling their advanced lte network 5g, which is
simply false, and they are being sued because of that.

On 3/12/19 9:13 PM, Paul wrote:
T wrote:
Hi All,

I have a customer set up to remotely log into his
Windows 7 Pro computer with MSTSC.exe (M$ Terminal
Service Connector) from his Windows 10 Pro laptop.

Problem: when he tries to log in, he gets a black
screen.Â* It takes several attempt to get it.

He seems to have no issue logging in with wfreerdp,
but tell me he can't run Quickbooks with it.

I have no issues whatsoever logging in with xfreerdp
(Fedora Linux 29).

Is there something wrong with mstsc.exe in Windows 10?
Any fixes?


Many thanks,
-T

Working normally here.

Win10 17134 (barely in support video) -- Win7 SP1 supported video card
(Geforce10 series)
Win10 17763 (barely in support video) -- Win7 SP1 supported video card
(Geforce10 series)

Both worked fine. Win10 complained
about "certificates" it was offered by
the Win7 Sp1 machine, but that's understandably
due to the patch level of the Win7 setup.

It helps for the session to be "up" on the Win7 machine,
with user account logged in, versus other possible states.
I noticed some performance anomalies in other states,
when the connection was made.

I expect you know all these curve balls by now.

For anyone playing along at home, on the Win7 box you
go to System control panel, and there is a remote item
on the left. I expect when you "enable" it, it also
tells the Firewall to enable two items to allow the
connection to be made. When you switch off from
the System Control Panel, the Firewall items are
closed too.

Â*Â* Paul



Thank you for the verification! I am certain it is a poor 3G
connection.

Anyone what to know how to set this up, I have an extensive howto
I will share. Ping me int he subject line

On 3/12/19 5:30 PM, T wrote:
HeÂ*seemsÂ*toÂ*haveÂ*noÂ*issueÂ*loggingÂ*inÂ*with *wfreerdp

Well, it can only scale to 2/3 of his local screen size,
meaning larger fonts. An he likes that. He does not
have to wear glasses!