Quote:> The problem is with Windows trying to use a protocol or service to access
> the share that Samba doesnt recognise I beleive.
Quote:> In windows XP the easy solution I found was to disable the WebClient service and that fixed it for
> me and numerous others.
True, however OP is using win2000
Quote:> Also make sure you have got the right registry patches applied to you
> windows boxes and you are running that 2.2.8a(latest samba version)
There are no patches needed for windows except for the WinXP signorseal
patch. Win2000 + SP4 is still being, will be ironed out, after all
Win20000 SP4 is only days old.... See Shaun Marolf's post in linux.samba
for more info. Do a google groups search for sp4 profile issue update.
> Give it a go and let us know how things go.
> > Hi Samba fans,
> > Accessing files (both read/write) thru Samba seems to be quite slow.
> > Details:
> > accessing the first file is very slow (20+ sec), after that access other
> > (or the same files) is under 1 sec. If I don't access any of the files for
> > awhile, the problem happens again.
> > My config is:
> > - client is Windows 2000
> > - Samba server is run in Solaris
> > Another possible cause of problem is that all those files live in
> > a single directory; it has 5000+ files there.
> > And I don't think I can change this stupid file structure.
> > My guess is: when the connection is established, things go fast.
> > When cache of the directory is established, things go fast.
> > Question:
> > Could you give me pointers to possible cause of the problem
> > and suggestion to improve it?
See "Big problem" above
Try adding to [global]
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=12000
> > [I have access to SysAdmin of both the client and server sides]
> > Thank in advance.
> > J.
Samba Setup Guide