[Samba] Fedora, Cups, print$, and Windows XP - Oh my :) Round 2 - FIGHT

[jed at kraptastic.com]

Hello from Canada!

I'm posting again about a problem I posted about in February, I'll repost
the message here, with updated information. When I read that it was a
possible/probably bug with Samba, I decided to wait a while and see if it
wasn't hashed out by now. It doesn't appear to be fixed (or I messed up).
Anyways, here is the information with updates. A "*" indicates new info.

Thanks.

-----
Executive summary:
I can make the printer print if I, in order:
Install the printer driver in windows
* A prompt warns me about virus's and whatnot
Delete the printer driver in windows
so a smbstatus
kill the session
Install the printer driver in windows again.
* This time there is no prompt

Then everything works. This is not just one client, its several. I assume
its a permission issue so I have tried setting permissions to 777, and
force user = root, guest account = root, to no avail. I'm hoping some
pro's here will have some time to take a peek at this one. I've checked
google, google groups, samba.org faq's and dox, and searched the mail
lists here for quite a bit of time. I just can't seam to get past it.

-----
The details:

The first time I install the printer driver in windows, i'm given the
warning:

You are about to connect to a printer on printx0r, which will automatically
install a print driver on your machine. Printer drivers may contain virsus
or scripts that can be harmful to your computer. It is important to be
certain that the computer sharing this printer is trustworthy. Would you
like to continue? I select Yes, and it pulls up the printer display menu.
If I try and do a printer properties from there, I get the error

"Function address 0x6062e728 caused a protection fault. (exception code
0xc0000005) Some or all propery page(s) may not be displayed."

Then I can display nothing. However, if i delete the driver and kill any
connections to the PC that just gave this error, and reinstall the driver
The warning message does not appear, and the error does not come up.
Printing works just fine. If it was just me I'd live with it, but this is
for a couple dozen people.

* We have been using a dreaded windows box for a print server

 My configuration:
-----
OS - Fedora Core 1
Kernel - Linux 2.4.22-1.2115.nptl
* Samba - (updated rpm) samba-3.02-7.FC1 (from Fedora's updates)
Cups - (defualt rpm) 1.1.19-13
Printer - HP CP1700 (connected via USB)
-----
smb.conf
[global]
         workgroup = shiney
         server string = %h server (Samba %v)
         load printers = yes
         printing = cups
         printcap name = cups
         map to guest = Bad User
         hosts allow = ALL
         null passwords = yes
         username map = /etc/samba/smbusers
         smb passwd file = /etc/samba/smbpasswd

[printers]
         comment = All Printers
         path = /var/spool/samba
         browseable = no
         public = yes
         guest ok = yes
         writable = yes
         printable = yes
         printer admin = root
         use client driver = yes

[print$]
         comment = Printer Drivers
         path = /etc/samba/drivers
         admin users = root
         guest ok = yes
         read only = yes
         write list = root
-----
I played around with doing guest only, and forcing users, to no avail.
* I also tried doing several variants of security = share, paranoid sever
security = yes/no, use client driver, devmode = yes, all sorts of config
options
-----
testparm reports no errors.
-----
permissions on /var/spool/samba nobody:nobody(0777)
permissions on /var/cache/samba nobody:nobody(0755)
permissions on /etc/samba/drivers root:root(0777) -R
-----
cat /etc/samba/smbpasswd
root:0:F6E25(etc)
nobody:0:NO PASSWORDXXX(etc)
-----
cat /etc/samba/smbusers
root = administrator admin
nobody = guest pcguest smbguest
-----
rpcclient -Uroot%secret -c 'enumprinters' printx0r
        flags:[0x800000]
        name:[\\printx0r\HPColor1700]
        description:[\\printx0r\HPColor1700,HP Color Inkjet CP1700,General
Purpose Printing]
        comment:[General Purpose Printing]
-----
rpcclient -Uroot%secret -c 'enumdrivers' printx0r

[Windows NT x86]
Printer Driver Info 1:
        Driver Name: [HP Color Inkjet CP1700]


[Windows NT x86]
Printer Driver Info 1:
        Driver Name: [HP Color Inkjet CP1700]

-----
not sure why this is listed twice.
* still not sure why this is listed twice. :)
-----

rpcclient -Uroot%secret -c 'getdriver HPColor1700' printx0r

[Windows NT x86]
Printer Driver Info 3:
        Version: [3]
        Driver Name: [HP Color Inkjet CP1700]
        Architecture: [Windows NT x86]
        Driver Path: [\\printx0r\print$\W32X86\3\hpwa2ku0.dll]
        Datafile: [\\printx0r\print$\W32X86\3\hpwa1700.dat]
        Configfile: [\\printx0r\print$\W32X86\3\hpwantp0.dll]
        Helpfile: [\\printx0r\print$\W32X86\3\hpwauih0.hlp]

        Dependentfiles: [\\printx0r\print$\W32X86\3\hpwacfg0.exe]
        Dependentfiles: [\\printx0r\print$\W32X86\3\hpwaren2.dll]
        Dependentfiles: [\\printx0r\print$\W32X86\3\hpwaren1.exe]
        Dependentfiles: [\\printx0r\print$\W32X86\3\hpwasvb0.dll]
        Dependentfiles: [\\printx0r\print$\W32X86\3\hpwavip0.dll]
        Dependentfiles: [\\printx0r\print$\W32X86\3\hpwares0.dll]
        Dependentfiles: [\\printx0r\print$\W32X86\3\hpwapre0.exe]
        Dependentfiles: [\\printx0r\print$\W32X86\3\hpwajui0.dll]
        Dependentfiles: [\\printx0r\print$\W32X86\3\hpwaime0.dll]
        Dependentfiles: [\\printx0r\print$\W32X86\3\hpwaflt0.dll]
        Dependentfiles: [\\printx0r\print$\W32X86\3\hpwaeng0.exe]
        Dependentfiles: [\\printx0r\print$\W32X86\3\hpwarpp0.dll]

        Monitorname: []
        Defaultdatatype: []
-----
I should note, that I had to do a
rpcclient -Uroot%secret -c 'setdriver HPColor1700 "HP Color Inkjet CP1700"'
printx0r
because the windows install of the drivers didn't complete.
* I should also note, that I had to take out 'use client driver = yes' in
order to make the setdriver command not have a WERR_ACCESS_DENIED message
(thank you google)
-----
smbd.log
*
[2004/04/17 22:06:27, 0] smbd/connection.c:register_message_flags(220)
  register_message_flags: tdb_fetch failed
[2004/04/17 22:06:36, 1] smbd/ipc.c:api_fd_reply(292)
  api_fd_reply: INVALID PIPE HANDLE: 72fb
[2004/04/17 22:06:37, 1] smbd/ipc.c:api_fd_reply(292)
  api_fd_reply: INVALID PIPE HANDLE: 72fa
[2004/04/17 22:06:37, 0] smbd/connection.c:register_message_flags(220)
  register_message_flags: tdb_fetch failed
[2004/04/17 22:06:40, 0] smbd/connection.c:register_message_flags(220)
  register_message_flags: tdb_fetch failed
[2004/04/17 22:07:53, 0] lib/util_sock.c:get_peer_addr(952)
  getpeername failed. Error was Transport endpoint is not connected
[2004/04/17 22:07:53, 0] lib/util_sock.c:read_socket_data(342)
  read_socket_data: recv failure for 4. Error = Connection reset by peer
[2004/04/17 22:25:44, 0] lib/util_sock.c:get_peer_addr(952)
  getpeername failed. Error was Transport endpoint is not connected
[2004/04/17 22:25:44, 0] lib/util_sock.c:read_socket_data(342)
  read_socket_data: recv failure for 4. Error = Connection reset by peer

-----
I've done allot of searching on each of these errors, but can't find
anything conclusive
* I've done more searching in the last couple days and can't seam to find
any answers. :(
-----
The nmbd.log was just the service starting and stopping.
-----
I've also blown away all of the tbd files in /etc/samba, as well as
/var/cache/samba several times with several config options.
-----
* I'm still hoping (and not hoping) that this is a config or permissions
issue that I've fouled up.

* Thanks in advance for any help or suggestions.