Question

Locked

Citrix Printer Error

By pcolabove ·
I remotely support several servers and the way I access them is via a web browser .

"Citrix Web Interface" for Presentation server 4.0.

The Problem - After I print from a local application to our network and network printer(not the customers), I get the following error in the remote Servers event log

Event Type: Error
Event Source: TermServDevices
Event Category: None
Event I 1111
Date: 1/9/2007
Time: 8:42:55 AM
User: N/A
Computer: SERVER22
Description:
Driver Citrix Universal Printer required for printer Sales_C350 on eagle (from USIS07) in session 25 is unknown. Contact the administrator to install the driver before you log in again.

Now I dont have any other Citrix software loaded for printing. I only have the Citrix software that was required to remotely log in via a web browser

looking at Citrix web site I see some other client software that I think might allow me to control printers, etc. Just dont know where to go.

This conversation is currently closed to new comments.

3 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Answers

Collapse -

driver

by jamesatmaisonverre In reply to Citrix Printer Error

Try reinstalling to driver on the print server

Collapse -

Driver redirection, fixing registry, desktop management

by Tom Friedriks In reply to Citrix Printer Error

As you enabled local printing with RDP, server needs printer driver. Check you have printer driver name listed in Ntprint.inf because sytem does the check for it on user logon. You can use the Terminal Server Fallback Printer Driver feature to overcome the problem when server doesn't have driver that is installed on the client and needed to work with printer. Check if Computer Configuration|Administrative templates|Windows Components|Terminal Services|Client/Server Data Redirection is enabled within the linked GPO. You can create a printer mapping file yourself that will allow to map server driver name to client driver name. Open HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\Wds\rdpwd key, create new PrinterMappingINF and PrinterMappingINFSection String parameters and set the path to the INF file you want to use (i.e. c:\windows\inf\inffiletoredirect.inf) and 'Printers' as the value for these parameters correspondingly. Check the name of local and remote drivers and add a string to [Printers] section within that inffiletoredirect.inf:
"local_printer_driver_name" = "remote_printer_driver_name"
You also might want to use Terminal Server Printer Driver Redirection Wizard. Check also, if printer port doesn't begin from LPT, USB or COM. If so, it will not be redirected. Last but not least, the most convenient way to overcome such problems with lookups, redirection and other print management task I guess is to use desktop management software. We work with Desktop Authority and it smoothly works with auto-added printers when working with terminal connections.

Back to Networks Forum
3 total posts (Page 1 of 1)  

Related Discussions

Related Forums