Monitor unlimited number of servers
Filter log events
Create email and web-based reports

Direct access to Microsoft articles
Customized keywords for major search engines
Access to premium content

Event ID: 1111 Source: TermServDevices

Level
Description
Driver <driver name> required for printer <printer type> is unknown. Contact the administrator to install the driver before you log in again.
Comments
 
I encountered same error few days ago. We discovered that our Phaser Printer had the wrong driver installed. I suggest you check the printer driver.
If you use a DOT4 (USB) printer and want to redirect it, you must change a registry setting on the client computer. See “MCSEworld TermServDevices Error” for details.
For quick access via Terminal Services without mapping local resources, run mstsc /console. The "/console" option will give you direct access to the server and will let you see popups and warnings. Also, you will have more rights to install software and so on. This option is only working with admin rights and only on W2k3.
Microsoft has a tool that you can use to resolve printer-mapping problems. See “Terminal Server Printer Redirection Wizard Tool” to get the tool.
From a newsgroup post: "On your RDP connection, you have enabled the local printers so the server is attempting to map that printer. Therefore, you can print locally from within the RDP session. The server does not have that printer driver installed henceforth the error. You need either to uncheck allowing local printers, install that printer driver, or leave it as is and know what the error is indicating".

Check ME294429 to see how Win2k and Win2k3 Terminal Services redirects a client computer's local printer ports.


If you are using Microsoft Windows Server 2003, you might get this error each time you log in using Microsoft Terminal Server Client (MSTSC). The way to fix this, is to run MSTSC, click "Options >>", click the "Local Resources" tab, and uncheck "Printers".
As per Microsoft: "When a client logs on, the Windows 2000-based server checks the name of the printer driver on the client and looks for the same printer driver name in the Windows 2000 Ntprint.inf file. If the name of the driver is not found, the error messages are logged and the printer is not redirected. ". See the links below for more details.

There used to be an article available from Microsoft: "ME253524 - Event IDs 1111, 1105, and 1106 with Windows 2000 Terminal Services" but it is no longer published (either is no longer applicable, it contained errors or simply did not fix the issue).

If you do not wish to map the local printers to the remote terminal services session you can disable this function by using the Terminal Services Configuration tool. Right-click on the connection type (i.e. RDP-Tcp) and on the Client Settings tab check "Windows printer mapping" to disable it.

Windows Event Log Analysis Splunk App

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.

Read more...

 

Cisco ASA Log Analyzer Splunk App

Obtain enhanced visibility into Cisco ASA firewall logs using the free Firegen for Cisco ASA Splunk App. Take advantage of dashboards built to optimize the threat analysis process.

Read more...