Re: Remote desktop connection broken ERROR: "The client could not connect to the remote computer. ..."

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Sooner Al (SoonerAl_at_somewhere.net.invalid)
Date: 02/19/04 

Date: Thu, 19 Feb 2004 05:41:02 -0600

Is the desktop PC using a DHCP assigned IP on you home LAN? If it is and you rebooted the desktop
after the first test its possible the IP changed. I recommend using a static IP for your desktop on
your home LAN to preclude that problem.

Likewise, if your ISP assigns a DHCP IP to your router, its possible the IP changed when the lease
expired. In the case of the public IP changing, try using one of the dynamic DNS services that map
an alias to your ISPs assigned IP address.I use a free service from No-IP.com that maps an alias to
my ISPs DHCP assigned IP address. A small program runs on your PC and contacts the No-IP.com servers
on a periodic basis. The server then maps the IP of your PC to the alias and propagates that over
the public internet. It works very well for me and its FREE....

Go to http://www.no-ip.com for help. Additional like services, some FREE and some $$$$, can be found
on this page...

http://www.remotenetworktechnology.com/ow.asp?Remote%5FNetwork%5FHome%2FConnections

You would call the remote PC using the alias...Remote access also presumes you have TCP Port 3389
open on any firewall/NAT/router's between the public internet and your home LAN. 

-- 
    Al Jarvi (MS-MVP Windows Networking)
Please post *ALL* questions and replies to the news group for the mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no rights...
"a" <a@snm.com> wrote in message news:dl%Yb.3716$qO6.107397@news.uswest.net...
> I have two computers.  Remote Desktop Connection (RDC) worked yesterday from
> a campus PC to my home desktop computer (runs XP-PRO, call it #1PC)).  Today
> it is broken.  I tried RDC from my laptop (also running XP-PRO) both at
> school and at home (on my local LAN) with the following error:
> "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. Please try your connection again later. If the problem continues
> to occur, contact your administrator."
>
> The solutions offered in HELP and Support aren't much, really, actually.
>
> Cause:  The remote computer might not be set up to accept remote
> connections.
> Solution:  Try connecting to the remote computer at a later time. If you
> receive the same message, contact the server administrator.
> It's set up correctly, I double checked.
>
> Cause:  The remote computer might already have the maximum number of remote
> connections it is set up to accept.
> Solution:  Try connecting to the remote computer at a later time. If you
> receive the same message, contact the server administrator.
> No one else is trying to connect, promise.
>
> Cause:  Network problems might be preventing the connection.
> Solution:  Try connecting to the remote computer at a later time. If you
> receive the same message, contact the server administrator.
> Don't know what this (Network problems) could be, but inside the house, over
> the LAN, what could the deal breaker be?
>
> Remote Desktop is enabled (MyComputer -> Properties -> System Properties ->
> Remote -> Remote Desktop -> "Allow users to connect remotely to this
> computer"
>
> and
>
> The registry (Regedt32) is set up to accept incoming traffic at port 3389.
>
>
> HELP please.
> I don't know where else to look for anomalies
>
>

Relevant Pages

  • Re: Remote desktop Connection
    ... on the internet just not my remote desktop connection. ... The client could not connect to the remote computer. ... receive the same message, contact the server administrator. ... Network problems might be preventing the connection. ...
    (microsoft.public.windowsxp.help_and_support)
  • Remote desktop Connection
    ... I cannot connect with my job through my remote desktop connection. ... The client could not connect to the remote computer. ... receive the same message, contact the server administrator. ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: dis-connection problem
    ... > "Connected to remote computer. ... Verifying user name and password... ... > connection." ... away from open flames, naked flames and old flames; avoid inhaling fumes; ...
    (alt.os.windows-xp)
  • Re: SBS 2003 - Remote Connection Manager
    ... Did you run the RRAS wizard and enabled VPN? ... the server is SBS2003 and the Remote Computer is Windows XP SP2. ... > The Remote computer has an ADSL connection to the internet. ... >>> need to change the network settings for this connection. ...
    (microsoft.public.windows.server.sbs)
  • Re: Remote Desktop stopped working through firewall/router
    ... Is the PC using a dynamic or static IP on your home LAN? ... It works very well for me when I call my home network using Remote Desktop. ... with the router port forwarding or addressing of the router from the public internet. ... > Now I can make a Remote Desktop connection to the machine ...
    (microsoft.public.windowsxp.network_web)