Prev: Upgrading 3.2.15 to 3.3.12 sernet package on opensuse 10.2
Next: Winbind is kill me too
From: Todd And Margo Chester on 11 Apr 2010 23:50
Hi All,

I am using CentOS 5.4 (Old-Out-Of-Date) and

$ rpm -qa samba\*
samba-client-3.0.33-3.15.el5_4.1
samba-common-3.0.33-3.15.el5_4.1
samba-3.0.33-3.15.el5_4.1

On Thursday, at a customer's site, I did my
CentOS updates and got the above sort-of-new
version of Samba.

Problem: when CentOS booted back up, suddenly
the only thing anyone could get into was their
"homes" share.

If you browsed over to the server, you could
see all the shares, but if you selected any one
of the shares, except your "homes" share, you
got told that the share did not exist.

This affected all my Windows client and both
my Linux clients (cifs).

To workaround the problem, I stopped winbind
(/etc/rc.d/init.d/winbind stop), and everyone
was able to access network shares again.
As soon as winbind started back up, you were
back to only being able to browse your homes
share.

If power goes out and the server reboots, winbind
will restart and I will be dead meat.

Do I even need winbind? Anyone know how to
permanently fix this? I have access to the prior
build of Samba. Would it be best to just revert
to it?

Many thanks,
-T

--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
 | 
Pages: 1
Prev: Upgrading 3.2.15 to 3.3.12 sernet package on opensuse 10.2
Next: Winbind is kill me too