Accessing PCs via Remote Desktop from different location??

[Guest]

Area-1 has a wireless network consisting of 3 PCs running XP Pro (SP1), DSL Modem connected to LinkSys Router, LinkSys Network cards, LinkSys Access Point. All PCs are relatively new and has 1 GB of RAM

Area-2 has a wireless network 2 PCs running XP Pro (SP1), DSL Modem connected LinkSys Router, LinkSys Network card

Remote Desktop works great in Area-1 (same loc/bldg). All PCs can access each other with no problems via Remote Desktop

Area-2 is 45 miles away from Area-1. Port forwarding has been enabled on Area-1 Routers to 3389 and PCs are configured for Remote Desktop access.

Remote Desktop access from Area-2 FAILS!!!. Error msg "Computer busy...etc". Worked with MS Support for couple of weeks on this problem - problem still unresolved. MS support claims that XP Remote desktop has problems functioning over such distances and all firewalls must be disabled first for it to work!!! We tried disabling firewalls and all the other stuff suggested by support. We are still clue less as to where the problem lies. To complicate the issue, we are in the process of expanding our network for overseas access to the servers, etc.. MS Support has esclated the proble to research team (don't know what that means) for resolution. Need resolution asap. Any help would be greatly appreciated.

 

[Sooner Al]

What Linksys router are you using at Area-1?
Are the Area-1 PCs using static or dynamic local IP addresses?
Are you calling the correct public IP, ie. the ISP assigned IP address, of the router at Area-1?

Is it possible TCP Port 3389 is blocked outbound at Area-2?

If you run this telnet test from a PC at Area-2, what are the results?

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

To access more than one Remote Desktop session behind a router look at this page...

http://members.cox.net/ajarvi/RemoteDesktop/Multiple_PC_RD.html

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

Area-1 has a wireless network consisting of 3 PCs running XP Pro (SP1), DSL Modem connected to

LinkSys Router, LinkSys Network cards, LinkSys Access Point. All PCs are relatively new and has 1 GB
of RAM.

Area-2 has a wireless network 2 PCs running XP Pro (SP1), DSL Modem connected LinkSys Router, LinkSys Network cards

Remote Desktop works great in Area-1 (same loc/bldg). All PCs can access each other with no problems via Remote Desktop.

Area-2 is 45 miles away from Area-1. Port forwarding has been enabled on Area-1 Routers to 3389

and PCs are configured for Remote Desktop access.

Remote Desktop access from Area-2 FAILS!!!. Error msg "Computer busy...etc". Worked with MS

Support for couple of weeks on this problem - problem still unresolved. MS support claims that XP
Remote desktop has problems functioning over such distances and all firewalls must be disabled first
for it to work!!! We tried disabling firewalls and all the other stuff suggested by support. We are
still clue less as to where the problem lies. To complicate the issue, we are in the process of
expanding our network for overseas access to the servers, etc.. MS Support has esclated the proble
to research team (don't know what that means) for resolution. Need resolution asap. Any help would
be greatly appreciated.

 

[Guest]

Area-1 Router - LinkSys Router WRT54
All PCs in Area-1 has static IP addresse

Don't know what you mean by calling the correct ISP assigned IP address. How do I go about finding the assigned ISP IP address

TCP port 3389 outboound is not blocked out in Area-2 as we can access the web thru the PCs connected to the router. However, somehow we cannot ping the router or access the router admin screen even when we are physically connected directly (Ethernet cable connnection) to the router. We don't understand this behavior. Any ideas? Thanks.

 

[Sooner Al]

You can find the public IP address of the Area-1 router, ie. the router your trying to access Remote
Desktop through, by going to the http://www.whatismyip.com site from a PC on the Area-1 LAN. That
would be the address you use to call from a PC on the Area-2 LAN. So you need to verify your calling
the correct IP for the Area-1 router when you call from Area-2.

TCP Port 3389 has nothing to do with accessing the web from a PC on the Area-2 LAN. TCP Port 3389 is
used by Remote Desktop (the Remote Desktop Protocol) for PC to PC communications and data. Are you
trying to use the web based Remote Desktop access or the normal Remote Desktop access (ie. NOT web
based)?

What were the results of the telnet test?

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

Area-1 Router - LinkSys Router WRT54G
All PCs in Area-1 has static IP addresses

Don't know what you mean by calling the correct ISP assigned IP address. How do I go about finding the assigned ISP IP address?

TCP port 3389 outboound is not blocked out in Area-2 as we can access the web thru the PCs

connected to the router. However, somehow we cannot ping the router or access the router admin
screen even when we are physically connected directly (Ethernet cable connnection) to the router. We
don't understand this behavior. Any ideas? Thanks.