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 server has encountered a network error
|English: This information is only available to subscribers. An example of English, please!|
As per Microsoft: "The following situations can cause these symptoms:
- Your network interface card (NIC) may not be functioning correctly.
- You may have an outdated or incompatible NIC. "
See the links below for more info.
I believe this error can also result from disabling (but not uninstalling) the IPV6 protocol. I had been getting this error for months, but haven't seen it since going to the properties for the connection and uninstalling IPV6.
See ME907546 for a hotfix applicable to Microsoft Windows 2000.
See WITP72465 for possible solutions to this problem.
This event can indicate a corrupt “tcpip.sys” file. Make sure ME898060 is installed and set the MTU size to 576. See ME898060 for more details on this issue.
Peter Van Gils
Look in the System log for cluster errors and warnings. More specific, EventID 15 from source disk, EventID 1035, 1077, 1215, 1209 from source clussvc, EventID 57 from source ftdisk, EventID 50 from source ntfs, and so on. If any, resolve these first.
See ME134905 and the link to "EventID 2012 from source NCP Server" for details on this event.
Jason S. Rundle
See Microsoft Knowledge Base Article - ME193839.
|Private comment: Subscribers only. See example of private comment|
|Links: EventID 2012 from source NCP Server|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
|Custom search for *****: Google - Bing - Microsoft - Yahoo|
Send comments or solutions
- Notify me when updated