Event 5778 May Be Logged with an Incorrect IP Address (311759)
The information in this article applies to:
- Microsoft Windows 2000 Server SP1
- Microsoft Windows 2000 Server SP2
- Microsoft Windows 2000 Advanced Server SP1
- Microsoft Windows 2000 Advanced Server SP2
- Microsoft Windows 2000 Professional SP1
- Microsoft Windows 2000 Professional SP2
This article was previously published under Q311759 SYMPTOMS
The System event log on domain controllers may contain many event 5778 messages. The event message may be similar to:
Event Type: Information
Event Source: NETLOGON
Event Category: None
Event ID: 5778
Date: 5/6/2002
Time: 2:20:16 AM
User: N/A
Computer: Computer Name
Description:
'Computer Name' tried to determine its site by looking up its IP address ('Computer IP Address') in the Configuration\Sites\Subnets container in the DS. No subnet matched the IP address. Consider adding a subnet object for this IP address.
CAUSE
Windows 2000-based clients that are multihomed or that use VPN to access the network that hosts Windows 2000-based domain controllers may send Netlogon packets from an interface that has a source IP address that is not the IP address for that interface. These packets contain IP addresses that belong to subnets that may not be configured in Active Directory. When a domain controller receives a Netlogon packet, it examines the source IP address to determine the client's site name. If a site cannot be located, event 5778 is logged.
RESOLUTIONTo resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the
Microsoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack
The English version of this fix should have the following file attributes or later:
Date Time Version Size File name
------------------------------------------------------
04-Feb-2002 11:41 5.00.2195.4901 143,152 Netbt.sys
WORKAROUND
In some cases, you can ignore these events.
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows 2000 Service Pack 3.
Modification Type: | Minor | Last Reviewed: | 9/26/2005 |
---|
Keywords: | kbHotfixServer kbQFE kbbug kbfix kbnetwork kbWin2000PreSP3Fix kbWin2000sp3fix KB311759 |
---|
|