RDC No Longer Connects

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...b;EN-US;283673

Is Remote Desktop enabled on the target PC?

http://www.microsoft.com/windowsxp/p...op/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...

"B Means" <anonymous@discussions.microsoft.com> wrote in message
news:5b9101c3ad2a$d8597980$a601280a@phx.gbl...

> 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!

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.

>-----Original Message-----
>I started to experience the same thing here. A number of
>my users; myself included; started to have this trouble a
>few days ago. All machines are running XP pro with all of
>the latest service packs and updates.I have just updated
>all of these machines (the ones we are connecting to) to
>Office Professional Edition 2003. We have applied all
>patches and updates. It seems that the remote PC's loose
>the connection to the network. I can tell this by
>connecting to the servers and I see that the PC'c in
>question do not appear. Logging on to the computer
>locally reestablishes the connection to the network. As I
>say Office 2003 and windows XP updates are the only
>changes on my network. Is anyone else having this
>problem, and is there a fix?

>US;283673

>le/remotedesktop/default.asp

>group for the mutual benefit of all of us...

>confers no rights...

>message

>to

>the

>connections...".

>the

>router

>have

>am

>that

>everything

>.
>

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)
winxp@longhornconsulting.com

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

On Tue, 18 Nov 2003 10:27:57 -0800, "Ken Claggett"
<kenc@syzygycorp.com> wrote:

>
>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.
>

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


"Jeffrey Randow (MVP)" <winxp@longhornconsulting.com> wrote in message
news:qm9orv8c6l1vcuthte586chtmnhcugh51b@4ax.com...

> 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)
> winxp@longhornconsulting.com
>
> 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
>
> On Tue, 18 Nov 2003 10:27:57 -0800, "Ken Claggett"
> <kenc@syzygycorp.com> wrote:
>

>