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 originating IP address of message with ID <id> could not be determined based on its Received headers.
|English: Request a translation of the event description in plain English.|
From a Microsoft support post: This event means the message headers added by your ISP is not RFC- compliant or one of your servers is issuing non-standard receive headers or may be caused by incorrect configuration in the perimeter list.
Please go to ESM and locate Message Delivery -> General, open the perimeter
list, please check if there is any incorrect IP listed."
As per Microsoft: "This event indicates that Sender ID filtering is not able to correctly process a message. This error may occur if one of your servers is issuing non-standard receive headers. This error may also occur if you have not correctly configured the list of internal servers". See MSEX2K3DB for additional information about this event.
|Private comment: Subscribers only. See example of private comment|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated