Created attachment 8091 [details] samba log for client involved When connecting to a samba share (\\<servername>\Public) running on a Unbuntu 12.04 server running samba 3.6.3, from a client running windows 7, I receive the error : The specified network name is no longer available. On the server, the log shows a samba PANIC: sys-setgroups failed. This problem suddenly showed up roughly 2 weeks ago, so it could be patch related (either windows or samba-side). No config changes were made prior to problem showing up. This is the config for Samba on the server: [global] log file = /var/log/samba/log.%m passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* . obey pam restrictions = yes socket options = TCP_NODELAY map to guest = bad user winbind trusted domains only = no encrypt passwords = yes winbind use default domain = yes passdb backend = tdbsam passwd program = /usr/bin/passwd %u dns proxy = no netbios name = <servername> #real name removed server string = %h server (Samba, Ubuntu) unix password sync = yes workgroup = WORKGROUP os level = 20 syslog = 0 panic action = /usr/share/samba/panic-action %d usershare allow guests = yes max log size = 1000 pam password change = yes [printers] create mask = 0700 comment = All Printers printable = yes guest only = yes public = yes path = /var/spool/samba [print$] guest ok = no comment = Printer Drivers writable = no path = /var/lib/samba/printers [Public] writeable = yes path = /home/Public force group = shrpublic force user = nralbers comment = Public data share guest only = yes public = yes
Okay, did some more research. The problem looks to be kernel-related. Problem exists while i'm running: Linux <servername> 3.5.0-1-generic #1~precise-Ubuntu SMP Mon Jun 25 17:55:09 UTC 2012 i686 i686 i386 GNU/Linux but disappears when I reboot into Linux <servername> 3.2.0-30-generic-pae #48-Ubuntu SMP Fri Aug 24 17:14:09 UTC 2012 i686 i686 i386 GNU/Linux Strangely, it didn't appear immediately after I moved to the 3.5.0-1 kernel. The kernel version i'm using is out of a PPA supplied by Kamal Mostafa (https://launchpad.net/~kamalmostafa/+archive/bufferbloat), and is part of some ongoing research on my part into Bufferbloat prevention. Anyway, i've managed to fix my problem, but this may be of interest for when kernel version 3.5 moves into the mainstream.
not a samba issue