Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.


[edit: seems i wasnt clear enough, so i have rewritten parts]

I have one computer (A) running xp ready to recieve vpn connections on a local network (connected to the internet) in the 192.168.0.x range with the approriate ports forwarded from the router.

Client computer (B) is a windows 7 laptop on a different local network (connected to the internet) which also is configured to 192.168.0.x

Now, this obviously causes problems when B connects to A, specifically that B can only find A by IP and not by name.

Changing the range for B is not a good option because there are many many wifi networks out there with this configuration.

Changing the subnet for computer A is also a bit of a pain as there are many computers with static IPs.

So, instead of changing the whole local network where A resides, cant i just have A appear to have a different subnet to its vpn client? Because since im creating a virtual network between two computers, i should be able to give them any range i want?)

With that in mind I tried just turning off automatic dhcp in A's vpn settings and changed it to 172.31.255.x. Computer B now gets the address assigned alright and it can ping but it still cannot ping the server name and it seems to be because the dns on B's vpn connection points at

Is that the reason it doesnt work, and how can i change it?

PS everything worked when B was on a 192.168.1.x network, and there is no problem establishing the actual connection.


share|improve this question
wow. what? no idea what "xp server" is, and I can't figure out what your setup is. –  August Sep 7 '12 at 17:02
i have now edited my question, i hope it is clearer now. thanks –  laserpanda Sep 7 '12 at 21:22

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.