Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
The cluster IP address resource could not create the required NetBIOS interface.
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is the role of the Cluster Service?
What is a cluster ip address resource?
As per Microsoft: "There may be a network adapter problem or a network adapter driver-related problem. Make sure that the adapter is using a current, correct driver. If this is an embedded adapter, contact the OEM to determine if a specific OEM version of the driver is required. If you already have many IP address resources defined, make sure that you have not reached the NetBIOS limit of 64 addresses. If you have IP address resources defined that do not need NetBIOS affiliation, use the IP address private property to disable NetBIOS for the address". See the link to "Windows Cluster Service Troubleshooting and Maintenance" to download the original white paper.
See MSW2KDB for additional information about this event.
As per Microsoft: "This behavior occurs because Netbios has a table limit of 64 IP Addresses. In most cases, this number of IP addresses might be used for World Wide Web or FTP resources which do not require an entry in the Netbios table". See ME248605 for more details.
This behavior can occur if third-party network drivers are added to the computer and the installed Windows NT service pack is not reapplied.
|Private comment: Subscribers only. See example of private comment|
|Links: ME232910, ME248605, Windows Cluster Service Troubleshooting and Maintenance, MSW2KDB|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated