Event ID/Source search
Keyword searchExample: Windows cannot unload your registry file
Event ID: 1374 Source: NTDS Inter-site Messaging
|Source: NTDS Inter-site Messaging|
The query for how sites are interconnected via transport CN=IP,CN=Inter-Site Transports,CN=Sites,CN=Configuration,DC=delrus,DC=ru failed with the
A device attached to the system is not functioning.
The record data is the status code.
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is NTDS and what are the roles of its components?
EventID 1374, and several other event log errors (like 1311 and 1586) were regularily occuring in our multiple Windows 2000 server environment. I would focus on a particular error, seem to get if fixed, only to have new ones occur. But when I found Article ME266657, the associated fix solved all of the replication, dns, and active directory errors. In a nutshell, we had Exchange 5.5 on a Windows 2000 server that was also acting as a Domain Controller. Apparently Windows 2000 NTDSA requires exclusive use of Port 389, but has a weak grip on it. Exchange''s LDAP protocol was interfering with NTDSA by taking control of port 389. When I ran DCPromo and demoted the server with Exchange 5.5, the relevant errors on all of the servers disappeared. Likely disabling LDAP on Exchange would have been adaquate, too. I had another server available to act as a Domain controller, so I chose that path.
I have seen this when rebooting. It followed a 1369 warning and appeared to occur after the DNS service had been shutdown, there was a warning from NetLogon (ID:5781) that DNS was unavailable.
|Private comment: Subscribers only. See example of private comment|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated