Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Remote Desktop Disconnected 1

Status
Not open for further replies.

vich

Technical User
Sep 26, 2000
107
US
I have read many posts on this topic and still can't seem to solve the problem.

I have a computer runnigng XP Pro SP2 that I used to be able to RDP to just fine. Now I get the message "This computer can't connect to the remote computer. Try connecting again. iF the problem continues, contact the owner ot the remote computer or your network administrator". I have checked;
Control Panel\System\Remote and remote desktop is enabled( it is grayed out but enabled. Other computers on my network are grayed out as well but I can RDP them).
I checked the Windows firewall and RDP is listed as an allowed exception.


I am under the gun to get this working any help is appreciated. I have read many posts and looked at those suggestions to no avail.

Sorry to post another question about a similiar topic. Just feel like I could use some more pointed help if someone has the time.
 
See whats in the Select Remote users option. Probably should be empty or at the very least have your credentials in there.
 
it is empty and I am also set up on the machine as an administrator but even the actual machine normal user can not access with RDP anymore.
 
I checked the "allow Users to connect remotely..." setting and it is set to "not Configured"

This is just a workstation running XP Pro SP2. Not a server.
 
Anybody got any other suggestion?
Would really appreciate it.
 
Sometimes when Remote Desktop dies it remains that way until you reinstall the operating system.

Are there any hidden firewall components included in any other security products that you have installed, or in any Nvidia Network Adapters? Try a clean boot and see if you can get through.

310353 - How to Perform a Clean Boot in Windows XP

316434 - HOW TO: Perform Advanced Clean-Boot Troubleshooting in Windows XP

310560 - How to Troubleshoot By Using the Msconfig Utility in Windows XP



How to reset security settings back to the defaults

Run the System File Checker program from the Run Box by typing.....Sfc /Scannow in it and have your XP CD handy.

If they don't work you could try repairing windows by running it over itself. You will lose all your windows updates but your files will be untouched.

How to Perform an In-Place Upgrade (Reinstallation) of Windows XP (Q315341)
 
Thanks, I'll try these, the idea of having to reload is not appealing. But that may be all that I have. My challenge is that I am not sure where the OEM disk is and I belive it was upgraded from Home to PRO somewhere along in it's life.

I tried booting in safe mode - no luck

I tried the System File Checker but it didn't like the Windows XP Pro Disk I was using.

Thanks for all of the suggestions.
 
Have they recently added a router? How do they connect to the Internet cable? adsl?
 
I get the same message whether I try to connect through the VPN or if I am in the office on the LAN locally. I can connect to other machines either locally or via the VPN.

I can ping the machine.
 
What computer and at which location are you trying to remotely connect to? Can your problem machine make a Remote Desktop connection to any other machine at all?

This thread mentions Port Forwarding via any Router involved (at the other end). Is this a possible problem?

remote desktop
thread779-1114681
 
When you go to services.msc what is the status of the terminal service?
Have you tried to RDP by the stations IP address rather than computer name?
What is the output of netstat -a
Does it show the compuiter listening on port 3389?
 
I can RDP to other machines, our Windows Server 2003 and other desktops running XP Pro.

I have tried the IP address, same results.

Terminal Services is started.

I see it listening on 3390 but not 3389
 
The port number change solved the problem.
Many, Many THANKS to everyone who responded and help me resolve this problem.

tlscousin your responses helped me avoid doing a operating system reload. THANKS!!! Have a Star!!!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top