RDC No Longer Connects

  • Thread starter Thread starter B Means
  • Start date Start date
B

B Means

I have been using RDC to connect to my home machine for
several months with no problem. Suddenly, when I try to
connect I get the generic "Cannot connect to the remote
computer. Remote connections might not be enabled or the
computer might be too busy to accept new connections...".

To my knowledge, nothing has changed on either side of the
equation. My home PC is behind a linksys (befw11s4) router
with all appropriate ports enabled and forwarded. I have
verified my external ip address has not changed, but I am
unable to ping this address.

The only thing that I can think of is a power outage that
occured the weekend prior to my having problems. I
rebooted the router, pc and modem to ensure that everything
was synched up.

Any ideas?

Thanks!
 
Any chance the XP ICF is enabled?

http://support.microsoft.com/default.aspx?scid=kb;EN-US;283673

Is Remote Desktop enabled on the target PC?

http://www.microsoft.com/windowsxp/pro/using/howto/gomobile/remotedesktop/default.asp

Are you calling the correct IP?

--
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...
 
I have the same symptom, only maybe worse. Have two XP
boxes on a local net - I can ping both ways. ICF off and
Remote Desktop Sever enabled as described below. Used to
be I could connect both ways just fine. But now, when I
try to conect Machine B as a client to Machine A, I get
the "Cannot connect" message as described below. Same
thing if I try to connect to Machine A with any other
machine as a client. (However, I can connect fine to
Machine B) So both machines are set up identically, but I
cannot connect to Machine A. Trouble is, Machine A is the
one I want to use as the RDC server. Any ideas would be
greatly appreciated.
 
Try running "telnet ipaddress 3389" from computer B to computer A.
What happens? Do you get a timeout error or does the screen clear?

If you get a timeout error - there is a TCP/IP or network problem
between the two computers. Refer to the following KB article
(http://go.msmvps.com/l.aspx?linkid=108) to diagnose TCP/IP problems
between computers.
(Also

http://go.msmvps.com/l.aspx?linkid=107)

Jeffrey Randow (Windows MVP - Networking & Smart Display)
(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 Wiki -
http://www.remotenetworktechnology.com
Smart Display Support - http://www.smartdisplays.net
Windows XP Expert Zone - http://www.microsoft.com/windowsxp/expertzone
 
Hi,

I had a similar problem: no way to connect to remote desktop.

Two possible problems
1) "server" (= remote computer) refuses loging because another session etc:
logon with admin-privilieged user, start task manager and logoff blocked
session (not very nice for user who looses current stuff not yet saved, do
save often), then user can relog.
2) could not connect with *any* user from XP session: reworked after
rebooting "client" computer, or when trying with win2K terminal service
client (fro another computer running win2k)

hope this helps

regards
 
Back
Top