General discussion

Locked

Computers join domain at different sites

By scottara2 ·
OK. I think this is a good one.
My host site has 3 domain controllers.
When physically at the host site, while joining a pc to the domain, the pc will often join the domain at a remote site. The computer doesn't show in AD host site, only at the remote site, until replication takes place.

Each remote site has one DC, and is connected to the host via 56k frame relay.

Regular user authentication seems to work fine, enterprise wide. Each user authenticates to their local DC at their site.

The KCC (Knowledge Consistency Checker) has been turned off enterprise wide.

This did work at one point, but I'm not sure what changed. Any ideas?

This conversation is currently closed to new comments.

5 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

by sgt_shultz In reply to Computers join domain at ...

if this used to work and now doesn't. i would check event logs on troublesome clients. i would ping local domain controller. i would ask myself what has changed on local domain controller? what do troublesome clients have in common

Collapse -

by p.j.hutchison In reply to Computers join domain at ...

Open Sites and Services MMC and check settings, make sure servers are in correct 'sites' and check replication schedule in the Inter-Site Transports section.

Collapse -

by CG IT In reply to Computers join domain at ...

why did you turn off the KCC? KCC is automatic and unless available bandwidth is so poor that KCC bring the whole net down you should have it on. Failover is also disabled if you turn off KCC. [if bandwidth is that bad you seriously ought to consider getting a bigger pipe]

Collapse -

by BFilmFan In reply to Computers join domain at ...

Since you've turned off default site bridging by disabling the KCC, this is normal behavior.

Check to see what is configured in the following registry key on the clients:

HKLM | System | CurrentControlSet | Services | Netlogon | Parameters |DynamicSiteName

The value of this key should eb the flatname of a domain controller.

You can explicitly name the sites that a DC will cover. To do so, set the system's HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters subkey's SiteCoverage value to the list of sites to cover (use the sites' relative distinguished names?RDNs?separated by spaces). Setting this value forces the DC to publish SRV records for the named sites, whether or not those sites already contain DCs. You can set the subkey's GcSiteCoverage value in the same way to control the publication of site-specific GC locator records.

In addition, are each of these domain controllers, also global catalogs?

Is this Windows 2000 or Windows 2003? Note that if the systems are Windows 2000, you will need to have Service Pack 2 installed for this registry modification to function properly.

Collapse -

by exNN In reply to Computers join domain at ...

on sites and services, make sure the subnets are properly configured on each site. so the hosts will look for their local DC

Back to Windows Forum
5 total posts (Page 1 of 1)  

Related Discussions

Related Forums