I have been getting an even viewr error ever since one the nt machine use a different domain name.<br><br>How do I get rid of the following error message:<br><br><br>No Windows NT Domain Controller is available for domain TEST2. (This event is expected and can be ignored when booting with the 'No Net' Hardware Profile.) The following error occurred:<br>There are currently no logon servers available to service the logon request. <br><br>Thanks for any input,<br><br><br><br>
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 IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
EVEN VEIWER ERROR
- Thread starter Solo
- Start date
SunilVarma
IS-IT--Management
hi solo,<br><br>Can i get the event id for this..<br><br><br><br>
- Thread starter
- #3
- Thread starter
- #4
SunilVarma
IS-IT--Management
Hi Solo,<br><br>Found the folling solution in the technet cd. Hope this will solve the problem. If the problem still persists, pls give all the details about your setup like ras, how many pdc servers, stanalone servers, type of clients, and protocol for communication. <br><br>If the below solution din't solve the problem then you pls try to remove all the protocols and then recreate it and get back to us with the updates.....<br><br><br><br><br>:quote:<br><br>Netlogon Event ID 5719:<br> <br> No Windows NT Domain Controller is available for domain <domain_name>.<br> The following error occurred:<br> <br> There are currently no logon servers available to service the logon<br> request.<br> <br>NOTE: This event is expected and can be ignored when booting with the No Net<br>Hardware Profile.<br><br><br><br>CAUSE<br>=====<br> <br>Workstation and stand-alone server computer accounts are mistakenly treated as<br>LanMan backup domain controllers (BDC) by the primary domain controller (PDC).<br>LanMan BDCs are declared as such in a Windows NT domain by creating a special<br>Windows NT global group called servers, creating user accounts that correspond<br>to the computer names of the LanMan BDCs, and placing those user accounts in the<br>servers group.<br> <br>Authentication with the PDC fails when the accounts in the servers group are<br>actually Windows NT workstations and servers. This is because Windows NT will<br>use the secure channel account password against to authenticate with the PDC.<br>The PDC finds a matching user account in the servers group for the Windows NT<br>system and treats it as a LanMan BDC. During challenge/response authentication,<br>the PDC uses the user account password instead of the secure channel password to<br>authenticate the Windows NT system. This causes the errors noted in the summary.<br> <br>RESOLUTION<br>==========<br> <br>If no LanMan BDCs exist, then remove the servers group and restart the Netlogon<br>service on the PDC.<br> <br>If LanMan BDCs exist, then remove the user accounts for the Windows NT systems<br>experiencing this problem from the servers group. Restart the Netlogon service<br>on the PDC.<br><br>:unquote<br><br>
- Status