samba - Aug 2006 - Samba Point-and-install driver location problems

Hi,

I'm trying to configure my Samba server to support Point-and-install 
driver installation of a CUPS printer (the printer works with Samba when 
Point-and-install is not configured, and the driver is installed 
manually on Windows XP).  I've gone through the actual configuration 
process, and am able now to just install the printer on Windows XP 
machines via the Samba-supplied driver.  When I click on the printer 
properties and look at the printer driver path in Windows, I see a 
problem though, as the UNC name for the printer server is prefixed by 
*4* backslashes, instead of 2.  ( \\\\SATURN\print$\........ ).  I'm 
guessing this is what then causes Windows to behave very strangely and 
continue to prompt for printer drivers.  rpcclient shows the following:

root@saturn $ rpcclient -U'root%password' -c 'enumdrivers 3'
saturn

[Windows NT x86]
Printer Driver Info 3:
        Version: [3]
        Driver Name: [AcuLaser-C900-driver]
        Architecture: [Windows NT x86]
        Driver Path: [\\\\SATURN\print$\W32X86\3\EPKAI7CC.DLL]
        Datafile: [\\\\SATURN\print$\W32X86\3\EPKAI7CC.DAT]
        Configfile: [\\\\SATURN\print$\W32X86\3\EPKAI7AC.DLL]
        Helpfile: [\\\\SATURN\print$\W32X86\3\EPKAI7AC.HLP]

        Dependentfiles: [\\\\SATURN\print$\W32X86\3\SETUP32.DLL]
        Dependentfiles: [\\\\SATURN\print$\W32X86\3\E_SRCV03.EXE]
        Dependentfiles: [\\\\SATURN\print$\W32X86\3\E_SMSTE1.HLP]
        Dependentfiles: [\\\\SATURN\print$\W32X86\3\E_SCHK03.EXE]
        Dependentfiles: [\\\\SATURN\print$\W32X86\3\EPUPDATE.EXE]
        Dependentfiles: [\\\\SATURN\print$\W32X86\3\EPKAI7RC.TAG]
        Dependentfiles: [\\\\SATURN\print$\W32X86\3\EPKAI7QC.DLL]
        Dependentfiles: [\\\\SATURN\print$\W32X86\3\EPKAI7JC.DLL]
        Dependentfiles: [\\\\SATURN\print$\W32X86\3\EPKAI7BC.DLL]
        Dependentfiles: [\\\\SATURN\print$\W32X86\3\EPKAI0UC.EXE]
        Dependentfiles: [\\\\SATURN\print$\W32X86\3\EPKAI0TC.TAG]
        Dependentfiles: [\\\\SATURN\print$\W32X86\3\EPKAI0SC.TAG]
        Dependentfiles: [\\\\SATURN\print$\W32X86\3\EPKAI0OC.EXE]
        Dependentfiles: [\\\\SATURN\print$\W32X86\3\EPKAI0MC.DLL]
        Dependentfiles: [\\\\SATURN\print$\W32X86\3\EPKAI0LC.DLL]
        Dependentfiles: [\\\\SATURN\print$\W32X86\3\EPKAI0KC.DLL]
        Dependentfiles: [\\\\SATURN\print$\W32X86\3\EPKAI0GC.DAT]
        Dependentfiles: [\\\\SATURN\print$\W32X86\3\EPKAI0EC.DLL]
        Dependentfiles: [\\\\SATURN\print$\W32X86\3\E_LEST32.DLL]
        Dependentfiles: [\\\\SATURN\print$\W32X86\3\E_L1X111.DAT]
        Dependentfiles: [\\\\SATURN\print$\W32X86\3\E_L1E111.DLL]
        Dependentfiles: [\\\\SATURN\print$\W32X86\3\E_L19111.EXE]
        Dependentfiles: [\\\\SATURN\print$\W32X86\3\E_L18111.EXE]
        Dependentfiles: [\\\\SATURN\print$\W32X86\3\E_L10IC1.EXE]
        Dependentfiles: [\\\\SATURN\print$\W32X86\3\EB_SET04.EXE]

        Monitorname: []
        Defaultdatatype: [RAW]

I have seen from output that other people have posted from rpcclient 
enumdrivers that the rpcclient output should contain the UNC name with 
only two backslashes, instead of the four I have.  

The printer driver was installed through rpcclient, using the 
following command line:

rpcclient -U'root%password' -c 'adddriver "Windows NT x86"
AcuLaser-C900-driver:EPKAI7CC.DLL:EPKAI7CC.DAT:EPKAI7AC.DLL:EPKAI7AC.HLP:NULL:RAW:EB_SET04.EXE,E_L10IC1.EXE,E_L18111.EXE,E_L19111.EXE,E_L1E111.DLL,E_L1X111.DAT,E_LEST32.DLL,EPKAI0EC.DLL,EPKAI0GC.DAT,EPKAI0KC.DLL,EPKAI0LC.DLL,EPKAI0MC.DLL,EPKAI0OC.EXE,EPKAI0SC.TAG,EPKAI0TC.TAG,EPKAI0UC.EXE,EPKAI7BC.DLL,EPKAI7JC.DLL,EPKAI7QC.DLL,EPKAI7RC.TAG,EPUPDATE.EXE,E_SCHK03.EXE,E_SMSTE1.HLP,E_SRCV03.EXE,SETUP32.DLL'
saturn

This operation was successful, as was associating the driver with the 
printer.  

testparm produces this output

------------
Load smb config files from /etc/samba/smb.conf
Processing section "[homes]"
Processing section "[public]"
Processing section "[printers]"
Processing section "[AcuLaser-C900]"
Processing section "[print$]"
Loaded services file OK.
WARNING: You have some share names that are longer than 12 characters.
These may not be accessible to some older clients.
(Eg. Windows9x, WindowsMe, and smbclient prior to Samba 3.0.)
Server role: ROLE_STANDALONE
Press enter to see a dump of your service definitions

[global]
        workgroup = DOMTEST
        server string = %h server (Samba, Ubuntu)
        obey pam restrictions = Yes
        passdb backend = tdbsam
        passwd program = /usr/bin/passwd %u
        passwd chat = *Enter\snew\sUNIX\spassword:* %n\n
*Retype\snew\sUNIX\spassword:* %n\n .
        username map = /etc/samba/smbusers
        syslog = 0
        log file = /var/log/samba/log.%m
        max log size = 1000
        socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
        load printers = No
        printcap name = cups
        show add printer wizard = No
        preferred master = Yes
        dns proxy = No
        panic action = /usr/share/samba/panic-action %d
        printing = cups
        cups options = "raw"
        print command = 
        lpq command = %p
        lprm command = 

[homes]
        comment = Home Directories
        read only = No
        create mask = 0700
        directory mask = 0700
        browseable = No

[public]
        comment = Public Data
        path = /home/samba/public
        guest ok = Yes
        share modes = No

[printers]
        comment = All Printers
        path = /tmp
        create mask = 0700
        printable = Yes
        browseable = No

[AcuLaser-C900]
        comment = Epson AcuLaser C900
        path = /var/spool/lpd/alc900
        guest ok = Yes
        printable = Yes

[print$]
        comment = Printer Drivers
        path = /var/lib/samba/printers
        write list = root
        read only = No

------------

This is on a Ubuntu 6.06 server.  I've had the exact same behaviour with 
both the stock Ubuntu Samba server deb package, as well as with a Samba 
I have downloaded and compiled from source.

I am now running the from-source built Samba 3.0.23a.

Would appreciate any suggestions as to how to solve this problem.

Roshan

--
http://roshan.info

Error: Keyboard not attached. Press F1 to continue.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Roshan Sembacuttiaratchy wrote:
> I'm trying to configure my Samba server to support 
> Point-and-install  driver installation of a CUPS
> printer (the printer works with Samba when
> Point-and-install is not configured, and the 
> driver is installed  manually on Windows XP).
> I've gone through the actual configuration  process,
> and am able now to just install the printer
> on Windows XP machines via the Samba-supplied driver.
> when I click on the printer properties and look
> at the printer driver path in Windows, I see a
> problem though, as the UNC name for the printer 
> server is prefixed by  *4* backslashes, instead
> of 2.  ( \\\\SATURN\print$\........ ).  I'm
> guessing this is what then causes Windows to
> behave very strangely and  continue to prompt
> for printer drivers.
Nope.  That's not the problem.  The code has been that way
for a really long time.  I'd recommend looking at a
level 10 debug log from smbd instead.
> The printer driver was installed through rpcclient, 
> using the following command line:
I know I started this but I really wish people would
install using a real Windows client instead.




cheers, jerry
====================================================================Samba       
------- http://www.samba.org
Centeris                         -----------  http://www.centeris.com
"What man is a man who does not make the world better?"      --Balian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.4 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFE12apIR7qMdg1EfYRAmteAKCrN9rYiekknZpdYPGGk20zAvr+8gCgsXzp
W5kOt+jTjGFDN7qf0vc3W2A=O1Te
-----END PGP SIGNATURE-----