Windows Server multiple NIC's

NachT

NachT

NachT

Associate
Joined
20 May 2006
Posts
1,068
Hey guys,

I'm doing a bit of studying at the moment using Windows Server 2012.

I've got the main DC setup with two NIC's, the primary NIC is completely isolated to my main home network, and it is only used for communications between clients and other servers.

I've added in a second NIC, which can communicate to my actual home network and route, to gain internet connectivity. It uses a different subnet to the isolated network.

I'm trying to set it up so clients on the isolated network can also gain access to the internet, without having a second NIC in each of them. So they use the domain controller as a sort of gateway.

Whats the best way of getting this setup? Would I need to setup a proxy server?

If anyone has any links to guides, or could point me in the right direction that would be awesome!
 
It's a *really* bad idea to have a domain controller with more than one IP address. If you have a VM environment, just make the tiniest DC VM (1GB RAM is fine) you can, and create a separate proxy VM.
 
I can create another VM server no problem to avoid IP issues. So I'm guessing the proxy server will be the best way forward for something like this?

I've had a look through the various roles you can setup on 2012 R2, would a proxy server come under IIS?

I'm trying to avoid using 3rd party applications
 
The best/easiest way is to use a linux firewall appliance. Smoothwall is a popular option.
 
Thanks guys, ended up using Smoothwall as rotor suggested, all up and running now!

I would have assumed this kind of functionality would have been available within Windows Server, seems strange that it is not. But I'm still new, so just learning heh
 
NachT said:
Thanks guys, ended up using Smoothwall as rotor suggested, all up and running now!

I would have assumed this kind of functionality would have been available within Windows Server, seems strange that it is not. But I'm still new, so just learning heh
Click to expand...

Well of course it is, but if you understood AD and how it functions you wouldn't be surprised why multihoming can and if not properly configured will cause issues. Biggest issue is DNS poisoning, clients trying to connect to an interface they'll never be able to route to and subsequently authentication issues. Sites and services and site binding becomes difficult if not impossible.

Much better of using a router of sorts and a single interface using RAS.
 
NachT said:
I would have assumed this kind of functionality would have been available within Windows Server, seems strange that it is not. But I'm still new, so just learning heh
Click to expand...
It is entirely possible to do this with Windows, but I wouldn't recommend it.
 
You must log in or register to reply here.
Back
Top Bottom