I know that the VPN Port is 1723 and cannot be changed. In a small office setting, there are less than 10 computers and each have Remote Desktop access set up from port forwarding configured by the router: Computer 1 Port 5001 --> 3389 Computer 2 Port 5002 --> 3389 ... Computer 10 Port 5010 --> 3389 When I try to do the same thing with the VPN ports: Computer 1 port 5101 --> 1723 Computer 2 port 5102 --> 1723 ... Computer 10 port 5110 --> 1723 and put in the ip address in the VPN client like so: xxx.xxx.xxx.xxx:5101 I am unable to connect unless I change the settings in the router to be Computer 1 port 1723 --> 1723. Is there a way that I am able to make the VPN work by the client using non-standard port numbers and where the router forwards everything to the proper port?

VPN isn't really designed to work that way. Why do you need to setup a VPN connection to multiple computers? Normally you would have one VPN server and all incoming connections would connect to that server. Once you are connected to the VPN server you should then have access to the internal network and be able to connect to individual computers just as you would if you were on the internal network. If you could give us a little more information about what you are trying to accomplish by setting up VPNs to multiple computers maybe somone could come up with an alternate solution. Kerry Brown MS-MVP - Windows Desktop Experience

Each computer would have it's own VPN connection, not having 1 VPN connection to multiple computers. When one thinks small office, they think that everybody in that office is working with the same software that benefits the company as a whole. Unfortunately, this is not exactly the case. To simplify things, each user is their own "business" that have decided to share common resources - ie. office staff, phone, copy machine, etc. Each user's computer is their own "personal" computer to where they install their own programs, store different file types, etc. Having each on-site computer run a VPN server makes it easier for the user to transfer files to their off-site computer while running Remote Desktop simultaneously. The vagueness of how Microsoft CAL's work and the cost involved is keeping Windows Server 2k8r2 from being deployed in that capacity.

The best way I can think of to do this is with a router/gateway device that is the VPN endpoint and has the ability to filter which computers VPN users can access based on the user. Maybe someone else can think of a better solution. Kerry Brown MS-MVP - Windows Desktop Experience

Microsoft MESH / Logmein / teamviewer / VNC / Hamachi.... Anyway but the builtin MS VPN

Using a 3rd party solution costs money & problems - not an option.

Microsoft MESH and VNC are FREE...logmein / teamviewer / hamachi have free for personal use. I am sorry to tell you that the options I posted are more secure, more robust and easy to use when compared to MS VPN, AND MS's VPN is more hassle which equals timewhich equals money. And for you want MS VPN is not an option, so you must look at third party tools.

Given what Longhair-NL is trying to do security is probably not a consideration :-) It sounds like a nightmare situation to me. The most secure solution would be a router/gateway/firewall that is the VPN endpoint then only allow each user to access their own computer via a protocol that the VPN can monitor and secure. Longhair-NL: As Bubbapcguy has said you have to find an alternative. The built in VPN solution will not meet your needs. Personally I would rethink what you are trying to do. Possibly a terminal server would work for remote access. In any case it will cost you either time or money or both to do this. It will be very hard to do it securely. Kerry Brown MS-MVP - Windows Desktop Experience

A properly set up SSH Server & PuTTY is giving me a secure tunnel, so that part is covered. It is sad that Microsoft has dropped the ball with it's VPN server once again forcing people to look for alternative solutions for port forwarding.