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 system detected an address conflict for IP address 0.0.0.0 with the system having network hardware address <MAC>. Network operations on this system may be disrupted as a result.
|English: Request a translation of the event description in plain English.|
I had this with an Intel Based server that had dual network cards installed. The cards were teamed and presenting a single IP address but after about 6 weeks we started to get the IP address conflict which turned out to be between the 2 cards themselves. Breaking and recreating the team resolved the issue although only time will tell if this is a permanent fix or whether it will happen again in a few weeks.
You will see this event if Windows detects a duplicate media access control address on the network. See ME164903 for details.
See the link to "EventID 4199 from source Tcpip" for details on this event.
|Private comment: Subscribers only. See example of private comment|
|Links: ME164903, EventID 4199 from source Tcpip|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated