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 Printer represented by PrintQueue LDAP://CN=ARHIMEDE-<printer name>,CN=<server name>,CN=computers,DC=altairtech,DC=net cannot be found: 709
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is LDAP?
What is the role of ESENT?
This event could also be caused by a shared printer on a workstation, when the workstation is turned off. When Active Directory tries to verify that the printer is present, it cannot contact the "print server" (the workstation that's off) and raises the error. From what I found, Active Directory performs this check every 8 hours. Solutions would be:
1. If you have configured that workstation as a print server, don't turn it off
2. When you share the printer, uncheck the "List in the directory" box (unverified).
This may be caused by a corrupted printer object on client workstation. Delete and re-add the printer on W2K workstation.
This event may occur on a Windows 2000 domain controller when File Replication Service is unable to update the local schema from the Primary Domain Controller. Look also for event 13508, which will confirm whether this is the issue.
|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