[Samba] Network lockups with win98 [&winxp] and samba 3

[Gary Newcombe]

OK, added;

use sendfile = no

to the config.

As an addition to this, it appears that one of the XP counter machines also
locked up this morning. I don't have any more info until I get to the store,
but I'm guessing that the BM DOS software is getting a write lock on
something and not releasing the file properly causing the others to wait for
the file to available again.

Thing is, are are no errors in the samba logs anymore if I grep error apart
from the

log.robyn:  check_ntlm_password:  Authentication for user [nobody] ->
[nobody] FAILED with error NT_STATUS_NO_SUCH_USER

Which I'm assuming is not connected with this file locking or network issue.

Any ideas?

Gary 

-----Original Message-----
From: Jeremy Allison [mailto:jra at samba.org] 
Sent: Friday, 4 August 2006 3:26 AM
To: Gary Newcombe
Cc: samba at lists.samba.org
Subject: Re: [Samba] Network lockups with win98 and samba 3

On Thu, Aug 03, 2006 at 11:26:19PM +1000, Gary Newcombe wrote:
> Hi all,
>  
> This is a new install on a network comprised of win98 and xp machines. I'm
a
> relative newbie to samba and getting some errors and problems. I would
much
> appreciate some advice on my setup.
>  
> The setup is samba-3.0.23,1 running on FreeBSD 6.1-STABLE as a windows
> server replacement and with clients mostly running dos POS software on
win98
> machines and other dos and windows software on win98 and xp machines - no
> windows servers.
>  
> As there was no real user/password security in the place, I tried to set
up
> samba using nobody/anon access as much as possible so that we could just
> drop the server in. The windows machines are all set up to use the samba
> server for wins resolution through dhcp as well as dns etc.
>  
> The main problem is that the windows 98 machines keep hard locking and
need
> a hard reset (usually) to get the network back. To begin with, I had
oplocks
> set to default on. The winxp machines were ok but the win98 machines were
> locking every 3 to 4 transactions. They would also freeze after an
extended
> period left idle. This is also after updating them all. Disabling oplocks
> seems to have helped, but there are still problems, mostly like the
examples
> following.
>  
> Any comments and suggestions much appreciated.

Try turning off sendfile. We should detect a Win9x client and
not use sendfile, but it won't hurt to be sure.

Jeremy.