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 17:11:02 -0600

Well, I suppose its possible that your school is blocking TCP Port 3389 outbound. You would need to
contact the local network administrators about that .One way to test the router is to do this telnet
test using the IP of the router. You need to test this from a remote location or dial into the
internet using a laptop, etc.

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q187628

The bottom line though, is if you can not connect over your home LAN then its also possible Remote
Desktop is not enabled on the PC. Have you checked to see if RD is actually listening on TCP Port
3389 on the host PC? On the host XP Pro machine go to "Start -> Run", type 'cmd' (without the
quotes). At the command line type the command 'netstat -a' (without the quotes). Look for a line
like this.

TCP <Your PC>:3389 <Your PC>:0 LISTENING

For example on my XP Pro desktop, Ashtabula, the line looks like this using the default port 3389.

TCP ashtabula:3389 ashtabula:0 LISTENING

The line should be present...If the Remote Desktop host is not running, then you will not see a line
like that and you will not be able to connect. If you run services.msc on the target machine is the
"Terminal Services" service started? Also, check the Event log to see if anything stands out when
you try to connect. 

-- 
    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:Yy5Zb.38$xq6.38630@news.uswest.net...
> Thanks Al
> Well,
> yes my home pc uses an internally assigned IP from (via DHCP on the
> actiontec 1520 router) and my ISP has changed my external IP in the past
> (rarely).
> This, unfortunately, isn't the problem.
>   At home, I confirmed the internal IP on each pc and I even checked the
> router's table port forwarding, and it was all good.
>   From campus, I called my roommates, and they confirmed I was using the
> correct IP.
> Therefore, I'm certain I have the correct IP in each situation.
> I don't know if it matters, but with this error, the RDC client fails
> immediately, seemingly without ever even looking for the remote computer to
> connect to.
> Does that help anyone out there?  Has anyone else even had this problem?
> TIA
>
>
> "Sooner Al" <SoonerAl@somewhere.net.invalid> wrote in message
> news:eHacB1t9DHA.1648@tk2msftngp13.phx.gbl...
> > 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: how to enable XP ICF non administrative account
    ... Computer Configuration, Administrative Templates, Network, Network Connections ... > they could easily switch on and off the ICF when depending ... > give administrator privileges to them. ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Remote Desktop doesnt connect online ...
    ... The remote computer is set up to accept remote connections ... The remote computer does not have exceeded the maximum number of remote ... It is also possible that network problems are preventing your ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: xp pro and home compatibility?
    ... you definitely want the printer hooked up to an XP Pro. ... We run a 9 system pier to pier network. ... "No more connections can be made to this remote computer at this ...
    (microsoft.public.windows.server.networking)
  • Re: remote access
    ... The client could not connect to the remote computer. ... connections might not be enabled or the computer might be too busy to accept ... It is alos possible that network problems are preventing ...
    (microsoft.public.windows.server.sbs)
  • Re: Remote desktop stopped working
    ... >> Can you test this over the local LAN at the remote site to see if RD works? ... > there was network problems at the client. ... >>> The client could not establish a connection to the remote computer. ... >>> 1) Remote connections maybe isn't activated on the remote computer. ...
    (microsoft.public.windowsxp.work_remotely)