jedinegotiator :
Thanks for the help. I do have a couple more questions. I have set up a VPN on my computer as the host and we have successfully connected but every time we connect it will last for a minute or two and then the client computer will lose internet connection completely. Something is conflicting with another. I think it may be what your saying with the subnet as I am still a little confused on what you mean by that. Are you saying one computer needs to be 255.255.255.0 and the other 255.255.0.0? I dont think thats what you mean but im not sure.
255.255.255.0 and 255.255.0.0 are subnet masks. When combined w/ an IP address, they determine your subnet.
Let’s say your network is using addresses 192.168.1.1 thru 192.168.1.255. That means the subnet mask is 255.255.255.0, with the trailing .0 indicating only the last node changes.
Let’s say the other network is using addresses 192.168.1.1 thru 192.168.255.255. That means the subnet mask is 255.255.0.0, with the trailing .0.0 indicating the last two nodes change. This subnet has 255 times more usable network addresses than the previous subnet. More importantly, this subnet and the prior subnet *overlap* since this subnet includes the prior subnet, and more.
What you need for the second network is a non-overlapping subnet, such as 192.168.2.1 thru 192.168.2.255 w/ subnet mask 255.255.255.0. Since it uses the same subnet mask as the first subnet, but uses a different third node (1 vs 2), you have no conflicts, no overlap, and no VPN issues.
Also do we need three computers for this to work? Does there need to be a third computer to actually be the VPN server or can one of the two computers be the server and the other the client?
There’s no need for a third computer (not unless you want to). Each computer can serve both as a VPN client and VPN server to the other. You’re essentially cross-connected. You see his computer/network, he sees your computer/network.
My local IP address is 192.168.3.100 and his local IP address is 192.168.1.2
Assuming you’re both using the same subnet mask of 255.255.255.0 (highly likely), you have two, non-overlapping subnets, so you’re fine. OTOH, if for some reason either of you was using a subnet mask of 255.255.0.0, then you’d have a problem since you’d have some overlap.
We connected together like I said but after we connect windows gets mad at something and he loses his internet completely. I am sure its something simple I am missing but please help me if you can.
In all likelihood you each want to maintain internet access locally, and only want direct access to each other’s “local” resources. Let’s assume that’s the case for now.
Each VPN client can be configured to either use its own gateway for internet access, or send Internet requests across the VPN. By default, Windows assumes the latter. But if the VPN server is configured to either not allow access to anything but that VPN machine, or doesn’t provide a default gateway for its VPN clients, then any VPN client expecting to use the VPN server for Internet access will be denied.
The best thing to do is to confine your Internet access locally. To do that, find the client network connection, right click to Properties, select the Network tab, double click TCP/IP, under TCP/IP properties select Advanced, and make sure “Use default gateway on remote network” is NOT checked. Now all your Internet access will remain local, it won’t use the VPN server.
Also since you said not to use DHCP what do I set the range to? something like 192.168.3.(150-200) or something like 192.168.4.(100-150)?
I said DHCP probably won’t work across the VPN (at least it gives me lots of headaches), but if it works for you, great. I think it’s either because the VPN client is not able to push DHCP requests across the VPN connection, or perhaps a policy issue on the VPN server side. I haven’t determined which.
So if you encounter the same problem, you can configure the VPN server w/ a static range of IP addresses. Doesn’t matter what you use as long as it doesn’t conflict w/ your existing devices or the IPs being handed out by the DHCP server on that network.