Hi!
Correction to my previous message.
If oplocks are turned off, Win does
really not notice any difference, but
Samba writes other error messages in log:
> [2003/08/21 13:04:42, 0]
lib/util_sock.c:write_socket_data(388)
> write_socket_data: write failure. Error =
Connection timed out
> [2003/08
Hi!
Thanks for anserwing so fast.
I agree with your idea that it is the
oplock problem, i.e. that was one
of my first ideas after finding
out the following log lines:
> [2003/08/21 12:41:30, 0]
smbd/oplock.c:request_oplock_break(1023)
> request_oplock_break: no response received to
oplock break
Hi, everybody!
I have 20 WinXP client machines and a sever running
Samba (first try was with 2.2.8, now it's 3.0.0rc1).
If it matters to someone (for statistics, fun or for
understanding the problem), i use Slackware 9.0 Linux,
kernel 2.4.20 on server (and clients are XPpro/SP1,
buld 2600 as far
