Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

NETLOGON IS DISABLED AFTER REBOOT 1

Status
Not open for further replies.
Dec 14, 2003
9
US
I have a problem that I can't seem to solve. When I reboot the Server 2003 (PDC), the service netlogon is disabled. I have enabled the service "automatic" and have started the service. Once I reboot the PDC the netlogon service is disabled. For Active Directory Event log the following error appears:

Active Directory was unable to establish a connection with the global catalog.

Additional Data
Error value:
1792 An attempt was made to logon, but the network logon service was not started.
Internal ID:
3200caf

For DNS Server log the following error is reported:

DNS server has updated its own host (A) records. In order to ensure that its DS-integrated peer DNS servers are able to replicate with this server, an attempt was made to update them with the new records through dynamic update. An error was encountered during this update, the record data is the error code.

If this DNS server does not have any DS-integrated peers, then this error
should be ignored.

If this DNS server's Active Directory replication partners do not have the correct IP address(es) for this server, they will be unable to replicate with it.

To ensure proper replication:
1) Find this server's Active Directory replication partners that run the DNS server.
2) Open DnsManager and connect in turn to each of the replication partners.
3) On each server, check the host (A record) registration for THIS server.
4) Delete any A records that do NOT correspond to IP addresses of this server.
5) If there are no A records for this server, add at least one A record corresponding to an address on this server, that the replication partner can contact. (In other words, if there multiple IP addresses for this DNS server, add at least one that is on the same network as the Active Directory DNS server you are updating.)
6) Note, that is not necessary to update EVERY replication partner. It is only necessary that the records are fixed up on enough replication partners so that every server that replicates with this server will receive (through replication) the new data.

For more information, see Help and Support Center at

I try to go into Active Directory and it is disabled. It tells me that the server could not be contacted. I know I receive all these errors and logs because of the netlogon service being disabled after reboot. Because once I enable the netlogon service and restart the mmc. Active Directory works fine and is contacted.

I tried everything I could think of. If you have any suggestions other than what already suggested, it will be greatly appreciated. Thanks for your help!
 
Hi Shem,

OK, first things first. In Win2K there is no longer a PDC but there is a PDC Emulator role. How many domain controllers are in your network? Have you verified that there is a Global Catalog configured? This is set in AD Sites and Services.

The fact that no GC is available is cause for concern, particularly since you are indicating that this is your main server. If you have more than one server then get a copy of the netdom utility from the resource kit and do a quick check to see what roles your server thinks it has.

use the command:
Netdom query fsmo

You should see that this server has the PDC Emulator role. Run this same command on your other DCs and make sure they all agree. If they don't then you have a replication problem between your DCs and this is a bigger problem. Let me know what you find on this and I will follow up on how to fix the replication problem if that is the case. I just had to resolve this for a client.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top