Re: Remote connection error after reboot

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Robin Walker (rdhw_at_cam.ac.uk)
Date: 09/29/04 

Date: Wed, 29 Sep 2004 16:52:38 +0100

"Triatron" <Triatron@discussions.microsoft.com> wrote in message
news:932E45C3-04F7-4411-BA9F-80D2DEA9114E@microsoft.com...
>
>I am recieveing the 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 the network problems are
> preventing your connection.
>
> Please try connecting again later. If the problem continues to occur,
> contact your administrator.
>
> This is happening on a XP Prof laptop trying to connect to a XP Prof
> desktop. After a reboot and the desktop is not logged into is when the
> message happens.
>
> If I log in to the desktop and then try it works fine.

Try updating the video driver on the RDP server: i.e. the PC you are trying
to connect to, rather than the one you are connecting from. 

-- 
Robin Walker
rdhw@cam.ac.uk

Relevant Pages

  • Re: Event ID: 1004
    ... might not be enabled at the remote computer. ... maxium number of connections was exceeded at the remote ... note, we have enough licenses. ... >The client runs XP Home, and needs a purchased TS CAL. ...
    (microsoft.public.win2000.termserv.clients)
  • Re: Remote desktop connection broken ERROR: "The client could not connect to the remote compute
    ... seemingly without ever even looking for the remote computer to ... >>> connections. ... It is also possible that network problems are preventing ... contact the server administrator. ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: Remote Desktop Web Connection
    ... You have connection problems only over the WAN? ... The client could not connect to the remote computer. ... connections might not be enable or the computer might be too busy to ...
    (microsoft.public.windows.terminal_services)
  • The client could not connect to the remote computer
    ... "The client could not connect to the remote computer. ... might be too busy to accept new connections. ... It is also possible that network problems are preventing ...
    (microsoft.public.win2000.termserv.clients)
  • Re: Event ID: 1004
    ... client ping the TS? ... MCSE, CCEA, Microsoft MVP - Terminal Server ... > might not be enabled at the remote computer. ... > maxium number of connections was exceeded at the remote ...
    (microsoft.public.win2000.termserv.clients)