A last week there was a message about using Samba with HP Jetdirect cards. The Jetdirect cards don't multithread, so when samba does an lpq- there is a "hang time" for the client. I understand that. But, why is NT smart enough to put a message in the event log saying that the printer is busy as where *unix/samba causes the client to page me or come to my desk and wine "How come the printers are so slow now?" -Cox
The problem is that NT queus it all while the default setup of Unix remote printing is to send the file directly to the JD printer with the expectation it will queue the jobs. If you want to stop the whining set up a bounce queue entry in your printcap to force sever queueing and compensating for the JD. This will solve the problem as I see it, it worked for me. The problem is not with Samba it is in fact doing exactly what it should do. Regards Bruce Kerr