Remote Desktop problem testing internet ip on same subnet of a rou

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have Remote Desktop setup on one machine as the terminal server and on
another machine as the remote connection client. Both machine have XP Pro,
Service Pack 2 installed and are installed on the same home subnet attached
to a Netgear MR810v2 router. This setup is to test using Remote Desk before
actually using Remote Desktop over an internet connection. Remote Desktop
works very nicely when when the client connects to the server within the
local subnet (client ip 192.168.0.3 to server ip 192.168.0.4). However, when
I try to simulate using an internet connection by connecting from the client
to the internet ip of router (ip 65.188... omitted rest of the ip), I can
make the remote connection, but it works very, very slowly and eventually
fail ending the session. It does work to some some extent some times, but is
not at all useable. Since it does work a little bit, I think this a valid
way try to test -- but I could be wrong. The connection to the ISP is a
cable modem (roadrunner from Time Warner Cable). The down link speed is
about 4 mbs, and the up link speed is about .34 Mbps, so I am expecting
reasonable response times.

Does any one have any idea what might be the problem. Thanks.
 
Here are a few more details I forgot. The router has port forwarding set for
port 3389 to the terminal server ip, 192.168.0.4. I am using Windows One
Care on both machines with the Windows firewall enabled, of cousre. I think
the firewalls are probably set ok because I can connect using the ip of the
router -- but it runs so slowly and fails after awhile.

Thanks for any ideas.
 
RobertS said:
I have Remote Desktop setup on one machine as the terminal server and on
another machine as the remote connection client. Both machine have XP
Pro,
Service Pack 2 installed and are installed on the same home subnet
attached
to a Netgear MR810v2 router. This setup is to test using Remote Desk
before
actually using Remote Desktop over an internet connection. Remote Desktop
works very nicely when when the client connects to the server within the
local subnet (client ip 192.168.0.3 to server ip 192.168.0.4). However,
when
I try to simulate using an internet connection by connecting from the
client
to the internet ip of router (ip 65.188... omitted rest of the ip), I can
make the remote connection, but it works very, very slowly and eventually
fail ending the session. It does work to some some extent some times, but
is
not at all useable. Since it does work a little bit, I think this a valid
way try to test -- but I could be wrong. The connection to the ISP is a
cable modem (roadrunner from Time Warner Cable). The down link speed is
about 4 mbs, and the up link speed is about .34 Mbps, so I am expecting
reasonable response times.

Does any one have any idea what might be the problem. Thanks.
Click to expand...

Well, generally testing that way is not a valid test. In most cases using a
loopback like that just fails completely. Testing between two PCs on your
local network is generally only valid using the local LAN IP.

Really the only valid test using the public IP of the router is from a
computer that is not on your local network...

--

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...
How to ask a question
http://support.microsoft.com/KB/555375
 
Back
Top