B
Brian
Hi,
I'm in the progress of updating our domain to W2K3. We have 2 W2K combined
AD and DNS servers. I have now installed 2 W2K3 combined AD and DNS servers
and promoted them. When I set the DNS to point at itself (just like it is
configured on the old W2K servers) I get several errors.
First it takes about 5 minutes to get a logonprompt. It is just displaying
"Preparing Network Connections". Then after 5 minutes I can log on. There is
then several errors in the event log.
The Systemlog starts with a Netlogon error - 3096. "The primary Domain
Controller for this domain could not be located"
Then there are several LSASRV errors - 40960
BROWSER errors - 8021 and 8032
Also the Directory Service log gets an error - NTDS Replication - 2088.
If I set the DNS to point at one of the other DNS servers there is no
problems. But Microsoft Best Practice explain that you should point DNS to
the servers own IP address.
I hope someone can help me out.
Thanks in advance.
Best Regards
Brian
I'm in the progress of updating our domain to W2K3. We have 2 W2K combined
AD and DNS servers. I have now installed 2 W2K3 combined AD and DNS servers
and promoted them. When I set the DNS to point at itself (just like it is
configured on the old W2K servers) I get several errors.
First it takes about 5 minutes to get a logonprompt. It is just displaying
"Preparing Network Connections". Then after 5 minutes I can log on. There is
then several errors in the event log.
The Systemlog starts with a Netlogon error - 3096. "The primary Domain
Controller for this domain could not be located"
Then there are several LSASRV errors - 40960
BROWSER errors - 8021 and 8032
Also the Directory Service log gets an error - NTDS Replication - 2088.
If I set the DNS to point at one of the other DNS servers there is no
problems. But Microsoft Best Practice explain that you should point DNS to
the servers own IP address.
I hope someone can help me out.
Thanks in advance.
Best Regards
Brian