The remote client would have access to all resources on this server through its private IP address. If the VPN server is not connected to a local network, that is all the remote client can see. This sort of setup can be used to give remote clients access to resources stored on this server but no other machines. There is one possibility which might work as you want.
You may have to install a second interface to do that as NAT needs a public and private interface , but you could use a loopback adapter either a NIC with a loopback plug or a Microsoft Loopback Adapter. You could then add the internal interface mentioned above as a private interface in NAT.
You can do that from the RRAS console unless you are running W2k, where you had to use a netsh command. From W2k3 it is included in the GUI.
Hello Bill and thank you for replying. What you wrote in the second paragraph sounds like something that is worth trying. However, I am not sure how to configure that. Would it be possible for you to include the major steps of this kind of setup so I can follow them? Thank you, Arie. There is very little to do manually. The wizard can configure NAT.
I would install the loopback adapter first and manually configure it with an IP address in its own IP subnet. Since you don't have a LAN, nothing actually uses this. Go to the IPv4 tab and set up an address pool for your remotes. You have now configured both NAT and remote access. The physical NIC should have "public interface connected to the Internet" selected and both the loopback adapter and the internal interface should have "private interface connected to private network" selected.
Your remote access clients should now have Internet access through this server. I will post some screen shots on my skydrive it I have time later.
As far as how to configure it in the VM guest, or adding a NIC and make it available in the VM guest, it would be done within the VM utility, bujt that would depend on what virtual host you are running. Keep in mind, if the guest will be accessing the external subnet, the host will require an additional interface physically plugged into the outside network.
After you've configured the virtual host and guest with the appropriate IPs and interface connections, you can follow the RRAS wizards. I still think it's much, much easier and works just as well using a single NIC and keeping the RRAS server internal, and translate port re-map the necessary ports in the firewall to the server. Use that option. Why would it matter what virtualization product he was using? He will not be using the loopback adapter at all.
There are no local clients at all. He could in fact disable the MLA and everything would still work. It is only required to provide a second interface for the NAT setup wizard. The reason I mentioned that is each virtual product has their own ways to configure an additional interface. Some consider HyperV a little confusing setting up additional interfaces. But the whole point of this exercise is for this server to do NAT for the remote clients.
Because it is a VM, I can either install the MS loopback adapter from within the Windows server or add an additional virtual adapter, it wouldn't make a difference at all. However Ace, the host does not have a second dapter installed in it. Let's go back to the beginning for a moment. You said it has one adapter, as you are saying now. Is this NIC physically plugged in and connected to the WAN side of the perimeter firewall or is it plugged into the internal network switch with a private IP, but you have a public IP mapped to it?
I think this is the easiest method based on your current setup. We are leasing a server from a hosting company. We installed VMware server and now the server that we are leasing is hosting another Windows Server on it. Currently, the Guest has only one virtual NIC installed I can add more with no problems and again, it is configured with a public IP address in the same range as that of the Host server. There are no private IP addresses involved in this configuration at all.
Hmm, Interesting scenario. The other servers all have public IPs. From your description, there is no private subnet. You would appear to need to redesign everything if this is the case.
Hello Ace,. This could very well be the case! I think I will drop this case for the moment until we figure out what exactly we need to accomplish and how and then will reopen this can of worms. Thank you for all your help thus far. No, that isn't really necessary, Ace. This is usually set up so that remote users can keep an Internet connection without having to use split tunnelling or a second server on the LAN.
But there is really no necessity to have a private LAN at all. IP address winserver : Can anybody help me to solve this problem? Please somebody answer me Share Flag. All Answers. Collapse -. Back to Networks Forum. Start or search. Start New Discussion. Create a new discussion If you're asking for technical help, please be sure to include all your system info, including operating system, model number, and any other specifics related to the problem.
It turns out that if you have 2 NIC's on a seperate network both need to be set up to route. I enabled both as routers and enabled RIPv2 on each including my router and everything works flawlessly. If you're asking for technical help, please be sure to include all your system info, including operating system, model number, and any other specifics related to the problem. Also please exercise your best judgment when posting in the forums--revealing personal information such as your e-mail address, telephone number, and address is not recommended.
Please note: Do not post advertisements, offensive material, profanity, or personal attacks. Please remember to be considerate of other members. All submitted content is subject to our Terms Of Use. A breif overview of my home server lab topology. My guess at how this works is NIC2 becomes router for the I assume I need a default route for this network that points to NIC1.
0コメント