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.
Printer \\<IP address\printer name>specified in the request from <IP address> does not exist: request ignored
|English: Request a translation of the event description in plain English.|
I had the same problem on my Windows Server. In my case, the hosts file in C:\WINDOWS\system32\drivers\etc had the wrong IP address entry. After I fixed the entry and restarted the print spooler service everything worked fine.
This event (logged in Win2003) occurs when a Solaris LPR print server is sending jobs to a Windows Print Spooler where the Windows print queue no longer exists. To resolve, remove the LPR queue from the Solaris server.
This problem was first corrected in Windows NT Server 4.0 Service Pack 6 and Windows NT Server 4.0, Terminal Server Edition Service Pack 6. Please see Microsoft Knowledge Base Article - ME237420.
|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