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. The same thing happens on a network (80 users) running Samba 2.0.4b server under HPUX 10.20 and two Samba 2.0.3 servers on Linux 2.0.3(2/6) and another network (15 users) with a single 2.0.3 Samba server on Linux 2.2.6. Accessing a Samba server with smbclient seems not to have this problem. W95 machines logon to the network with the 'client for microsoft networks' logon. I did log a trace (loglevel 4, not included with this message) of the initial opening of a share and a subsequent access but can not make much of it. I would appreciate some advise very much, Frans -- Frans C. H. Schneider <mailto:f.schneider@nido.nl> NIDO Universal Machines BV <http://www.nido.nl> Industriestraat 34 <mailto:info@nido.nl> PO Box 30 tel. +31 (0) 548 370 000 7450 AA Holten fax +31 (0) 548 370 233 the Netherlands
"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 ________________________________________________________________________ Gerald ( Jerry ) Carter Engineering Network Services Auburn University jerry@eng.auburn.edu http://www.eng.auburn.edu/users/cartegw "...a hundred billion castaways looking for a home." - Sting "Message in a Bottle" ( 1979 )
> "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, > jerryLoad 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
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@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