>>My original Dilemma....
[quote]Originally posted by easikwilson
[b]I have a network (192.168.1.xxx) on private side of Linksys WAP DSL/Cable Router which is connected to Internet via Cable Modem. I would like to establish a Remote Desktop Connection to a server located on the private side of a remote network (also a 192.168.1.xxx network) that is connected to the internet with a 3COM DSL Router with built-in VPN. I can currently establish the VPN connection through my Linksys equipment, but cannot connect to the server using Remote Desktop Connection while using the Linksys router on my end. If I remove the Linksys router on my end and use a direct connection from my local cable modem to a single PC, I can establish the VPN conenction AND I can connect to the remote server using Remote Desktop Connection. There are no known IP address conflicts between the two private networks, but it seems like when I have the Linksys router installed on my end that the connection request for Remote Desktop Connection may not be leaving my local private network, so I eventually get a "fail to connect error" just like you do if I use the wrong IP address when attempting to connect using the single PC approach without the Linksys router.
>>My response after trying to change one of the network IP settings...
I went ahead and changed the IP address (from say 192.168.1.xxx to 192.168.22.xxx) of one of the systems, and yes it does work now. Thank You !!
Is there any way known to have both networks at the same address?
>>New Information to aid with discovering a possible way to keep the IP addreeses of both systems the same.
In my original scenario, both networks were set at 192.168.1.xxx, and when I would VPN in from my cable-modem internet conenction, the gateway/router on the remote end (which has built-in VPN functionality, there is no "server" machine handling the VPN) would dole out an IP address of 192.168.1.189 (with a subnet mask of 255.255.255.255). I was able to see this information by using the IPCONFIG command from the command line. I could ping IP addresses (that existed) in the IP range 192.168.1.xxx on my end only, I could not ping any IP address on the remote network at all. Once I changed my smaller network address to 192.168.22.xxx and repeated the VPN conenction, I was once again assigned 192.168.1.189 by the remote network when connected by VPN, and now I could ping all known IP addresses in the remote network, including the Windows 2000 terminal services server to which I wanted to connect with remote desktop.
What I am looking for a solution to is finding a way to have both networks at 192.168.1.xxx (with no conflicting IP addresses on either end) and be able to VPN into the remote network and have my cable/DSL gateway/router allow me to both connect via VPN, but then see the IP addresses on the remote network. Once I can see the remote networks IP addresses, it seems I have no problem with conencting via Remote Desktop Connection to the Windows 2000 terminal services server.
Hope this helps...