Single-Homed Domain Controller to Multi-Homed

Everything is working fine on our single homed Win2003 domain controller (named bigserver) on our local LAN (IP: 192.168.1.1 class C). As part of an effort to isolate one department from another, we created a new subnet (IP:192.168.2.1 class C). The idea was to add a second NIC on our domain controller and make it serve as the domain controller on the new subnet. We added the NIC and rebooted the server. When it came up we noticed DNS had two entries for the server (biggserver) -- one for 192.168.1.1 and 192.168.2.1.

We went to Sites and Service and looked for the server in the new (192.168.2.1) site -- no cigar! We thought well maybe, we need to give the server a seperate name (otherserver) in DNS for the new IP:192.168.2.1 . Then rebooted, still no show on the entry in Sites and Services.

We then manually added the server into the new site and waited to see if the NTDS setting would show up under the new site but still no cigar! Unless I am told otherwise, I do not think this multi-homed server is acting like a DC on the new subnet. Any suggestions?
steve_woolleyAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
Dave_DietzConnect With a Mentor Commented:
A server can only be in one site at a time.

As long as the machines in both subnets can logon on using domain credentials the DC is serving both subnets.

A Domain can contain many subnets - a subnet can have machines from different domains.
A site can contain meny subnets - a subnet can only be part of one site.

Dave Dietz
0
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.

All Courses

From novice to tech pro — start learning today.