[Samba] Slow listing of mapped drives in Explorer

[tim at ccmp.ox.ac.uk]

Thanks for the suggestion Dennis, but surely this only affects the server
service on the Windows clients. We need to stop our v3.0.24 SAMBA server
disconnecting clients so quickly. It shouldn't require a client-side fix
for what seems to be an smbd issue on the server.

Perhaps Debian have compiled in a different auto-disconnect behaviour in
their 3.0.24 'stable' release?

I'm considering using the 3.2.3 SAMBA package from Debian 'testing' but
would like to know if the premature auto-disconnect has been fixed before
trying it. Can anyone comment?

Tim

> Perhaps on your Windows clients, set the Autodiscconect to -1 (never
> disconnect)
>
> At a command prompt type:
> "net config server" to see the current setting.
> 15 minutes is the default
>
> To set it to never disconnect:
> "net config server /autodisconnect:-1"
>
> Dennis
>
>> -----Original Message-----
>> From: samba-bounces+dmcleod=foranyauto.com at lists.samba.org
>> [mailto:samba-bounces+dmcleod=foranyauto.com at lists.samba.org]
>> On Behalf Of tim at ccmp.ox.ac.uk
>> Sent: Wednesday, November 05, 2008 7:43 AM
>> To: samba at lists.samba.org
>> Subject: [Samba] Slow listing of mapped drives in Explorer
>>
>> We recently moved our Linux file servers from Debian Woody to
>> Debian Etch (v4.0r3). We use the current stable Debian Samba
>> package which is version 3.0.24.
>>
>> Since moving to this Samba version from 2.2.8a-0.1 we see
>> that Windows clients are very slow to list the 5 network
>> drives mapped by our domain login script in Explorer or "My
>> Computer". It can take 10 seconds or so before the drives
>> appear and Explorer starts responding again.
>>
>> Interestingly, if the clients already have a file or
>> directory open on these mapped drives then the problem goes
>> away and drive listing is instantaneous.
>>
>> There appears to be a change in default Samba behaviour which
>> results in client connections being dropped after a few
>> seconds by version 3.0.24 servers. The older Samba 2 servers
>> maintained client connections indefinitley and this gave much
>> better explorer response times.
>>
>> Can I get Samba 3.0.24 to maintain client connections ?
>>
>> I've tried setting:
>>      deadtime = 0
>> in smb.conf but this makes no difference.
>>
>> Our smb.conf file is very simple and is included below for
>> reference. I'd be VERY grateful for any suggestions as this
>> explorer lag is frustrating to our users and spoils an
>> otherwise flawless Samba migration.
>>
>> Thanks guys,
>>
>> Tim
>>
>> [global]
>>         workgroup = OURDOMAIN
>>         netbios name = FS1
>>         security = SERVER
>>         encrypt passwords = true
>>         password server = 129.67.44.5 129.67.44.6
>>         hosts allow = localhost, 129.67.44.0/255.255.252.0
>>         wins server = 129.67.44.5 129.67.44.6
>>
>> [homes]
>>         comment = Home Directories
>>         browseable = no
>>         writable = yes
>>         valid users = %S
>>
>> [groups]
>>         comment = Group Files
>>         path = /groups
>>         writable = yes
>>         public = no
>>         force create mode = 0660
>>         force directory mode = 0770
>>
>> [Distrib]
>>         comment = Distributed Software and Files
>>         path = /distrib
>>         writable = yes
>>         public = no
>>
>> [Temp]
>>         comment = Temporary Data Files
>>         path = /temp
>>         writable = yes
>>         public = no
>>         force create mode = 0666
>>         force directory mode = 0777
>>
>>
>>
>> --
>> To unsubscribe from this list go to the following URL and read the
>> instructions:  https://lists.samba.org/mailman/listinfo/samba
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/listinfo/samba
>