Hi all, today happened very strange thing to me. I'm running Samba 3.0.1 on Debian. Today users called me that machines with XP has problems to work on the network. I haven't changed configuration for 1 month... Users on XPs can logon into domain, but when they try, after logon, to open ANY share on Samba server, it locks up (explorer has no response] for about 5 minutes and after that it shows the content of that share. When they close window and they open same share again, it opens immediately. When they try open another share on same server it locks up again for 5 minutes and then it normally opens the share. In log.nmbd I see always same errors, when the client machine is locked up: [2004/01/28 02:53:00, 1] nmbd/nmbd_processlogon.c:process_logon_packet(95) process_logon_packet: Logon from 192.168.123.20: code = 0x12 [2004/01/28 02:53:00, 1] nmbd/nmbd_processlogon.c:process_logon_packet(95) process_logon_packet: Logon from 192.168.123.20: code = 0x12 [2004/01/28 02:55:00, 1] nmbd/nmbd_processlogon.c:process_logon_packet(95) process_logon_packet: Logon from 192.168.123.20: code = 0x12 [2004/01/28 02:55:00, 1] nmbd/nmbd_processlogon.c:process_logon_packet(95) process_logon_packet: Logon from 192.168.123.20: code = 0x12 Interesting thing is, that I see same error messages when W2k client is opening share on server, but it's opened immediately. Do you have any idea, why this happens EVEN I haven't touched Samba configuration for a long time??? (I do updating of packages only) My smb.conf: [global] client schannel = no server schannel = no client signing = no server signing = no template primary group = staff unix charset = ISO8859-2 dos charset = CP852 admin users = root bind interfaces only = yes workgroup = BLONDEL server string = Samba load printers = yes printing = cups guest account = nobody log file = /var/log/samba/log.%m max log size = 1000 syslog only = no syslog = 0 security = user encrypt passwords = true passdb backend = smbpasswd socket options = TCP_NODELAY local master = yes os level = 64 domain master = yes preferred master = yes domain logons = yes logon path = \\samba\profiles\%U logon drive = H: logon home = \\samba\%u logon script = logon.bat add user script = /usr/sbin/useradd -d /dev/null -g 100 -s /bin/false -M %u wins support = yes dns proxy = no name resolve order = lmhosts host wins bcast passwd program = /usr/bin/passwd %u passwd chat = *Enter\snew\sUNIX\spassword:* %n\n *Retype\snew\sUNIX\spassword* %n\n . obey pam restrictions = yes Regards, Pavel Flajshans
On Wed, 2004-01-28 at 13:34, Pavel Flajshans wrote:> Hi all, > > today happened very strange thing to me. I'm running Samba 3.0.1 on Debian. > Today users called me that machines with XP has problems to work on the > network. I haven't changed configuration for 1 month... > > Users on XPs can logon into domain, but when they try, after logon, to open > ANY share on Samba server, it locks up (explorer has no response] for about > 5 > minutes and after that it shows the content of that share. When they close > window and they open same share again, it opens immediately. > > When they try open another share on same server it locks up again for 5 > minutes and then it normally opens the share. > > In log.nmbd I see always same errors, when the client machine is locked up: > > [2004/01/28 02:53:00, 1] nmbd/nmbd_processlogon.c:process_logon_packet(95) > process_logon_packet: Logon from 192.168.123.20: code = 0x12 > [2004/01/28 02:53:00, 1] nmbd/nmbd_processlogon.c:process_logon_packet(95) > process_logon_packet: Logon from 192.168.123.20: code = 0x12 > [2004/01/28 02:55:00, 1] nmbd/nmbd_processlogon.c:process_logon_packet(95) > process_logon_packet: Logon from 192.168.123.20: code = 0x12 > [2004/01/28 02:55:00, 1] nmbd/nmbd_processlogon.c:process_logon_packet(95) > process_logon_packet: Logon from 192.168.123.20: code = 0x12This is a perfectly normal packet. I have turned up the debug level in 3.0 cvs.> Interesting thing is, that I see same error messages when W2k client is > opening share on server, but it's opened immediately. > > Do you have any idea, why this happens EVEN I haven't touched Samba > configuration for a long time??? (I do updating of packages only)Did you update your Samba package? This smells like some of our interesting 3.0.1 behaviours in the authentication area. Try 3.0.2rc1 or 3.0.0 again. Andrew Bartlett -- Andrew Bartlett abartlet@pcug.org.au Manager, Authentication Subsystems, Samba Team abartlet@samba.org Student Network Administrator, Hawker College abartlet@hawkerc.net http://samba.org http://build.samba.org http://hawkerc.net -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part Url : http://lists.samba.org/archive/samba/attachments/20040128/e21a3f35/attachment.bin