Domain Controller with 2012 Errors and Connectivity Problems
Description: The server has encountered a network error.
- Your network interface card (NIC) may not be functioning correctly.
- You may have an outdated or incompatible NIC.
- Replace the NIC on the server that is having the Event ID 2012 errors.
- Contact the manufacturer of the NIC and get an updated driver.
- If the client is receiving one of the above error messages, a quick test to rule out something on the client side causing the problem would be to pause the NetLogon service on a domain controller with the 2012 errors. If the client is able to log on to another domain controller successfully, then the problem has been isolated to the server.
- Check for the IPX protocol and the Btrieve applications on the server.For additional information, see the following article or articles in theMicrosoft Knowledge Base:195641 Btrieve, IPX, and Event ID 2012
- Replace the network interface card (NIC) on the server with the Event ID 2012 errors. The faulty NIC may be any variety of Token Ring or Ethernet.
- Review the Windows NT Hardware Compatibility List (HCL) to ensure that the NIC in the computer is on the HCL. If the card is not on the HCL, replace it with an HCL-compatible NIC.
- Another known cause of connectivity problems is that the NIC driver may be outdated. Obtaining an updated driver from the manufacturer may resolve the issue.
- The problem has also been seen with network switch problems that may be preventing the connectivity on an intermittent basis. Resetting the network switch may resolve the issue. Contact the switch manufacturer for detailed information on resetting your network switch.
Article ID: 200017 - Last Review: 12/05/2015 10:26:27 - Revision: 2.3
- kbnosurvey kbarchive kbprb KB200017