Hi, I have install Samba 3.0.24-3 on Fedora Core 6 The system is all ok But when I update to Samba 3.0.24-4 by yum. The samba service is show OK. But I can't access my share disk. I have see /var/log/messages Like the follow: Apr 16 11:08:43 fileserver1 smbd[4414]: [2007/04/16 11:08:43, 0] lib/util_sock.c:write_data(562) Apr 16 11:09:47 fileserver1 smbd[4484]: [2007/04/16 11:09:47, 0] lib/util_sock.c:write_data(562) Apr 16 11:09:58 fileserver1 smbd[4502]: [2007/04/16 11:09:58, 0] lib/util_sock.c:write_data(562) Apr 16 11:10:02 fileserver1 smbd[4522]: [2007/04/16 11:10:02, 0] lib/util_sock.c:send_smb(769) Apr 16 11:10:32 fileserver1 smbd[4545]: [2007/04/16 11:10:32, 0] lib/util_sock.c:send_smb(769) Apr 16 11:10:55 fileserver1 smbd[4566]: [2007/04/16 11:10:55, 0] lib/util_sock.c:send_smb(769) Apr 16 11:11:28 fileserver1 nmbd[4614]: [2007/04/16 11:11:28, 0] nmbd/nmbd.c:terminate(58) Apr 16 11:11:28 fileserver1 nmbd[4614]: Got SIGTERM: going down... Apr 16 11:12:05 fileserver1 nmbd[4754]: [2007/04/16 11:12:05, 0] nmbd/nmbd.c:terminate(58) Apr 16 11:12:05 fileserver1 nmbd[4754]: Got SIGTERM: going down... I don't know what is this messages. In my smb.conf #======================= Global Settings ===================================== [global] log file = /var/log/samba/%m.log #display charset = utf-8 #unix charset = utf-8 #dos charset = cp950 template homedir = /home/%D/%U load printers = yes idmap gid = 10000-20000 socket options = TCP_NODELAY SO_SNDBUF=65535 SO_RCVBUF=65535 vfs object = recycle extd_audit vscan-fprotd vscan-oav: config-file = /etc/samba/vscan-fprotd.conf wins server = 192.168.1.202 recycle:keeptree = yes encrypt passwords = yes realm = eta.com.tw max xmit = 65535 nt acl support = yes dns proxy = no cups options = raw netbios name = Fileserver1 server string = FileServer1 idmap uid = 10000-20000 password server = etams001.eta.com.tw winbind enum users = yes workgroup = ETADN001 winbind enum groups = yes os level = 20 security = ads recycle:repository = ../Garbage/%u recycle:versions = yes max log size = 50 I have plugins some VFS 1. Antivirus 2. SambaAudit 3. Recycle And I have login AD Thanks a lot.
Simo, this one is yours.
And I was found error message at /var/log/samba/winbindd.log [2007/04/16 10:45:28, 1] nsswitch/winbindd_group.c:winbindd_getgrnam(259) group winbind in domain FILESERVER1 does not exist [2007/04/16 10:46:20, 1] nsswitch/winbindd.c:main(953) winbindd version 3.0.24-4.fc6 started. Copyright The Samba Team 2000-2004 [2007/04/16 10:50:00, 1] nsswitch/winbindd.c:main(953) winbindd version 3.0.24-4.fc6 started. Copyright The Samba Team 2000-2004 [2007/04/16 10:52:55, 1] nsswitch/winbindd.c:main(953) winbindd version 3.0.24-4.fc6 started. Copyright The Samba Team 2000-2004 [2007/04/16 10:57:58, 1] nsswitch/winbindd.c:main(953) winbindd version 3.0.24-4.fc6 started. Copyright The Samba Team 2000-2004 [2007/04/16 10:59:49, 1] nsswitch/winbindd.c:main(953) winbindd version 3.0.24-4.fc6 started. Copyright The Samba Team 2000-2004 [2007/04/16 11:10:54, 1] nsswitch/winbindd_group.c:winbindd_getgrnam(259) group winbind in domain FILESERVER1 does not exist I don't know why samba 3.0.24-4 have this error [2007/04/16 11:11:05, 1] nsswitch/winbindd.c:main(953) winbindd version 3.0.24-3.fc6 started. Copyright The Samba Team 2000-2004 And 3.0.24-3 have not this error. Thanks a lot.
This is not a samba.org issue (not yet :) See the following link for more details: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=235821
(In reply to comment #3) > This is not a samba.org issue (not yet :) > See the following link for more details: > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=235821 > Hello, You mean I only reboot Windows Client? If I reboot Windows Client. The Windows can access Samba 3.0.24-4. Is all right?