VPN windows 2003 with routeable IP address


the situation is as follows: I have a Windows 2003 server running which is connected to the internet. I have 4 (real) external IP addresses available on that machine. Two of which I am using for web sites. The other 2 I would like to be able to assign to VPN clients. I am having trouble to find the right settings to accomplish this.

I am using x.y.z.132 and x.y.z.133 for websites and a DHCP + RAS server. I would like to assign the x.y.z.28 and x.y.z.29 addresses to incoming VPN clients. The first problem I am having now is that the VPN server assigns itsself one of those (.28 or .29) addresses, leaving only 1 IP available for a VPN client. I would much rather have the VPN server use the .132 (or .133) address for itsself.

The other problem is that when the VPN clients gets the remaining address, it is not fully routeable. I mean that I would like someone on the internet to be able to connect to that address through my VPN server and have a connection to the VPN client.

Can anybody help me find the correct settings?


Who is Participating?
NYtechGuyConnect With a Mentor Commented:

This isn't possible.  They aren't routable because they are *ONLY* routable on your network.

The clients connecting from a remote location ALREADY have a valid external IP, as they are connecting over the internet to your VPN server.  Your IP address(es) are workable ONLY for your network, and theirs only work on their network.  

An IP address is not portable, it is dictated by the network to which you are connected.

All VPNs I have seen issue dynamic "private" addresses - 192.x.x.x, etc

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.