I'd like to use an added Win2K server on our small corporate network to do a job. The job: we access a remote network using one of a few IP addresses assigned to us. However, there are more users and individual PC's than there are IP addy's assigned to us and everyone has to switch from the internal DHCP IP addy to one of the assigned ones to access this remote network.
We use this VPN method to both browse a remote network in internet explorer and move files using Interdev. It'd be nice if we could get to the remote network by just typing in the URL in a browser without reassigning our machines with a new IP address acceptable to the remote network. Couldn't we get one machine, a server, to do some NAT or routing with one static IP address seen by the remote VPN serving network and then have all of the machines on our network somehow relate to our routing/ nat server to connect to the remote VPN network?
If so, in Win2K server, which service do I use? NAT actually doesn't seem right since we already have a DHCP server assigning IP's and a NAT server will want to do that (right?). Routing seems like a solution... I'm not sure.
Thanks!
Is this problem still ongoing? The solutions above will work?
Either a server performing NAT or a Router as allready suggested will cure this problem. However most medium to large companies employ this functionality in their firewall, for example my network uses a PIX firewall to NAT my eternal address which is registered 194.189.188.0 to my internal addresses which are all 172.16.0.0 I also have internal registered subnets but the NAT is only performed on the 172 addresses.
I am not a fan of mounting NAT on a server (No matter where it is in the network) the first point of call security wise on your LAN should be your firewall.
Also using this method inbound VPN is a breeze to set up, using Cisco's own secure client.
Pete