[Samba] can't print over samba

[David Banning]

On Mon, Mar 17, 2003 at 10:18:32PM -0500, Joel Hammer wrote:
> You might try using the printing parameter.

Well I goofed. I have tried so many combinations over the last few days,
that the last one did not have it in there. Sorry about that.
Trying it again;

My smb.conf;

[global]
        log file = /var/log/log.%m
        printcap name = /etc/printcap
        max log size = 50
        printer = raw
        interfaces = 192.168.1.1/255.255.255.0
        dns proxy = no
        encrypt passwords = yes
        path = /var/spool/lpd/raw
        server string = Samba Server
        workgroup = workgroup
        socket options = TCP_NODELAY
        load printers = yes
        security = user
        writable = yes
        public = yes

[printers]
   comment = All Printers
   path = /var/spool/samba
   browseable = yes

# Set public = yes to allow user 'guest account' to print
   guest ok = yes
   writeable = yes
   printable = yes

# This one is useful for people to share files
[jim]
   comment = Root directory file space
   path = /usr/jim
   read only = no
   public = yes

[chantelle]
   comment = Root directory file space
   path = /usr/chantelle
   read only = no
   public = yes

My /var/log/messages;

Mar 18 03:16:37 d nmbd[66029]: [2003/03/18 03:16:37, 0] nmbd/nmbd_responserecord
sdb.c:find_response_record(235)
Mar 18 03:16:37 d nmbd[66029]:   find_response_record: response packet id 21230
received with no matching record.
Mar 18 03:16:37 d nmbd[66029]: [2003/03/18 03:16:37, 0] nmbd/nmbd_responserecord
sdb.c:find_response_record(235)
Mar 18 03:16:37 d nmbd[66029]:   find_response_record: response packet id 21231 
received with no matching record.

My log.nmbd;

[2003/03/18 03:16:37, 0] nmbd/nmbd_responserecordsdb.c:find_response_record(235)
  find_response_record: response packet id 21230 received with no matching recor
d.
[2003/03/18 03:16:37, 0] nmbd/nmbd_responserecordsdb.c:find_response_record(235)
  find_response_record: response packet id 21231 received with no matching recor
d.

Could the above be my problem?