samba - Aug 2009 - 20 second delays when accessing Samba on Fedora 11

I had samba running fine on a Fedora 6 machine.  I've upgraded to Fedora 
11 and I'm getting huge delays when first accessing a folder.  With 
Fedora 11 I'm ussing samba-3.3.2-0.33.fc11.i586.

I'm getting about 60+ second delays before being requested to enter my 
username/password.

I've used WireShark and can see

1) Session Setup AndX Request, NTLMSSP_NEGOTIATE
2) 20 seconds pass
3) Session Setup AndX Request, NTLMSSP_AUTH, User: xxx/yyy from my PC
4) 20 seconds passes
5) Session Setup AndX Request, NTLMSSP_AUTH, User: xxx/yyy from my PC
6) again, 20 sec
7) Session Setup AndX Request, NTLMSSP_AUTH, User: xxx/yyy from my PC

Then it asks me for username/password and I can access the share.

There isn't anything unique in my smb.conf compared to before (when it 
worked well with Fedora 6).   Highlights are below.

       workgroup = HOME
         server string = Wonka

         netbios name = Wonka

         interfaces = lo eth1

        security = user
         passdb backend = tdbsam

[homes]
         comment = Home Directories
         browseable = no
         writable = yes

[Miscellaneous]
         path = /media/home/public/Miscellaneous
         writeable = yes
         browseable = yes
         guest ok = no

All my PCs have this problem and they all run XP.

Any thoughts or suggestions are greatly appreciated.

... Altan

On Thu, Aug 06, 2009 at 07:59:34PM -0400, Altan (aol.com)
wrote:
> I had samba running fine on a Fedora 6 machine.  I've upgraded to
Fedora
> 11 and I'm getting huge delays when first accessing a folder.  With  
> Fedora 11 I'm ussing samba-3.3.2-0.33.fc11.i586.
>
> I'm getting about 60+ second delays before being requested to enter my
> username/password.
>
> I've used WireShark and can see
>
> 1) Session Setup AndX Request, NTLMSSP_NEGOTIATE
> 2) 20 seconds pass
> 3) Session Setup AndX Request, NTLMSSP_AUTH, User: xxx/yyy from my PC
> 4) 20 seconds passes
> 5) Session Setup AndX Request, NTLMSSP_AUTH, User: xxx/yyy from my PC
> 6) again, 20 sec
> 7) Session Setup AndX Request, NTLMSSP_AUTH, User: xxx/yyy from my PC
>
> Then it asks me for username/password and I can access the share.
>
> There isn't anything unique in my smb.conf compared to before (when it
> worked well with Fedora 6).   Highlights are below.
Hmmmm. Name resolution lookup timeouts ? Possibly IPv6 related
(just a guess).

Jeremy.

Hi,

Just a thought, have you checked your nic for problems?


I once had the same problem and it turned out to an nic problem.

Cr.

-----Original Message-----
From: "Ryan Novosielski" <novosirj at umdnj.edu>
To: samba at lists.samba.org
Sent: 07/08/09 11:42 PM
Subject: Re: [Samba] 20 second delays when accessing Samba on Fedora 11

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jeremy Allison wrote:
> On Thu, Aug 06, 2009 at 07:59:34PM -0400, Altan (aol.com) wrote:
>> I had samba running fine on a Fedora 6 machine.  I've upgraded to
Fedora
>> 11 and I'm getting huge delays when first accessing a folder.  With
>> Fedora 11 I'm ussing samba-3.3.2-0.33.fc11.i586.
>>
>> I'm getting about 60+ second delays before being requested to enter
my
>> username/password.
>>
>> I've used WireShark and can see
>>
>> 1) Session Setup AndX Request, NTLMSSP_NEGOTIATE
>> 2) 20 seconds pass
>> 3) Session Setup AndX Request, NTLMSSP_AUTH, User: xxx/yyy from my PC
>> 4) 20 seconds passes
>> 5) Session Setup AndX Request, NTLMSSP_AUTH, User: xxx/yyy from my PC
>> 6) again, 20 sec
>> 7) Session Setup AndX Request, NTLMSSP_AUTH, User: xxx/yyy from my PC
>>
>> Then it asks me for username/password and I can access the share.
>>
>> There isn't anything unique in my smb.conf compared to before (when
it
>> worked well with Fedora 6).   Highlights are below.
> 
> Hmmmm. Name resolution lookup timeouts ? Possibly IPv6 related
> (just a guess).
I had a similar odd situation on RedHat at one point (old stuff,
probably 9.x) where for some reason, the upon connecting to the machine,
it would try to contact a former IP address it had for a really long
time, eventually time out, and then connect to the right address. I
never did figure out why it was doing that.

- --
 ---- _  _ _  _ ___  _  _  _
 |Y#| |  | |\/| |  \ |\ |  | |Ryan Novosielski - Systems Programmer II
 |$&| |__| |  | |__/ | \| _| |novosirj at umdnj.edu - 973/972.0922 (2-0922)
 \__/ Univ. of Med. and Dent.|IST/CST - NJMS Medical Science Bldg - C630
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkp8kcEACgkQmb+gadEcsb6WyQCfZCyANeKlHbqT5uQT+vB0GKa1
CxUAn0WdtECMtXPGbtMS8SGzj2Ym2nVB
=0/6n
-----END PGP SIGNATURE-----