appresco
asked on
Remote Desktop trouble
I have XP Pro at work and win 2000 at home. Remote Desktop has been working fine for a long time. After installing SP2 at work, remote desktop works OK over the LAN at work from another workstation, but from home I get. "The client could not connect ..."
I have turned off the firewall at work since the Interenet connection there is on a router which has port 3389 open. I have checked all the settings and everthing looks as it did before installing SP2.
As a last resort I un-installed SP2 today. SP1 seems to run faster, but still no luck on the remote connection from home. I can also successfully ping the work computer from home. Remote desktop still works fine over the LAN.
Any other ideas on something to check?
I have turned off the firewall at work since the Interenet connection there is on a router which has port 3389 open. I have checked all the settings and everthing looks as it did before installing SP2.
As a last resort I un-installed SP2 today. SP1 seems to run faster, but still no luck on the remote connection from home. I can also successfully ping the work computer from home. Remote desktop still works fine over the LAN.
Any other ideas on something to check?
Check the Windows Firewall to ensure that the remote desktop is enabled. The firewall is turned on by default with SP2 and uninstalling SP2 probably doesnt disable it.
ASKER
Checked that. Remote Desktop is/was enabled under SP2 and before and firewall was turned off in both cases anyway.
Can you ping the machine remotely?
ASKER
Yes, I can successfully ping the machine that I am trying to connect to. It responds in .3 sec.
Can you telnet to the machine using port 3389?
ASKER
Don't know much about telnet. If I put "telnet:xxx.xxx....." into my browser address field I get a DOS window for telnet.exe that shows an interface into my Intel Express 8220 Router. I don't know how to test for 3389 explicitly.
If I put "telnet:xxx.xxx.xxx.xxx:33 89" into my browser address field I get another DOS telnet.exe window that says "connnecting ..." for a few seconds and then goes away.
My ISP opened 3389 a couple of years ago and remote desktop has been working since then up until this problem.
If I put "telnet:xxx.xxx.xxx.xxx:33
My ISP opened 3389 a couple of years ago and remote desktop has been working since then up until this problem.
open a dos window, from the dos prompt type:
telnet ipaddressofmachine 3389
If you cannot connect then something is blocking that port. Odds are something changed and that port is now blocked.
telnet ipaddressofmachine 3389
If you cannot connect then something is blocking that port. Odds are something changed and that port is now blocked.
ASKER
"Connect failed" on telnet so installing SP2 closed port 3389? That's scary. I have a support ticket into my ISP for them to check it. I don't think I can re-open it since I do not have a password for the router; it belongs to the ISP.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
SP2 install should be smart enough to know that I want SP2 to act like SP1, but that doesn't matter now.
My ISP has checked 3389 and it is OK; it is exactly the same as before SP2. And like I've said above, the Windows firewall is turned off, so I am assuming that it cannot be causing the problem. I guess I'll re-install XP. Thanks for trying.
My ISP has checked 3389 and it is OK; it is exactly the same as before SP2. And like I've said above, the Windows firewall is turned off, so I am assuming that it cannot be causing the problem. I guess I'll re-install XP. Thanks for trying.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
It may be a version compatibilty issue with your client exe... You can try this one as it solved a similar problem I had a while back following an update that left me without Terminal Server access...
http://www.microsoft.com/windowsxp/downloads/tools/rdclientdl.mspx
http://www.microsoft.com/windowsxp/downloads/tools/rdclientdl.mspx
ASKER
What happened was that the SP2 upgrade changed the network settings to dynamically select an IP. As it turned out, I needed specific DNS addresses from my ISP as well, so the IP wasn't the only problem, but Brainded got me on the right track. I split the points and gave Kerry 100 for a good effort.