Why doesn't Remote Desktop Connection respond until after a reboot?
I use Remote Desktop Connection to access a number of PCs in an office, all of which are on a domain. For some odd reason, the two newest PCs, both Dells, have an issue I can't figure out.
When I attempt to remote into these PCs, RDC tries to connect, but does nothing. It almost seems like it refreshes, taking about three seconds before the "Connect" button becomes available again. I get no error message, it just seems like it tries once, then does nothing.
If I can have the user sitting at that machine reboot, then I can connect properly, but I'm wondering why this might be occurring, and why it only happens on the two newest machines, both Dells, less than two months old. All the PCs are running XP Pro w/ SP3.
Any suggestions will be greatly appreciated!
When I attempt to remote into these PCs, RDC tries to connect, but does nothing. It almost seems like it refreshes, taking about three seconds before the "Connect" button becomes available again. I get no error message, it just seems like it tries once, then does nothing.
If I can have the user sitting at that machine reboot, then I can connect properly, but I'm wondering why this might be occurring, and why it only happens on the two newest machines, both Dells, less than two months old. All the PCs are running XP Pro w/ SP3.
Any suggestions will be greatly appreciated!
johnb6767
Seems like the service is failing perhaps..... Have you checked the logs for anything related to the Terminal Services service?
ASKER
Not yet... What should I be looking for, and in which log would this be present?
Another thing you can try checking are the power options for these new computers. Perhaps the computer is going into a mode that is causing you to not be able to remote to it....such as the hard drive is powering down, or the system is hibernating. Check to see if the power schemes are set up the same for these two new computers as they are for the others.
Good Luck!
Good Luck!
System Log...... Under the source "TermServ, or Service Control Manager". Might reference the service failing, with an error code....
Can you telnet to the machine on the RDP port when this happens?
start>run>cmd
telnet PCNAME 3389
Can you telnet to the machine on the RDP port when this happens?
start>run>cmd
telnet PCNAME 3389
ASKER
johnb6767: I'm using RDC with custom ports for each machine. For example, one of the machines is using port 3336 for the connection. If I attempt a connection from outside their network, would I telnet to the machine using the external IP address and port?
telnet xxx.xxx.xxx.xxx 3336
Thanks for the help thus far...
telnet xxx.xxx.xxx.xxx 3336
Thanks for the help thus far...
yes....
Try internal first, to rule out any port forwarding problems.....
Try internal first, to rule out any port forwarding problems.....
ASKER
Ok, I'll give that a shot and let you know how it works out...
ASKER
OK, I tried to telnet into the machine both internal on their network and externally, and both were able to telnet in (I think) as the cmd screen goes completely black. RDC does not connect to this machine at the moment, it does the refresh thing, where it acts like it wants to connect for about two seconds, then the "connect" button becomes active again.
Ok, go to Computer Management, and Click up top to Connect to a remote computer.... Connect to this machine, before you try and connect....Check for the Terminal Servces service...Once it fails to connect, refresh the Services, and see if it is now stopped.....
And are you using the latest RDP client?
Remote Desktop Connection (Terminal Services Client 6.0)
http://support.microsoft.com/kb/925876
And are you using the latest RDP client?
Remote Desktop Connection (Terminal Services Client 6.0)
http://support.microsoft.com/kb/925876
ASKER
johnb6767:
All the machines are running SP3, so the latest version including TSC 6.0 won't install, as it indicates the Service Pack is newer than that hot fix.
Also, I'm confused about where I'm checking for the Terminal Services service, is that on the local machine on which I'm trying to connect to the problem machines? If so, I can connect to a number of other machines on that same remote domain, just not those two new Dells that require a restart.
I hope this helps to diagnose this issue and I appreciate the help.
All the machines are running SP3, so the latest version including TSC 6.0 won't install, as it indicates the Service Pack is newer than that hot fix.
Also, I'm confused about where I'm checking for the Terminal Services service, is that on the local machine on which I'm trying to connect to the problem machines? If so, I can connect to a number of other machines on that same remote domain, just not those two new Dells that require a restart.
I hope this helps to diagnose this issue and I appreciate the help.
Remote machine for that service.....Curious to see if it dies once the RDP window closes on your end....
ASKER
I'll check and let you know.
Any other ideas why this issue only happens on the two newest machines, both Dells?
Any other ideas why this issue only happens on the two newest machines, both Dells?
OEMs are NOTORIOUS for bundling all kind of CRAPWARE...... Did you drop your own image on them?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.