RDT Doesn't Work

[Walt]

I can't get remote desktop to work. My configuration is
as follows:

Server -
WinXP Pro connected to Ethernet Hub which is hooked to
DSL Modem (Verizon).

Client -
WinXP Pro connected with wireless 802.11b Wi-Fi to access
point, connected to Ethernet Hub (same as server).

I want to use my laptop anywhere in the house and access
my primary machine in my office.

I have set up both the server with Remote Desktop and
have enabled VPN. I have told the firewalls on both
machines (ZoneAlarm Pro) to accept connections and to act
as a server.

I use the IP address assigned by Verizon to access the
server. When I attempt to connect, I get the following
message:

"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 connecting again later. If the problem
continues to occur, contact your administrator."

Since I am the administrator, I can't help, because I
don't have a clue. I looked through about ten pages of
the newsgroup and could not find a match to my problem.

Any ideas? Or can anyone can help?

Thanks in advance,
Walt

 

[Andre]

Walt,
I have a similar problem and have uninstalled ZAPro but still get
the same problems.

Please let us know your solutions

Tks
Andre

 

[Walt]

Sooner Al,
I turned off ZoneAlarm Pro on both machines and attempted
to connect. I got the same message.

Anymore ideas anyone?
Walt

 

[Sooner Al]

Hmmm...
Are you sure that Remote Desktop is enabled on the target
PC? Run the 'netstat -a' command and make sure there is
an entry for TCP Port 3389 LISTENING...
Are you sure your calling the correct IP?
Can you test this from another remote PC, ie. get a
friend call using RD?

I suppose its possible your ISP is blocking TCP Port 3389.

Al

 

[Walt]

Sooner Al,
I am not sure what I did, but I finally got it to work. I
checked the 3389 and it showed Listening. However, I
decided to ping the server (don't know why I hadn't tried
this before) and got nothing. So I quit ZoneAlarm and got
it to ping. Then I tried remote connection again and got
it to work.

This isolated it to ZoneAlarm. I don't know why it didn't
work last night with I was not using ZoneAlarm... Anyway,
it seems I can use ZoneAlarm at the medium setting and
get through. I'm now going out to ZoneLabs to see if
there is something I can do to get RDT to work at the
high setting.

Thanks for all your help. Also, I hope Andre has been
reading this and found a solution for his machine.

Walt

Original Message

Are you sure that Remote Desktop is enabled on the target

 

[Sooner Al]

Good news...Thanks for the feedback...

 

[Jeffrey Randow (MVP)]

Double check the configuration of your network card to see if the
Microsoft Internet Connection Firewall may also be enabled. If so,
either disable (not recommended) or configure it to support Remote
Desktop.

I wouldn't necessarily recommend a VPN in your case since I am
assuming that you are getting assigned a second public IP address in
the same network as the server. Thus, routing tables will get a bit
complicated...

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