Samba

[Peter Quackenbush <pquack@gmail.com>]

I'm having some problems working with Samba.  Here is by /etc/samba/smb.conf

# Samba config file created using SWAT
# from 192.168.0.100 (192.168.0.100)
# Date: 2004/10/04 01:03:28

# Global parameters
[global]
        workgroup = MSHOME
        server string = %h server (Samba %v)
        passdb backend = tdbsam, guest
        passwd program = /usr/bin/passwd %u
        passwd chat = *Enter\snew\sUNIX\spassword:* %n\n
*Retype\snew\sUNIX\spassword:* %n\n .
        syslog = 0
        log file = /var/log/samba/log.%m
        max log size = 1000
        dns proxy = No
        panic action = /usr/share/samba/panic-action %d
        invalid users = root
        unix password sync = yes
        dns proxy = no
        ldap ssl = no
[homes]
        comment = Home Directories
        read only = no
        create mask = 0700
        directory mask = 0700
        browseable = No

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

[print$]
        comment = Printer Drivers
        path = /var/lib/samba/printers

[lp]
        comment = Samsung ML-1430 Series (SPL)
        path = /tmp
        read only = No
        create mask = 0700
        guest ok = Yes
        printable = Yes
        printer name = lp
        use client driver = Yes
        oplocks = No
        share modes = No


Here is tail /var/log/samba/log.nmbd

  Samba name server QUACK-ATTACK has stopped being a local master
browser for workgroup MSHOME on subnet 192.168.0.2

  *****
[2004/10/05 16:49:25, 0] nmbd/nmbd_become_lmb.c:become_local_master_stage2(396)
  *****

  Samba name server QUACK-ATTACK is now a local master browser for
workgroup MSHOME on subnet 192.168.0.2

  *****

And log.smbd
[2004/10/04 00:59:57, 0] smbd/server.c:main(760)
  smbd version 3.0.7-Debian started.
  Copyright Andrew Tridgell and the Samba Team 1992-2004
[2004/10/04 01:04:37, 0] smbd/server.c:main(760)
  smbd version 3.0.7-Debian started.
  Copyright Andrew Tridgell and the Samba Team 1992-2004
[2004/10/05 07:26:24, 0] smbd/server.c:main(760)
  smbd version 3.0.7-Debian started.
  Copyright Andrew Tridgell and the Samba Team 1992-2004


And lastly log.winbindd
[2004/10/04 01:04:45, 1] nsswitch/winbindd_util.c:init_domain_list(327)
  Could not fetch sid for our domain MSHOME
[2004/10/05 07:26:29, 1] nsswitch/winbindd.c:main(854)
  winbindd version 3.0.7-Debian started.
  Copyright The Samba Team 2000-2004
[2004/10/05 07:26:29, 0] nsswitch/winbindd_util.c:winbindd_param_init(560)
  winbindd: idmap uid range missing or invalid
[2004/10/05 07:26:29, 0] nsswitch/winbindd_util.c:winbindd_param_init(561)
  winbindd: cannot continue, exiting.
[2004/10/05 07:26:29, 1] nsswitch/winbindd.c:main(887)
  Could not init idmap -- netlogon proxy only
[2004/10/05 07:26:30, 1] nsswitch/winbindd_util.c:init_domain_list(327)
  Could not fetch sid for our domain MSHOME

Here's the setup.
I have 3 people with 3 windows xp sp2 computers trying to connect to
one server, called quack-attack.  Server is running debian sarge. 
That's samba 3.0.7-1, or whatever the most

Here's the problems. 
1.  Incosistent connections.  I often get the error "\\quack-attack is
not accessible.  You might not have permission to use this network
resource. Contact the administrator of this server to find out if you
have permissions.  Access is denied."  when trying to connect to
quack-attack.  Also note that sometimes, when quack-attack is the smb
network master, I'll get the error as well.  Just with MSHOME, and not
quack-attack.


2.  Printing is slow.  If I try to print a document when problem #1 is
not occuring (about 25% of the time), it a long time to send.  I can
see my network card send away data and I can see the server's card
accept it.  Doing a ifconfig before and after suggests that about 10
megabytes of data are sent, sometimes just to print a plain ascii
document.  If I click on the printer status in windows, it opens the
printer very slowly.  For example, I'll open the printer, about 10
seconds later the printer queue box will open with title saying
"Printer -- Initializing" then "Printer -- Refereshing" and about 10
seconds later, "Printer -- Ready"

Anyone have ideas how to fix this?

Thanks!

-- 
Peter Quackenbush
Welcome thy neighbor int-o thy fallout shelter.  He'll come in handy
if you run out of food.
     --Dean McLaughlin