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.
mimi8118Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Mohammed KhawajaManager - Infrastructure:  Information TechnologyCommented:
Install your DC in 192.168.0.0 subnet, in your sites and services add all three subnets belonging to the default site and your problem is solved.  With respect to DNS and DHCP, you can create your scopes on the AD DC (install DHCP roles) and in your router, add the IP address of the DC as the iphelper address.  This way, you will have DNS and DHCP hosted centrally.  I am assuming you do have a router where different subnets can communicate with each other.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Natty GregIn Theory (IT)Commented:
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.
0
Mohammed KhawajaManager - Infrastructure:  Information TechnologyCommented:
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.
0
Neil RussellTechnical Development LeadCommented:
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.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Legacy OS

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.