Cached credentials issue

[Guest]

I didn't see a Windows 2003 AD forum so I'm using this one.

We currenly promoted a new DC into the domain. When laptop users are
connected to the network and their LOGONSERVER is the new DC they don't
experience any issues. When the LOGONSERVER was the new DC during the users
last authentication/login when the laptop is disconnected from the network
the user is NOT able to make use of cached credentials. If the LOGONSERVER
was any of the other DC's during the users last authentication/login when the
laptop is disconnected from the network the user DOESN'T have any issues
making use of cached credentials. Any thoughts on what is causing the issue
or suggestions of what to look into?

 

[Herb Martin]

I didn't see a Windows 2003 AD forum so I'm using this one.

It's called:
microsoft.public.windows.server.active_directory

[I wish Microsoft would stop changing the names
of the product and the newsgroups convention and
just have "whatever.CurrentVersion.areaOfInternet"
Then when we go to Server 2006 Or 2007 it would'nt
matter.]

We currenly promoted a new DC into the domain. When laptop users are
connected to the network and their LOGONSERVER is the new DC they don't
experience any issues. When the LOGONSERVER was the new DC during the users
last authentication/login when the laptop is disconnected from the network
the user is NOT able to make use of cached credentials.

Such problems (authentication or replication probably) are
usually DNS errors in Win2000 or Win2003.

If the LOGONSERVER
was any of the other DC's during the users last authentication/login when the
laptop is disconnected from the network the user DOESN'T have any issues
making use of cached credentials. Any thoughts on what is causing the issue
or suggestions of what to look into?

Likely that new DC is not properly repclicated.

Try DCDiag (on that DC) and check the following:

DNS for AD
1) Dynamic for the zone supporting AD
2) All internal DNS clients NIC\IP properties must specify SOLELY
that internal, dynamic DNS server (set.)
3) DCs and even DNS servers are DNS clients too -- see #2
4) If you have more than one Domain, every DNS server must
be able to resolve ALL domains (either directly or indirectly)

netdiag /fix

....or maybe:

dcdiag /fix

(Win2003 can do this from Support tools):
nltest /dsregdns /serverC-ServerNameGoesHere
http://support.microsoft.com/kb/q260371/

Ensure that DNS zones/domains are fully replicated to all DNS
servers for that (internal) zone/domain.

Also useful may be running DCDiag on each DC, sending the
output to a text file, and searching for FAIL, ERROR, WARN.

Single Label domain zone names are a problem Google:
[ "SINGLE LABEL" domain names DNS 2000 | 2003 microsoft: ]