When adding "hosts allow = 192.168.1." in [global] section of smb.conf, samba server takes 6 seconds before accepting the connexion from any host. I need to wait 6 seconds when typing smb://192.168.1.100/x in nautilus (or \\192.168.1.100\x in windows) before I'm asked for the username and password. "hosts allow" is added in smb.conf when using gsambad 0.2.7 to choose which IP address can access the share. Using samba 2:3.2.3-1ubuntu3 in ubuntu 8.10 :
Created attachment 3763 [details] smb.conf used to reproduce the bug.
I want to add that this bug didn't happen with 3.0.28a-1ubuntu4.4 version of samba in ubuntu 8.04 with the same smb.conf file, so it looks like a regression.
Please upload a debug level 10 log of smbd showing this timeout
Created attachment 3765 [details] log.smbd
Created attachment 3766 [details] log.zxz-desktop
Created attachment 3767 [details] log.192.168.1.100
I attached smbd.log in level 10 mode with two other logs that appeared when I reproduce the timeout bug.
Ok, nothing obvious. Next idea would be that we do something IPv6y with DNS that takes longer than the IPv4 only stuff in your 3.0 setup did. You might want to look at network sniffs. Volker
Mmh, I'm not sure that I would have necessary skill to do this, unless there is some tutorial to help me giving you the necessary information. I also found that changing "hosts allow = 192.168.1." to "hosts allow = 192.168.1.100" removes the timeout problem. The same apply if you use another IP, 127.0.0. and 127.0.0.1 for localhost, as an example. I tested this on one machine and one virtual machine.
Volker, can we close this one?
oxmosys, information on how to create network sniffs can be found under http://wiki.samba.org/index.php/Capture_Packets We'll wait a couple of days for sniffs, and then close the report bug. Volker
This bug can be closed, I'm not able to reproduce this bug anymore with samba 2:3.3.2-1ubuntu3, not even with my old router on which I reproduced the bug in the past. Thanks!