Link to home
Start Free TrialLog in
Avatar of irishgx
irishgxFlag for United States of America

asked on

What is blocking Remote Desktop?

What is blocking me from connecting by Remote Desktop to my targeted LAN pc?

On the remote pc in system properties Remote Users are allowed to connect to the pc remotely, I am on the permissions list of Remote Desktop Users, Terminal Service is started, the firewall is off,  the reg entry fDenyTSConnections is set to 0, 2 settings in gpedit are allowing terminal services connections, the version of remote desktop are the same on both pc's.

I am able to remote back to my original pc, but not to the target pc.  What else is there that I can check?
Avatar of Fayaz
Fayaz
Flag of United Arab Emirates image

What error do you get?  Are you able to perform othere network operations like file share?  What is the back ground of this machine?
Teke a dump of netstat -an and see if the computer is listening on port 3389
Avatar of frankie_w
frankie_w

Some times the remote desktop option is "stuck" for various reasons. Disable the allow remote desktop on the target PC, hit apply and ok. Then enable it again. Double check the permission before you try remoting again. Its worth a try.
ASKER CERTIFIED SOLUTION
Avatar of Vaidas911
Vaidas911
Flag of Lithuania image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of irishgx

ASKER

The error is "This computer can't connect to the remote computer. Try connecting again, if the problem continues bla bla bla contact system adminstrator."

Port 3389 is listening, and open.  I am able to file share, just tested it.  The machine is Dell Optiplex 755 with XP Pro sp3 and on an AD Domain.  Nothing really special about it.

Going to test RDP by Lan, brb.

Avatar of irishgx

ASKER

It worked by LAN, so the problem lays in the routing of port TCP 3389 to the server.  How do I fix that?
You have to make sure that port TCP 3389 is forwarded via router (servers gateway) to interal terminal server IP.
You can use telnet utility from command line to make sure the port is open from internet. Syntax would be telnet <IP (external, if you try it from internet)> <port>, so telnet 213.23.244.21 3389.
If telnet screen shows error - you have to fix routing, if command propt screen goes blank - connection is OK.
Give me model of your router, maybe I could help you with exact directions how to configure it.
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Are you getting any event i.d like TERM DD 50?

Event Type: Error
Event Source: TermDD
Event ID: 50
Description:
The RDP protocol component "DATA ENCRYPTION" detected an error in the protocol stream and has disconnected the client.

Try this to resolve the issue.

http://support.microsoft.com/kb/323497

if not getting TERM DD 50

Try http://support.microsoft.com/kb/909444

Hope this will resolve the issue if still no go let us know.

Regards
Shahnawaz Ahmed
Avatar of irishgx

ASKER

I was able to telnet to the pc through port 3389, I then talked to my network admin who stated that "none of our switches are set to filter anything internally other than QOS."
Have you tried to connect from different computer? If telnet test pass and you can connect to RDC from local computer, the only problem left is your PC.
Avatar of irishgx

ASKER

I think I'm going to reimage it and see if ultimately that is the problem, which I didn't really want to do because I have countless PC's that have this problem on my campus lol.  DOH!  Anyways, points to you Vaidas, thanks a ton.
If you need any help debuging faulty workstation, I think it would be possible.
Avatar of irishgx

ASKER

I just did the cleanboot and I am able to remote into it YAY lol.
Avatar of irishgx

ASKER

I just figured out my problem and it was a stupid mistake lol.  I was using Faronics' Deep Freeze console to RDP to the workstations and apparently it is faulty.  Because I can remote with mstsc.exe without any issues.  Thanks for all the help.
Avatar of irishgx

ASKER

All of the solutions given weren't the fix to the problem, but it did reveal the root of the problem.