Discussion Locked

logging on and authentication issues

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I am one of several server admin managing a very large enviroment that is currently just finshed the W2K rollout for our servers. the desktop enviroment is primarily NT with a few Win95 machines.. We have several remote country sites plus 4 overseassites all with at least 1 DC. The problem is that at some of the sites when our users logon they are getting authenticated by a remote DC, not the local one.. in one case our tokyo users are getting authenticated by a DC in one of our mining sites in remote western australia. This involves several router hops and as can be expected frustrating. I would appreciate any help in trying to determine why this happening...

5 replies

by "doctor"

In sites and directories, make sure you have your physical structure correct, aka, you have your domain controllers list on the right subnets relative to your sites. Also, look at your domain replication scheme. And, make sure your tokyo users members of organization units only that exists on their local domain controllers. Having the same users spread out across multiple units will do this.

by timwalsh

One question about your organization:

Is your organization such that you have several sites within a single large domain, or is each site a subdomain in the AD forest? If the situation is the former (single large domain), your problem could be one of location of Global Catalog servers. Global Catalog serves are critical to log-on and authentication. I would suggest making 1 DC at each site a Global Catalog servers.

This discussion is closed to new replies.