The other option for configuring a
Firewall settings
For printing to network printers or to through print servers, one important consideration applies: by default the software firewall (either Sygate Security Agent or Symantec Endpoint Protection, depending on image version) that ships with the OS image on the XPe or WES thin clients is set to block traffic needed to talk to network printers. In order to successfully use network printers, the firewall needs to be configured to allow traffic on three ports used for discovery and printing, UDP port 161 (SNMP), TCP port 9100 (JetDirect) and UDP port 5353 (mDNS). If traffic on any of those ports is blocked, discovery of and printing to network printers may fail.
In the scenario of a thin client that has been added to a domain, and the users
For environments where the Windows Firewall is used, the only rule that needs to be added to the default firewall configuration is to allow mDNS traffic (UDP port 5353).
Note: the printing
Printing over an RDP/ICA remote session
In order to print to a local printer from a Microsoft Terminal Services or Citrix Presentation Server session, the printer must be configured in the thin client first; that is, a print queue must exist in the “Printers and Faxes” folder such that printing from applications running on the thin client works.
With that
Microsoft Terminal Services
When a client connects to a Windows 2003 Server Terminal Services session, if the local printer
The recommended approach under Microsoft Terminal Services is to have the original UPD
(www.hp.com/go/upd) installed in the server. To ensure compatibility with the widest array of HP printers, it is recommended to use the PCL5 version of the UPD on the server. One exception for this recommendation is if your environment has standardized in postscript printers, in which case it might be more effective to use the postscript version of the UPD on the server.
Driver mapping
Clients using the UPD for Thin Clients driver version 4.7 or earlier need to use driver mapping because while the driver is based on the original UPD, it has a different driver name and won’t be seen as such by the system. To get around the need of having a multitude of different drivers installed on the
5