I solved the problem but I didn't know what caused it. Here is the new smb.conf which works: # Samba config file created using SWAT # from 0.0.0.0 (0.0.0.0) # Date: 2006/04/18 14:30:00
# Global parameters [global] workgroup = HIDRAULICA server string = Server security = SHARE log file = /var/log/samba/%m.log max log size = 50 read only = No guest ok = Yes [server] path = /data/samba [mb] path = /data/mb I suspect 2 things: 1. path = /data/samba, was in the [global] section, insead of [server] section 2. guest account = smbguest, where smbguest user was created by me. On 4/19/06, Istvan Köpe <[EMAIL PROTECTED]> wrote: > I consulted the CentOS support and they don't recommend the upgrade. > Do you have any suggestion to solve this problem with this version? > > Here is my smb.conf: > # Samba config file created using SWAT > # from 0.0.0.0 (0.0.0.0) > # Date: 2006/04/18 14:30:00 > > # Global parameters > [global] > workgroup = HIDRAULICA > server string = Server > security = SHARE > password server = None > guest account = smbguest > log file = /var/log/samba/%m.log > max log size = 50 > socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 > printcap name = /etc/printcap > dns proxy = No > idmap uid = 16777216-33554431 > idmap gid = 16777216-33554431 > path = /data/samba > read only = No > guest ok = Yes > cups options = raw > > [server] > > [mb] > path = /data/mb > > > On 4/19/06, Volker Lendecke <[EMAIL PROTECTED]> wrote: > > On Wed, Apr 19, 2006 at 11:40:56AM +0300, Istvan Köpe wrote: > > > Yum for CentOS doesn't upgrade automatically Samba. The question is if > > > I upgrade manually will it affect the current setup? > > > > 3.0.10 to 3.0.22 is quite a step. Depending on your > > config it might affect you. Maybe you try it first with a > > test server. > > > > Volker > > > > > > > -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba