Discussion Locked

NETLOGON ERRORS

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
WIN2K DC generates "... failed: Status = 1355 0x54b ERROR_NO_SUCH_DOMAIN" errors when I use the NLTEST & NETDOM Utilities. As MS KB(Q260889)suggest, I used the FQDN instead of NETBIOS names. Yet, this domain is presently being broadcasted accross the network along with all its trusts: the NLTEST /DOMAIN_TRUSTS generates a successful response without any errror??? Nevertheless, I can not reset the computer account passwords. AD won't let you reset computer accounts on DCs. I must resolve this issue; Kerberos relies on W32TIME and W32TIME relies on NETLOGON services and all this stabilizes the domain structure. WIN2K EVENT LOG ID = 5721 on DC & 5789 on member server. All other administration tasks work fine; I just can not eliminate these NETLOGON ERRORS.

5 replies

by rabbit_runner

Do you have a HOSTS or LMHOSTS file on this machine? If there is, try renaming them to something else. Then re-boot.

I have had experience where a server on a domain, could not find the domain controler. It could ping and browse the network, but not find the domain controler. This prevented me from adding it to the domain. After much searching, I learned that when I upgraded this server, the previous OS had those files. Those files then hindered the normal network connectivity.

This may not be the problem in your case, but it is worth looking into.

Best of luck. Let me know the results.

by somastro

Thanks for your input. But I really don't think that is the problems because prior to last week I was not getting NETLOGON ERRORS. Thanks again.

by jack republic

DO SOME TESTS LIKE NETDIAG ,DCDIAG FROM WIN2K SUPPORT TOOLS AND LOOK FOR FATAL ERRORES.MY GUESSE IS THAT THERE IS A DNS PROBLEM.

This discussion is closed to new replies.