RDC Connection Trouble

  • Thread starter Thread starter Wilhelm Damsleth
  • Start date Start date
W

Wilhelm Damsleth

Hello from ice-cold Norway!

I'm having trouble connecting to my WinXP Pro computer from any other
computer (I've tried from a Mac and a Win2000 PC).

I get this error message: "The client could not connect to the remote
computer.

Remote connections might not be enabled or the computer might be too
busy to accept new connections. It is also possible that network
problems are preventing your connection."

The funny thing here is that it actually used to work a few weeks ago
(this is not a problem with a dynamic IP's). The target computer is
actually NOT listening on the RDC port (I haven't changed the port number).

And yes, Remote Desktop is checked in the Remote pane of the System
Properties-dialog.

All patches have been applied to the WinXP computer. There IS firewall
software running on it, but I have disabled it. All computers are on the
same network.

The Routing and Remote Access Service has been failing a few times, but
that is not happening any more.

Any help is greatly appreciated.

Thanks.
 
Are you behind a router? If so, has the private IP address of your
computer changed? This happens to people who are using DHCP to assign
addresses to computer behind a router..

Jeffrey Randow (Windows Net. & Smart Display MVP)
(e-mail address removed)

Please post all responses to the newsgroups for the benefit
of all USENET users. Messages sent via email may or may not
be answered depending on time availability....

Remote Networking Technology Support Site -
http://www.remotenetworktechnology.com
Smart Display Support - http://www.smartdisplays.net
Windows XP Expert Zone - http://www.microsoft.com/windowsxp/expertzone
 
Im not behind a router and im getting the same problem, also i couldnt find the terminal services folders on XP.
 
When I did these test, I did them "behind" the NAT router. All computers
have static IP's, and, just to be sure, I checked it, and it remained
the same.

I DID manage to get it working now, because I noticed that the "Terminal
Services" Service had been Disabled. I don't have any idea as to how
this has happened (I'm quite sure that I haven't disabled it ;-), but
anyway, setting it to Automatic launch has cured the bug (for now).

Thanks to all of you for your help!

- Wilhelm
 
If you aren't behind a router, you need to use your public IP address
and make sure you open TCP Port 3389 in your firewall.

Jeffrey Randow (Windows Net. & Smart Display MVP)
(e-mail address removed)

Please post all responses to the newsgroups for the benefit
of all USENET users. Messages sent via email may or may not
be answered depending on time availability....

Remote Networking Technology Support Site -
http://www.remotenetworktechnology.com
Smart Display Support - http://www.smartdisplays.net
Windows XP Expert Zone - http://www.microsoft.com/windowsxp/expertzone
 
Back
Top