samba - Aug 2002 - w2k and samba, printer properties hourglasses forver after driver upload + OK

RH 7.2 (LPRng) samba installed from 2.2.5-1 rpm with the following 
patches from http://us4.samba.org/samba/ftp/patches/jerry/post-2.2.5/:
Makefile.in.patch
addform.diff
ldap_start_tls.patch
parse_sec.patch
srv_spoolss_nt.patch

security=domain (using winbind), authenticate against windows pdc and 
use windows wins server.

What I do:
Connect to \\share-name from w2k pro as printer admin, double-click 
printers, right click on a printer in question, select properties.
I choose not to install a driver locally right now, viewing spooler 
properties is fine.
Now I go to upload a new driver under the Advanced tab from disk.  I 
point to the manufacturer's .inf, select correct printer, next, finish.

Now windows asks for *.inf on W2K Server CD-ROM, but I don't see one 
that matches the printer.  Here should I just point back to the 
manufacturer's .inf?  This is what I did.  Another time I selected the 
directory from the CD-ROM, but windows didn't see anything it liked 
there and prompted me again for *.inf on W2K Server CD-ROM.  Anyway, at 
this point I just selected the manufacturer's OEMSETUP.INF again.

Windows notified me that the .inf file does not contain a Microsoft 
digital signiature.  I clicked Yes, Continue.

Files upload to print share... I see them on the server in path/to/W32X86/2

I click OK (or Apply), and get the hourglass, and the properties window 
for the printer becomes unresponsive.  If I later end that task and try 
to print a test page, windows reports a failure.


Does anyone here see anything wrong in what I did?  What level logs 
should I post?  I have successfully uploaded drivers and been able to 
print using standard windows drivers for a different printer (LaserJet 
IIISi).  But now that I'm trying to install drivers from disk for this 
printer I get no luck.

Thanks for your help,
Daniel

smb.conf, potentially sensitive stuff removed:
# Samba config file created using SWAT
# Date: 2002/08/14 15:21:42

# Global parameters
[global]
        workgroup         netbios name         server string = Samba Server on
        interfaces         security = DOMAIN
        encrypt passwords = Yes
        password server         username map = /etc/samba/smbusers
        log level = 2
        log file = /var/log/samba/%m.log
        preferred master = False
        domain master = False
        dns proxy = No
        wins server         kernel oplocks = No
        winbind uid = 10000-20000
        winbind gid = 10000-20000
        winbind separator = +
        winbind enum users = No
        winbind enum groups = No
        guest account = ftp
        printing = lprng
        queuepause command = lpc stop %p
        queueresume command = lpc start %p
        blocking locks = No
        locking = No
        oplocks = No
        level2 oplocks = No
        socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192

[print$]
        path = /usr/local/samba/printers
        write list 
[printers]
        comment = All Printers
        path = /var/spool/samba
        printer admin         printable = Yes
        browseable = No

[tcslkm]
        path = /var/spool/samba
        printer admin         read only = No
        printable = Yes
        printer name = tcslkm
        comment = "windows test mita (6e)"

Hi there!

That's similar to the problem I had. I asked for help here, but noone has
given
a helpful answer.

The drivers made by HP for the HP 1220C do not work having samba as a
printing server.
When trying to print, spooler server dies (and sometimes also explorer.exe).

I have to keep on working with the M$ ripped drivers.

Hope you have better luck with it!

Any idea if uploading/downloading of print drivers from disk (not 
generic windows print drivers) from w2k will be fixed with samba 3.0 
release?  The print drivers worked with uploading from w2k box to NT 
print-server, but not w2k box to samba 2.2.5-1 rpm with patches.  The 
drivers upload successfully, but test print fails, etc.  Maybe it had 
something to do with no Microsoft digital signiature in the .inf file? 
 But it worked fine for uploading to w2k print server.  No Microsoft 
drivers available for this printer.  A different printer without 
Microsoft drivers had the signiature and uploaded fine, but print was 
wingdingish and often crashed print spooler and explorer.  Again, worked 
fine on w2k print server.  Does anyone have any luck with uploading 
print drivers from disk from w2k?  Has anyone encountered problems 
without the microsoft digital signiature in the .inf file?

Thanks,
~ Daniel

daniel.jarboe@custserv.com wrote:
> RH 7.2 (LPRng) samba installed from 2.2.5-1 rpm with the following 
> patches from http://us4.samba.org/samba/ftp/patches/jerry/post-2.2.5/:
> Makefile.in.patch
> addform.diff
> ldap_start_tls.patch
> parse_sec.patch
> srv_spoolss_nt.patch
>
> security=domain (using winbind), authenticate against windows pdc and 
> use windows wins server.
>
> What I do:
> Connect to \\share-name from w2k pro as printer admin, double-click 
> printers, right click on a printer in question, select properties.
> I choose not to install a driver locally right now, viewing spooler 
> properties is fine.
> Now I go to upload a new driver under the Advanced tab from disk.  I 
> point to the manufacturer's .inf, select correct printer, next, finish.
>
> Now windows asks for *.inf on W2K Server CD-ROM, but I don't see one 
> that matches the printer.  Here should I just point back to the 
> manufacturer's .inf?  This is what I did.  Another time I selected the 
> directory from the CD-ROM, but windows didn't see anything it liked 
> there and prompted me again for *.inf on W2K Server CD-ROM.  Anyway, 
> at this point I just selected the manufacturer's OEMSETUP.INF again.
>
> Windows notified me that the .inf file does not contain a Microsoft 
> digital signiature.  I clicked Yes, Continue.
>
> Files upload to print share... I see them on the server in 
> path/to/W32X86/2
>
> I click OK (or Apply), and get the hourglass, and the properties 
> window for the printer becomes unresponsive.  If I later end that task 
> and try to print a test page, windows reports a failure.
>
>
> Does anyone here see anything wrong in what I did?  What level logs 
> should I post?  I have successfully uploaded drivers and been able to 
> print using standard windows drivers for a different printer (LaserJet 
> IIISi).  But now that I'm trying to install drivers from disk for this 
> printer I get no luck.
>
> Thanks for your help,
> Daniel
>
> smb.conf, potentially sensitive stuff removed:
> # Samba config file created using SWAT
> # Date: 2002/08/14 15:21:42
>
> # Global parameters
> [global]
>        workgroup >        netbios name >        server string = Samba
Server on
>        interfaces >        security = DOMAIN
>        encrypt passwords = Yes
>        password server >        username map = /etc/samba/smbusers
>        log level = 2
>        log file = /var/log/samba/%m.log
>        preferred master = False
>        domain master = False
>        dns proxy = No
>        wins server >        kernel oplocks = No
>        winbind uid = 10000-20000
>        winbind gid = 10000-20000
>        winbind separator = +
>        winbind enum users = No
>        winbind enum groups = No
>        guest account = ftp
>        printing = lprng
>        queuepause command = lpc stop %p
>        queueresume command = lpc start %p
>        blocking locks = No
>        locking = No
>        oplocks = No
>        level2 oplocks = No
>        socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
>
> [print$]
>        path = /usr/local/samba/printers
>        write list >
> [printers]
>        comment = All Printers
>        path = /var/spool/samba
>        printer admin >        printable = Yes
>        browseable = No
>
> [tcslkm]
>        path = /var/spool/samba
>        printer admin >        read only = No
>        printable = Yes
>        printer name = tcslkm
>        comment = "windows test mita (6e)"
>
>
>