- 2003 Intermin Mode and Choice of Logon Server
- Posted by Phil Niles on February 20th, 2004
I have just upgraded my NT 4.0 domain to AD 2003. I now have two AD DCs and
two NT BDCs. I have about 20 Windows 2000 member servers. I have been
keeping a close watch on the event logs of the various servers. I noticed
many of the member servers have w32time errors. Now I think I know why but
the answer raises a question. I think their are so many w32time errors
because these member servers are still authenticating to the NT 4.0 BDCs. I
confirmed this by looking at the Logon Server environment variable. I
thought, however, that once you put an AD DC in a domain with 2000 or XP
machines those machines would automatically start authenticating to the AD
DCs. Is there a way to force the 2000 servers to seek out the AD DCs to
authenticate?
Phil
- Posted by Herb Martin on February 20th, 2004
That's my understanding too. But the behavior is predicated on the
Win2000/XP clients figuring out the AD is there and that is likely
to be compromised by any DNS problems.
My first check would be DNS, then DNS, then check DNS.
Run DCDiag on each DC -- check each client (including DCs and
"servers") to make sure their NIC "dns server" properties point to
the Dynamic DNS server (set) for the domain.
--
Herb Martin
"Phil Niles" <philniles@mcleodusa.net> wrote in message
news:4035866e@news.splitrock.net...
- Posted by Firmbyte on February 20th, 2004
Without seeing the actual error msg it's dificult to say whats causing the W32Time errors , but it might help to read this acrticle: http://support.microsoft.com/default...kb;EN-US;21673
- Posted by Phil Niles on February 22nd, 2004
Herb,
I finally got my member servers to recognize the AD 2003 servers by stopping
the netlogon service on the BDC that they were authenticating to. The I
logged off and back on. This time the servers authenticated against an AD
2003 server. I started the netlogon service again, logged off, and then
logged back on. The servers kept choosing the AD server.
I only tried this method after confirming that DNS was working correctly by
using nslookup and some queries that Mark Minasi suggests in his Windows
2003 Server book.
Phil
"Herb Martin" <news@LearnQuick.com> wrote in message
news:uSYYi529DHA.1672@TK2MSFTNGP12.phx.gbl...
