Link to home
Start Free TrialLog in
Avatar of Northumberland
Northumberland

asked on

Event ID 5719

On a Windows 2000 Professional PC Running Microsoft Service Pack 4 a user logs onto the domain without any error messages or any errors saying the profiles cannot be loaded etc.

BUT the event log reports : Event ID 5719 - Source : NETLOGON, No Windows NT or Windows 2000 Domain Controller is available for domain DOMAIN. The following error occurred:
There are currently no logon servers available to service the logon request.  

The PC has full network access after the logon without any problems so how do I stop the error in the event log ?
ASKER CERTIFIED SOLUTION
Avatar of Pete Long
Pete Long
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of JamesDS
JamesDS

Northumberland
Also, check that the User machine is pointing to the same internal DNS as the Domain Controller, and check that the DNS Server has a zone for your domain with the relevant _MSDCS entries

Cheers

JamesDS
Avatar of Northumberland

ASKER

Donte both of them and it didnt make any difference - the query is its machine specific other PC's on the DOMAIN are fine.
Northumberland
Try removing it from the domain and re-joining - not forgetting to backup the profile, just in case.

Cheers

JamesDS
This is probably WINS-related. Log on and check that you can resolve the name of the domain correctly (try opening User Manager or Server Manager for the domain). If necessary implement an lmhosts file. If you have any trusts with other domains ensure that your domain controllers have working secure channels to the other domains.

Using Domain Monitor will help with this (dommon.exe from the ResKit). Use nltest to check and reset your secure channels.
ThanQ
What  type of NIC card is the workstation running?  One of my networks experienced this with 40 workstations.  Yet the other 100 workstations had no problems.  The difference between the machines was the NIC card.  Turns out the NIC cards in the 40 non functioning machines were not completely windows 2000 compliant and generated the same errors as described above after completing authentication on the domain.  We exchanged the no-name NICs to a Name Brand NIC and presto, problem resolved.