Service records and sites

  • Thread starter Thread starter Andrew
  • Start date Start date
A

Andrew

Hello all,

Our org uses win2k.

We have one forest, within that we have 3 sites defined. In dns, under the
forward lookup zone, one of the sites keeps being populated with service
records from a domain controller not on that site. Thus logon scripts etc
are being run from the wrong DC. I've been through sites and services and
all looks to be OK.

Has anyone seen this before?

Any info much appreciated
 
Andrew said:
Hello all,

Our org uses win2k.

We have one forest, within that we have 3 sites defined. In dns, under the
forward lookup zone, one of the sites keeps being populated with service
records from a domain controller not on that site. Thus logon scripts etc
are being run from the wrong DC. I've been through sites and services and
all looks to be OK.

Has anyone seen this before?
Click to expand...

Sure. It is EITHER the server is in the wrong site
(but you checked this*) OR that the subnets are incorrectly
defined to specify the sites OR *even though it appears
to be correct replication is broken and the other DC(s)
don't see the same configuration.

Check your subnets (list them here if you wish).

Check your replication to see if that DC is in the
correct site on ALL copies of the AD.
 
Thaks for the reply Herb,

I have rechecked sites and services all is OK (from what I can gather - 3
sites and 3 subnets correctly assinged with the approproiate site domain
controller)

10.0.0.0/20 siteA DC-A
10.0.16.0/20 siteB DC-B
10.0.32.0/20 siteC DC-C

One thing I have noticed, when i opened ADS&S, i chose connect to domain
controller, siteC's DC was reported to be in siteB on the select server
list?

Any further help much appreciated.
 
Andrew said:
Thaks for the reply Herb,

I have rechecked sites and services all is OK (from what I can gather - 3
sites and 3 subnets correctly assinged with the approproiate site domain
controller)

10.0.0.0/20 siteA DC-A
10.0.16.0/20 siteB DC-B
10.0.32.0/20 siteC DC-C

One thing I have noticed, when i opened ADS&S, i chose connect to domain
controller, siteC's DC was reported to be in siteB on the select server
list?
Click to expand...

That sounds like a failure to replicate on
(at least) one of the DCs.

You say "all is OK" but did you check for
replication -- especially of the Config Partition
of AD (the Config partition is basicaly Sites &
Services.)
 
Thanks again Herb,

In sites and services, the way our previous admin has setup is that all 3
sites have all DC's added in there? is this correct? They have the site DC
with the other manualy added in? Does this shed any light on the issue?
Please let m eknow how to check for partition replication (AD Replication
Monitor with support tools?)

cheers, andrew
 
Sites are used to tell Active Directory what your network looks like.
Initially, there is a site called Default-First-Site and every dc thats
added to the domain is added to that site. What should happen is when you
add DCs to the domain, if they are in different physical locations, they
should have their own site. Next would be to create an appropriate subnet
and assign it to that site and finally add the DC to the site. You will also
want to create appropriate Site Links. Sites, subnets and site links tell
Active Directory what your physical network looks like so that KCC/ISTG
knows how to handle replication.

Here's a couple of helpful links:

Directory Replication Basics for Windows 2000:
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q199174

Well....it looks like MS has pulled some of the documents I've used on
sites, subnets and site links. Here's what I found googling:

http://www.google.com/search?hl=en&lr=&q=windows+2000+sites+site+links+subnets+site:redmondmag.com

http://www.google.com/search?hl=en&q=windows+2000+sites+site+links+subnets

HTH,
Chris
 
Back
Top