Hello,

I am setting up a VPN server at my small business and I am having a few problems.

I downloaded, set up, and installed PoPToP, its working great and I'm getting no problems surfing over the VPN. (Connected to from a Windows XP Machine)

However, I am having some network problems, and I hoped someone here might have the knowledge of networks that I don't have. The subnet at my office is 192.168.0.X. (we have a bunch of servers in the 192.168.0.200+ range that I want to connect to) This also happens to be the subnet that most home users have when logging into the VPN.

Now here's my problem: When I'm logged into the VPN remotely, my computer won't look through the VPN for a server we have (ie 192.168.0.200). Using ethereal, I can tell that windows is only looking on the lan for this address, not on the vpn. However, when I try to access any other IP (such as a website), it will look through the VPN and it will work correctly.

I would simply change some of the IPs of the various networks I'm dealing with, but unfortuantely I don't have the power to make that happen. (Its a long story).

Here are some of the things I'm considering: can I use NAT in some way so that the remote windows machines think that the servers here are actually another IP, such as 192.168.1.200? Can I add a 'route' on the remote windows machines, so they'll know where to look for the servers? (I saw something here about doing this, but I don't have the knowledge needed to apply it to my situation.)

If neither of those are feasible, is there someplace that I can go to get a handle on network terminologies that I need to know? Or perhaps a windows forum would be better suited to this question?

Thanks very much.

You need to route traffic hitting your external ip to your lan or more specifically a given host. There is no way to add a route to the local host because 192.168.0/24 is a privat or non routable ip space.

Tom