Default-First-Site-Name in windows 2003 active directory domain controller

[aaaa]

When I first created my windows 2003 domain controller, it is created under
Default-First-Site-Name.

Under subnets and IPs, I do not see anything....which is I guess, is the
default...

Now, I want to clean up this little bit....

If I have created this domain controller in my subnet say 192.168.100.X and
sunet mask 255.255.255.0 - then how do create these subnet and move my
first domain controller to here....so that it looks like lets say site name
as San Jose and subent 192.168.100.X and subnet mask 255.255.255.0.

Even if I do not have any other subnets and other domain controller else
where, still I like to do this as clean up process.......and I want to see
visually that this domain controller ( very first one ) is in this
subnets.....

thx

 

[Tim Springston \(MSFT\)]

When you create a subnet, it asks you to associate that subnet with an AD
site (as you may have seen). To associate your domain controller(s) with a
particular subnet, the domain controller(s) need to be located in the AD
site which the subnet is associated with.

To do that you can right-click the Server in it's current AD site location
(such as Default-First-Site-Name) and select Move, then choose the site you
wish it to be in.

To verify that your domain controller is identifying itself and being
identified by others as being in the same site you can do a couple of
different things.

-You can look in your Windows domain's forward lookup zone. Expand the
_sites subcontainer and look in the specific site container below that for
DNS service (SRV) records for that domain controller. If they are not there
as they should be it can lead to site membership discovery issues.

-You can examine the output from a NETDIAG /V on the domain controller and
look for the results of the test below, which will display a domain
controllers site membership:
DC discovery test. . . . . . . . . : Passed

Find DC in domain 'TESTDOMAIN':
Found this DC in domain 'TESTDOMAIN':
DC. . . . . . . . . . . : \\testdc.testdomain.local
Address . . . . . . . . : \\10.55.12.3
Domain Guid . . . . . . : {C45F07BE-1C7A-4445-9475-ESDDC232C}
Domain Name . . . . . . : testdomain.local
Forest Name . . . . . . : testdomain.local
DC Site Name. . . . . . : Houston <-----------------------------
Our Site Name . . . . . : Houston
Flags . . . . . . . . . : GC DS KDC TIMESERV WRITABLE DNS_DC
DNS_DOMAIN DNS_FOREST CLOSE_SITE 0x8

-In addition, you could watch the site discovery process by enabling
NETLOGON logging on the domain controller when you see or suspect a problem.

109626 Enabling Debug Logging for the Net Logon Service
http://support.microsoft.com/?id=109626

If I misunderstood your question or concern please post a reply.

 

[Tim Springston \(MSFT\)]

I wanted to add something that I did not explicitly say in the previous
post.

For site discovery to work properly the domain controller needs to have an
IP in that site's specified subnet range, and be registering it in DNS
successfully.