Remote Desktop Connection Refuses to work

[Curt]

I have setup many PCs with Remote Desktop Connection and only this that gives me problems. I have enabled it and assigned two users to be able to connect. Topology is very easy. All PCs are on a 3Com switch with no personal firewalls between with us. When I try to connect with PC with any Win XP Pro PC - It gives the standard error "The client could not connect to this computer. Remote connections might not be enabled or the computer might be too busy to accept new connections."

Some salient facts:
- All PCs in question are XP Pro
- No firewalls and Win XP firewall not activated
- The User names specified and part of Admin group and I tried User and Admin on that as well.
- I Unchecked and rechecked Remote Desktop in My Computer
- I Can ping the PC with no problem. Both by pc name and IP address.
- Have you made no modifications to Remote Desktop setup on target pc
- I Can use VNC with no problem

Are there any way to simply uninstall the service and reinstall or something similar?
How can I tell if the PC is works on the correct port?

Any help is welcome.

[Mel]

Try this on your PC on Command Prompt:
C:\ netstat -an |find "3389"
TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING

You should get the same result.

[Jason]

I get that result from my PC that works correctly but get no response to that command on the pc that isn't allowing connections via Remote Desktop Connection. I do netstat -an just to manually search the list and it's definitely not listening at 3389. Is there a way to restart the service or reinstall it?
Rebooting of my PC, give me no effect.

Thanks.

[Tod]

Try this Start > Run > services.msc and check the status of the "Terminal Services" service.
What's the startup type of its? Is it started or stopped?
This will helps you to find the service is currently running or not on your PC.

[Mel]

Thanks very much.
I was busy looking for a service titled Remote Desktop Connection that I didn't even think on Terminal Services. For some reason, the service was disabled not by user's. No group policy is defined on that.
Thanks again very much.

[justin]

Hi all!

I had the same problem, but I still need more help. Terminal Service on My PC is stopped, but when I try to start it, gives me an error message.
*** Could not start the Terminal Services service on Local Computer.
Error 1083:
The executable program that this service is configured to run in does not implement the service.

Can anybody tell me what I should check or maybe reinstall something.

Thanks

[Guest]

[Guest Morro]

Hey, why did not try terminal?
write in:
rdesktop --help

-----------------------------------------------------------------------------------------------
[root@RedHat root]# rdesktop --help
rdesktop: A Remote Desktop Protocol client.
Version 1.2.0. Copyright (C) 1999-2003 Matt Chapman.
See http://www.rdesktop.org/ for more information.

Usage: rdesktop [options] server[:port]
-u: user name
-d: domain
-s: shell
-c: working directory
-p: password (- to prompt)
-n: client hostname
-k: keyboard layout on terminal server (us,sv,gr,etc.)
-g: desktop geometry (WxH)
-f: full-screen mode
-b: force bitmap updates
-e: disable encryption (French TS)
-m: do not send motion events
-C: use private colour map
-K: keep window manager key bindings
-T: window title
-D: hide window manager decorations
--------------------------------------------------------------------------------------------

and you dont need to specify any port, just write example 192.168.0.1 and then it will connect....

[Guest]

[cdh4696]

First, I'm sorry about my bad English because I'm Korean.
I have the same problem which the first writer have. My PC is XP pro, No firewall, checked Remote Desktop, the user names specified, IE is operating well. Even my PC is listening port 3389, but it just doesn't work with the same error message!
Could you please help me?

[sah18]

I'm having the same problem on a Windows Server 2003 system. I tried the netstat command suggested and no listening is happening on 3389. I checked in Services, Terminal Services. It indicates that the service is started and is set to Manual. However, I wanted to stop it and start it again, but all the buttons are disabled (Start, Stop, etc). Any ideas why? What should I do to get the system listening again on 3389?
Thanks in advance!

[nooneyouknow]

I have been working through the unsuccessful Remote Desktop Connection issue for the last 6 hours and finally solved the problem. (At least on my system.) My problem system was running Windows Server 2003. I triple checked all my Remote Desktop Connection settings, verified the relevant services were running, and tried all of the ping tests with successful results. Everything was setup and should have been working perfectly but I still couldn’t connect to the system from any of the other systems on my network. I decided the next logical step would be to try and verify that the Remote Desktop Connection components were not corrupted. So on a whim I tried to connect to the problem computer with Remote Desktop Connection from the problem computer itself. (If you do this on a Windows Server 2003 System and the attempt is successful, your current Windows session show be uninterrupted. If you try this on a Windows XP machine however, and the attempt is successful, you will be logged out of your current windows session. Either way it should help in determining if the RDC components are valid and if your settings are correct.) I was able to successfully establish a Remote Desktop Connection. This was surprising to me. My thoughts then went to a firewall\port issue. In the Control Panel I went to the Windows Firewall and then the Exceptions Tab. For some reason the Remote Desktop Connection was unchecked. I checked it making Remote Desktop Connection an Exception to the Windows Firewall rules, click OK, and the problem was solved.

[deboasu]

Does anyone know why my router at work won't allow more than one person to connect remotely from home to their computer at work? Our network setup is as follows: broadband modem, linksys BEFW11S4 router, 16 port switch, with several XP Pro desktops. The home computers are also running XP Pro. The work router is set to allow port forwarding (3389) for the various IP addresses of our work computers, Windows firewall is set to allow remote desktop on both the work and home computers, but the router will only allow the first IP address on the port forwarding list to connect remotely. If a different person wants to connect to their personal work computer from home I have to change the order of the IP addresses in the router before they can connect, but once I do that, the other people can no longer connect. We use the following settings for remote desktop connection: Computer = router IP, Username = John Doe or whatever, Password = ???????, and the Domain = the computer name. Any help is appreciated.

[unashamed]

The problem is, routers will only allow 1 connection per port when using a feature like remote desktop.
What I do for my office is setup a port map.
I start at port 9000 ( can be any port in your case)
port 9000 outside maps to 3389 for pc1.
port 9001 outside maps to 3389 for pc2.
port 9002 outside maps to 3389 for pc3.
and so on and so forth.
works fine for me.

[krbuza]