Slow initial access to shares

[Hall, Ken (ECSS)]

Is there a chance the W95 machines have multiple protocols bound to the MS
Network client service?  I've seen similar problems where the client hunts
for a server using the wrong protocol first, before finally switching to IP
and finding it.

For me, the best results were obtained by removing all network protocols
from the clients except TCP/IP.

> -----Original Message-----
> From:	Frans C.H. Schneider [SMTP:f.schneider at nido.nl]
> Sent:	Friday, October 15, 1999 10:27 AM
> To:	Multiple recipients of list SAMBA
> Subject:	RE: Slow initial access to shares
> 
> > "Frans C.H. Schneider" wrote:
> > >
> > > Hi *
> > >
> > > The first time a share is being accesed on a Samba
> > > server from a W95 machine, it takes some 10 seconds
> > > to open the share. Subsequent accesses to the same share
> > > ot other shares on the server are fast. After not accessing
> > > the server for a while again the first access is really slow.
> >
> > I would guess that the initial slowness is due to
> > authentication occuring in the Session Setup request.
> > Subsequent connections can occur with the context
> > of this session and therefore do no need to be
> > revalidated.
> >
> > Is your server under extreme load?
> >
> > Cheers,
> > jerry
> 
> Load is not the problem. Password level is set to 0 (the default). Also,
> there is no difference between the 80 client network and the 15 client
> network. Because deadtime is set to 0, the context should be kept for
> subsequent accesses (I think).
> 
> Just all smb.conf settings use the default except for security = USER and
> TCP_NODELAY.
> 
> Frans