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.
|Maintenance: Recommended maintenance tasks for Windows workstations|
<computer name> is not a valid computer name.
|English: Request a translation of the event description in plain English.|
This behavior can occur if any one of the following conditions is true:
1.The computer has two network adapters and both network adapters attempt to register the same NetBIOS name with the Microsoft Windows Internet Naming Service (WINS).
2.A static entry exists in the WINS database.
3.There is a problem with a hardware component of the network, for example, a switch or router.
See ME317140, "JSI Tip 0935" and "JSI Tip 0980" to solve this problem.
If your computer has two network adapters installed, this behavior can occur if both network adapters attempt to register the same NetBIOS name with the Microsoft Windows Internet Naming Service (WINS). See ME197157 to avoid this problem.
See ME248057 to find out how to remove and reinstall the Workstation service.
See the link to "EventID 3870 from source System" for details on this event.
A possible static entry in the WINS database is the cause of this problem. To resolve this problem, remove the static entry from the WINS database.
|Private comment: Subscribers only. See example of private comment|
|Links: ME166184, ME197157, ME248057, ME317140, EventID 3870 from source System, JSI Tip 0935, JSI Tip 0980|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated