No Windows NT or 2000 domain controller available. Event ID 5719
This weekend, I set up a new 2003 AD machine on my network in preparation of retiring the old 2000 machine that was handling the process. I carefully followed all the white papers, was successful in the forestprep and domainprep functions then DCPROMO'd the new machine as an additional AD controller in an existing domain, I then transferred all the FSMO's to the new 2003 machine. Everything went as smoothly as possible but today I'm seeing sporadic "No Windows NT or Windows 2000 Domain Controller is available for domain XXXXX" in my System Event Log. Any idea what gives?
ASKER
It is and it wasn't. I stumbled across that just 20 minutes ago. I changed it and am monitoring it bow. I hope it's that simple.
Let me know
is your network card 1GB ?
ASKER
Well that's a fine question, it's a VMWare virtual machine and doesn't really specify. Just "Flexible" in bridged mode. The host however, is a Gigabit Ethernet adapter. The problem does seem to have subsided after only having the machine see itself for DNS. Not entirely sure why that would be an issue but I'm not complaining. I'll monitor it throughout the busy part of the day today and see what happens.
ASKER
Spoke too soon. I failed to refresh my event viewer. Still happening every couple of hours.
check here if you are able to isolate issues
http://blogs.technet.com/b/instan/archive/2008/09/18/netlogon-5719-and-the-disappearing-domain.aspx
http://blogs.technet.com/b/instan/archive/2008/09/18/netlogon-5719-and-the-disappearing-domain.aspx
there are a all possible scenarios discussed in this blog. hopefully one of them mataches your case
ASKER
Thanks, I'm seeing some interesting things in DNS (I inherited this domain 4 months ago). I found that the new server wasn't resolving its name under nslookup. I issued a /registerdns and that fixed itself. I'm also doing some cleanup. I'll tear into that link and see where it leads me...
ASKER
I mean, my experience has been that most any time I scratch my head in confusion, it turns out to be a DNS issue :-)
Are you still having issues?
ASKER
Yes, I'm waiting until later tonight to apply the latest Windows updates. I found hidden among the other login errors, Kerberos Ticktet (krbtgt) login failures in the security log. Researching this revealed that there are patches that need to be applied (There's a shock. These servers weren't well maintained). If Kerberos isn't working correctly, who knows what other things will be happening. Unfortunately I won't have an opportunity to reboot the machine until after 11:00 pm this evening. I'll keep you posted.
Sounds good.
ASKER
Still having issues. Minimal and not causing any user discernible issues but still highly annoying. I have to move on for the rest of today but will poke around some more over the weekend.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Needed to resolve this to ask my next questions. I appreciate all the help but in a world of fires, ths smoldering embers sometims just get stepped on.
Make sure that your 2003 DC is a GC.
Make sure the server is only pointing to itself for DNS.
Post dcdiag