[Samba] install_printer_drivers.pl and 2.2.4 issues

[Tom.Klopf at mms.gov]

Brian,
    I have experienced problems with rpcclient of a similar nature. I think
samba (smbd in particular) has trouble handling a large number of printers..
I'm guessing over 40.  The reason I believe this is that when I connect with
rpcclient to a samba server with a large # of printers (200+), I get an
error when running "enumprinters": NT_STATUS_UNSUCCESSFUL.   I can connect
to an NT server with rpcclient with the same printers installed (we're
trying to replace our NT print servers) and the enumprinters command works
fine.  

Problems come up when I run "getdriver printername", as well - rpcclient
actually crashes in this instance: "Segmentation Fault".

The "setdriver" command works, though, so if you can load a driver for a
certain printer model with the "add printer wizard" method to one printer,
you can use "setdriver" to associate the rest of the printers of that model
type with the appropriate driver.

  Anyway, hope that helps - you're not alone, anyway :).  I'm guessing that
imprints probably uses the same ms-rpc commands as rpcclient, hence it's
hitting the same problems. I really hope they get this fixed in future
versions. I'd be willing to help bug-test for anyone trying to fix this, by
they way.



Thomas Klopf


-----Original Message-----
From: Brian Payst [mailto:bpayst at tnc.org] 
Sent: Thursday, June 13, 2002 2:43 PM
To: samba at lists.samba.org
Subject: [Samba] install_printer_drivers.pl and 2.2.4 issues

Hello -
	I've been working on getting ready to cut our 60+ Samba servers over
from the old style printers.def approach to the new printer drivers
databases. However, I'm have a hard time uploading the packages onto the
server using the install_printer_drivers.pl script from Imprints 0.0.9b.
	To make sure I wasn't packaging them wrong I used the
imprints.sourceforge.org server to get the pacakges, but I get the same
error as for my roll-your-own versions.


Samba version: 2.2.4-2
OS: RedHat Linux 7.2

Here's the console output

Retrieving remote server information...
        Valid Printer Share Names:
                ColorLaser
                LaserJet
                test

        Valid Port Names:
                Samba Printer Port

Samba share name: test
Printer port: Samba Printer Port
[rpc]: Printer Driver Information :
[rpc]:     Printer Model   = HP LaserJet 5P/5MP PostScript
[rpc]:     Environment     = W32X86
[rpc]:     Driver Filename = PSCRIPT.DLL
[rpc]:     Data Filename   = HPLJ5P_1.PPD
[rpc]:     Config Filename = PSCRPTUI.DLL
[rpc]:     Help Filename   = PSCRIPT.HLP
[rpc]: Installing Windows NT x86 drivers for HP LaserJet 5P/5MP
PostScript...
[rpc]: Printer Driver Upload Directory = \\techtest\print$\W32X86
[rpc]: putting file hplj5p_1.ppd as \W32X86\hplj5p_1.ppd (922.8 kb/s)
(average 922.8 kb/s)
[rpc]: putting file pscrptui.dll as \W32X86\pscrptui.dll (3651.4 kb/s)
(average 2793.8 kb/s)
[rpc]: putting file pscript.hlp as \W32X86\pscript.hlp (631.8 kb/s)
(average 2276.8 kb/s)
[rpc]: putting file pscript.dll as \W32X86\pscript.dll (3729.1 kb/s)
(average 2844.3 kb/s)
[rpc]: Printer Driver HP LaserJet 5P/5MP PostScript successfully
installed.
[rpc]: ERROR! Windows NT error code : [result was
NT_STATUS_UNSUCCESSFUL]
Cleaning up temporary files...
Installation experienced problems.


a level 10 log shows this in the client log:

[2002/06/13 12:14:06, 5] smbd/uid.c:change_to_root_user(214)
  change_to_root_user: now uid=(0,0) gid=(0,0)
[2002/06/13 12:14:06, 3] smbd/vfs.c:vfs_ChDir(568)
  vfs_ChDir to /
[2002/06/13 12:14:06, 3] smbd/connection.c:yield_connection(48)
  Yielding connection to
[2002/06/13 12:14:06, 3] smbd/server.c:exit_server(495)
  Server exit (normal exit)

relevant smb.conf:

[print$]
        path = /home/config/print
        guest ok = Yes
        browseable = Yes
        read only = No
        write list = root
[test]
        printable = yes
        gueat OK = yes
        comment = test printer
        printer name = testLaser
        path = /var/spool/samba


However, when Windows 2000 clients connect they do not download the
drivers nor recognize the printer model. The files are uploaded to
print$/W32X86/2/

Any help would be greatly appreciated (stopping my head from banging
into the desk repeatedly will do wonders for me).

Thanks. 
-- 
Brian Payst
Technology Services Manager
The Nature Conservancy
bpayst at tnc.org | 919.484.7857 x 132


-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba