When a user is not using a samba share, after a while they become
"inactive". When a user wants to access the share again, it takes an
irritating long time before they get access again. The (windows)
application that does the accessing is not responding during that
time. There are no drive letters assigned to the shares in a logon
script. When I do assign a drive letter to the share (in a test
situation), this problem doesn't seem to exist. But how can I prevent
this without assigning drive letters to all the shares?
Here's the global section of my /etc/samba/smb.conf :
[global]
workgroup = SERCOM
server string = Samba Server
encrypt passwords = Yes
map to guest = Bad User
time server = Yes
unix extensions = Yes
socket options = SO_KEEPALIVE IPTOS_LOWDELAY TCP_NODELAY
keepalive = 0
printcap name = CUPS
add user script = /usr/sbin/useradd -c Machine -d /dev/null -s
/bin/false %m$
domain logons = Yes
os level = 65
preferred master = Yes
domain master = Yes
printing = cups
veto files = /*.eml/*.nws/riched20.dll/*.{*}/
I've already experimented with the 'socket options' and 'keepalive'
options, but these don't seem to make any difference...
Met vriendelijke groet / Best regards,
Wilfred van Velzen
--
SERCOM Regeltechniek b.v.
Heereweg 9
2161 AB Lisse
Nederland
+31 (0)252 416530 (voice)
+31 (0)252 419481 (fax)
<http://www.sercom.nl/>
Op al onze offertes, op alle opdrachten aan ons en op alle met ons gesloten
overeenkomsten zijn toepasselijk de METAALUNIEVOORWAARDEN, gedeponeerd ter
Griffie van de Rechtbank te Rotterdam, zoals deze luiden volgens de
laatstelijk aldaar neergelegde tekst. De leveringsvoorwaarden worden u op
verzoek toegezonden.
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
