Win2k clients die when getting properties of hp printers served by Samba 2.2.x

[Lluís Batlle i Rossell]

I don't know how can I use the HP drivers in the Win2k clients...
The HP printers are network printers served by Samba. I've tried two Samba versions: 2.2.3 and 2.2.5; the last one is the one we use.

The problem becomes when trying to get the properties of the HP printer, when the driver is already installed. Accessing the properties dialog makes "explorer.exe" process die, and it has to be restarted. All system becomes unstable after the first dying of 'explorer.exe'.

This problem only appears when using latest HP printer drivers. If we use Microsoft printer drivers for the HP printers, we don't have any problem.
But Microsoft drivers don't allow setting all the properties of the printers.
The printers we have are:
- Two HP 920 (actually using HP 880C drivers from MS)
- Two HP 1220C (actually using HP 1120C drivers from MS)
- One HP Business Inkjet 2230C (without knowing which drivers to use)
- One HP DesignJet 750C+ (using MS drivers)

Using MicroSoft drivers, we cannot set resolution over 300dpi in 1220C printers (a pitty), or some other settings in the DesignJet plotter.

Some old HP 1220C drivers don't blow up 'explorer.exe', but they print garbage.

The problems appears with ALL Win2ks we have tried: just after installing Win2k OS, using ServicePack2, ...

I've been some days looking for documentation through Internet, but I haven't found anything. I hope to get some help from you!
Thanks!

[Paul Bush]

Samba isn't the best print server. I would recommend using a jetdirect card or box, and configure the Win2k PCs for TCP/IP direct printing. It works like a charm, and gives the print driver full control. When adding the printer to Windows, select LOCAL printer instead of network printer, uncheck automatic detect, click next, then select 'create new port' and select 'Standard TCP/IP Port' from the drop down menu. Configure the port, add the driver, and viola! Problem solved.

Hope that helps!

Paul

[Ron Kinner · Accepted solution]

Time to get SP3. It's out now.

http://windowsupdate.microsoft.com

SP3 fixes:

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q317250

which may be your problem.

Ron

[Lluís Batlle i Rossell]

Thanks for your help, but it doesn't solve my problem. :(

1. All the printers I have are in jetdirects. But I must note that: I WANT A SPOOL. :)
The spooler is a CUPS server, which also has a samba acting as a windows printing server.

2. I tried that SP3 patch about HP printers about one week ago, when it was released. It didn't help.

I must note that patching Samba with "parse_sec.patch" (from one guy from HP... John, iirc) helped because now the Business Inkjet printer work.

It seems impossible for me to make the HP1220C drivers work. Windows spooler (and sometimes also explorer) die when trying to print (I can get & modify properties now!).

And I haven't tried the HP DesignJet 750C drivers (I'm still using the Microsoft ones), because they work for what I need. They are a bit ripped, but it doesn't suppose any problem for me.

My hardest problem is HP1220C drivers, because it's a high resolution printer, and M$ drivers only allow 300x300dpi. And the people who print to that printer needs high resolution!

Please, I would like you to try a samba printing server with the HP1220C drivers, and see what happens. HP1120C drivers also give same results. I tried them as the printers are similar.

I must note that this isn't a CUPS problem, as I use "print command" defined as a 'cat' to a file.
Samba logs at level 3 also don't help! and I don't understand nearly nothing at level 4! :)

Thanks for your interest!!

[Lluís Batlle i Rossell]

Sorry! It's me again!

I must say that I cannot submit to SP3 licensing terms.
Microsoft may think that their users are stupid. :)

[Ron Kinner]

It's interesting that Samba 2.2.5 release notes

http://www.linuxmax.net/news/00808.html

say:

25) Corrected alignment bug in spoolss parsing code which caused Win2k/XP
clients not to be able to view printer properties from a Samba host

You might try reporting your problem to the samba folk at:

samba@samba.org


Perhaps they can help.

Ron