User cannot connect to Terminal Server

[eric_d_green]

I have a person who is unable to connect to a Terminal Server outside
of the LAN. By cannot connect I mean she clicks on the RDP file and
when it tries to connect the top bar with the ip address and
minimize/maximize/close options comes up but the logon screen does not
appear. After a minute or so an error message comes back and says: The
connection to the remote computer was broken.


I try had her try to connect to a server on the LAN and it works just
fine.

I then logged in as two different users with the same permissions level
as her and tried connecting to the Terminal Server outside of the LAN
and it connected immediately.

*Please note that I never receive the Terminal Server Logon Screen on
the server outside of the LAN so it is not a user permissions problem
for that user on the Terminal Server.

It is almost as if the profile on the local computer is corrupt for
that user; does anyone know what file it may be looking at within the
users profile that could have become corrupt and is no longer allowing
the connection. I was about to blow out her profile but wanted to see
if there was an alternative.

Thanks.

 

[Pegasus \(MVP\)]

I have a person who is unable to connect to a Terminal Server outside
of the LAN. By cannot connect I mean she clicks on the RDP file and
when it tries to connect the top bar with the ip address and
minimize/maximize/close options comes up but the logon screen does not
appear. After a minute or so an error message comes back and says: The
connection to the remote computer was broken.


I try had her try to connect to a server on the LAN and it works just
fine.

I then logged in as two different users with the same permissions level
as her and tried connecting to the Terminal Server outside of the LAN
and it connected immediately.

*Please note that I never receive the Terminal Server Logon Screen on
the server outside of the LAN so it is not a user permissions problem
for that user on the Terminal Server.

It is almost as if the profile on the local computer is corrupt for
that user; does anyone know what file it may be looking at within the
users profile that could have become corrupt and is no longer allowing
the connection. I was about to blow out her profile but wanted to see
if there was an alternative.

Thanks.

It seems you are comparing apples with pears in your test,
using one .rdp profile file in one case and a different file in
the other case. You should use neither while testing - run
this command instead in each case:

mstsc /v:YourServerortNumber

The PortNumber is by default 3389.

 

[eric_d_green]

The RDP file was in the all user/desktop so it was apples to apples.
Also I had tried it through the run command... same results.