Use Windows (2k/2003) Printer Queues from HPUX

[Alzhy]

Has anyone successfully implemented printing from HPUX to pinter queues defined on Windows boxen? We've ben trying to consolidate printer control in our enterprise so that queues are managed from just one location -- on the Windows machines.

We are trying to avoid problem situations wherein HP and Windows will try to contend on who has access to which printer server port (mostly HP JetDirecr Cards and QMS ports). And in cases during printer maintenance, UNIX and NT Admins need to make sure nothing is sent to the printer ports...

[Ernie Burns]

Windows 2000 Advanced Server:
1. From the Control Panel select Add/Remove Programs
2. Select Add/Remove Windows Components
3. From the list of Components select "Other Network File and Print Services" Note - If you look at the details for this selection you will see "Print Services for UNIX".

UNIX:
1. Using SAM add printer as a remote printer.
Printer Name: UNIX printer queue name. Can be the same as the queue name on the remote system.
Remote System Name: Either IP Address of
the Windows Server or System Name if the UNIX system is able to resolve the server name. If you are unable to resolve the server name you could also place in /etc/hosts file on the UNIX server.
Remote Printer Name: Name of the queue on the Windows server.

[Alzhy]

Thanks Ernie.. we actually know how to do this either with the native Win2K/2003 services or a 3P product.

What I'd like to know is if colleagues in this forum are actually implementing this scheme and what experiences they may be having or if they recommend it. Let's face it, printers in any enterprise are almost by default largely controlled by the Windows machines and centralized. In contrast, UNIX machines have been traditionally interacting directly with the individual printers lpd/lpr subsystem (ie. the JetDriect card).. at times the printer group will have difficulty making sure no one will be using the printer. On windows, it is a simple call to the NT admin .. On UNIX, several calls to each admin of each boxen...

[doug mielke]

we do this on all our WAN connected printers, and many at our home office. I can also see the Win queue status from lpstat, (something I didn't get with our old Novell based printers)

The only down sides I have:
- printer setups can change on the Win side without my knowledge, so it requires some communication between the Win admins and the Unix guys.
- Sometimes after a Unix reboot some of the printers are not enabled. I assume this is due to slow communication links, but we've never had time to address this minor issue.