[Samba] Printing from Windows to Samba takes a LOT of time.

[Miguel Manso]

Hi there,

I've a linux server (PII 233, 94mb ram) running Mandrake Linux 9.1 with an HP
printer attached to it.

I've configured the printer (I'm using CUPS) and it works fine. Next, I've
configured samba:

[global]
.
.
.
   workgroup = MYWORKGROUP
   security = share
   log level = 2
   printing = cups
.
.
.

[hp]
   printer = hp
   printable = yes
   path = /var/spool/samba
   create mask = 0700


Now, I've installed the printer on a windows machine, it worked ok. I've tryed
the test page and it works like a charm.

Now, when I thought everything was doing fine, I've noticed that for documents
with more pages (4, 5, 6 ...) the printing takes a LOT (1,5 minutes for those
examples) to complete.

My first guess was that CUPS was taking too much time processing the job. After
analising the system with the "top" utility and configured CUPS to dissalow
printing jobs, I've noticed that the time was spent before CUPS. The smbd
process takes a lot to end.

I've looking at the /var/log/samba/log.user file and I've found this:


[2003/06/13 21:19:41, 2] rpc_server/srv_spoolss_nt.c:find_printer_index_by_hnd(263)
  find_printer_index_by_hnd: Printer handle not found:
find_printer_index_by_hnd: Printer handle not found: close_printer_handle:
Invalid handle (OTHER:2442:2255)
[2003/06/13 21:19:41, 2] rpc_server/srv_spoolss_nt.c:find_printer_index_by_hnd(263)
  find_printer_index_by_hnd: Printer handle not found:
find_printer_index_by_hnd: Printer handle not found: close_printer_handle:
Invalid handle (OTHER:2442:2255)
[2003/06/13 21:19:41, 2] rpc_server/srv_spoolss_nt.c:find_printer_index_by_hnd(263)
  find_printer_index_by_hnd: Printer handle not found:
find_printer_index_by_hnd: Printer handle not found: close_printer_handle:
Invalid handle (OTHER:2442:2255)
[2003/06/13 21:19:43, 2] rpc_server/srv_spoolss_nt.c:find_printer_index_by_hnd(263)
  find_printer_index_by_hnd: Printer handle not found: _spoolss_writeprinter:
Invalid handle (OTHER:2809:2253)


I thought that this only happed when I was printing, but no, it's allways
appearing on the log file.

My two guesses for the occurence are:

- My server is weak for the processing that samba needs
- I've any problem in the samba configuration (judging the logs)

Could someone point me to any direction? I think I've spent all my "guesses".

Thanks a lot.

-- 
Miguel Manso <mmanso at amplitudenet.pt>