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.
System error while enumerating the domain controllers. domain: <domain> ecode: <value> : message: <error message>.
|English: Request a translation of the event description in plain English.|
This can be caused by PCs or laptops physically connecting to the network that are members of a workgroup and not on the domain. Compare the domain listed in the event log error with the "domains" listed in My Network Places (My Network Neighborhood | Entire Network | Microsoft Windows Network). This error will go away once the PC or laptop is off the network long enough.
Check the Description field for the specific error. This response is specifically for "0x1558000: The Windows system call NetSessionEnum returned an error for server domain_name\domain_controller_name. Error Code: 53 : The network path was not found."
Websense looks to its C:\Program Files\Websense\bin\dc_config.txt file to find domain controllers. Our file still had entries for old DCs. I deleted them from the file restarted the agent and the above event log error regarding internal domain controllers is gone.
See the link to "Websense Support Article #: 1077" for documentation about troubleshooting DC Agent.
|Private comment: Subscribers only. See example of private comment|
|Links: Websense Support Article #: 1077|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated