Tarantella Administration Guide > Printing > Why do UNIX clients have a printer called _Default created in their Windows 2000/2003 application session?

Why do UNIX clients have a printer called _Default created in their Windows 2000/2003 application session?

Users, who access applications on a Windows 2000/2003 application server using a UNIX client, may find that they have a printer called _Default created in their Windows application session. This can be confusing to users if they actually have a different printer attached to their client or they have no printer attached.

This is caused by the default setting in the printerinfo.txt file which is used to associate the printer driver name with a print job when printing from a Windows 2000/2003 application server.

Correcting the printer driver name

To change the driver name, so that it shows the name of the printer the user actually has, you need to either:

Note Users do not have to have a printerinfo.txt file, but if they do, its settings take precedence over the settings in the default.printerinfo.txt.

Edit the [UNIX] section of this file so that it shows the correct printer name, Windows 2000/2003 printer driver name and printer type, for example:
"salesprinter" = "HP LaserJet 5/5M" PostScript

Note To ensure you have the correct driver name, search for it in the default.printerinfo.txt file. This file contains all the common driver names. We advise you to copy and paste the drive name from this file so as to avoid errors (for example, incorrect capitalization).

Removing the printer from the Windows application session

If users have no printers attached to their client device, you can prevent the printer from appearing in the Windows application session by removing the [UNIX] section from:

Related topics
  • Configuring printing for UNIX clients
  • Printing from a Microsoft Windows 2000/2003 application server