asked on

New Domain Controller with 2 subnets

I have inherited a customer that is currently on 3 workgroups with a file server in each workgroup. Workgroup 1 is accounting & office PCs on 192.168.0.X, workgroup 2 is Production Machines on 192.168.1.X & workgroup 3 is Shipping & Receiving on 192.168.100.X.; all set up that way from previous tech. They purchased a new Windows 2012 std. server several months ago before their "IT Guy" died & have asked me to research installing & configuring this new server as a the Primary DC with AD DS, DNS & DHCP for the entire physical network. They would like to keep the subnets as they are now due to the number of devices attached to those networks.

I'm researching to see what best practices would be in this scenario or to place everything into 1 network & use GP to define the separation between areas/groups. I would have to change a lot of IPs locally because of off-site tech support for production machines, etc.

Any & all suggestions would be greatly appreciated.

ASKER CERTIFIED SOLUTION

Mohammed Khawaja

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Natty Greg

if no router the server can act as a router you'll just need 3 different network interface card to separate the networks, each running a different sub-net, while keeping everything simple, and central. That's how this whole internet started, one server with at least 10 modems in it for dial up internet.

Mohammed Khawaja

Couldn't disagree more. You should not multi-home a DC, just buy yourself a cheap router and save yourself the headache of having Domain and DC issues.

Neil Russell

Please, for your own sanity and (if you have one) your partners sleep, do NOT add multiple NICs to your DC!

You will have far more problems than you will solve and it is NOT a supported configuration.