Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 11 Jun 2004 11:09:48 -0400
From:      Bill Moran <wmoran@potentialtech.com>
To:        "admin" <admin@tnn-network.org.tw>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: Problem with samba - windows clients reboot when saving.
Message-ID:  <20040611110948.5ddb4e14.wmoran@potentialtech.com>
In-Reply-To: <000601c44fc4$21de0800$f43c3f3d@louise.com.tw>
References:  <000601c44fc4$21de0800$f43c3f3d@louise.com.tw>

next in thread | previous in thread | raw e-mail | index | archive | help
"admin" <admin@tnn-network.org.tw> wrote:
> hello:
> 
> Freebsd 4.9
> Recent install world and kernel after cvsup
> Samba 2.2.8a
> 
> The clients have files in their home directories and on a common share on
> the BSD box.
> Every so often when they make a change to a file and save it the client
> machine reboots.

You might be better off asking on the Samba mailing list, but I can say two
things:
1) I've never see this happen before.
2) If the client is rebooting, the problem is with the client, not the
   server.

> Clients run win98 and office XP with SP2.

Windows 98 is notoriously buggy.  Although I've never seen it reboot just
because it was having trouble with a network share, I have seen it do all sorts
of other broken things.

However, it sure seems to me that this is a question that you'll get much better
answer on the samba lists than the FreeBSD ones, as it doesn't seem very related
to FreeBSD.

> error for the log.smbd:
>   smbd version 2.2.8a started.
>   Copyright Andrew Tridgell and the Samba Team 1992-2002
> [2003/10/15 08:04:55, 0] lib/util_sock.c:read_data(436)
>   read_data: read failure for 4. Error = Connection reset by peer
> [2003/10/15 08:17:43, 0] lib/util_sock.c:read_socket_with_timeout(300)
>   read_socket_with_timeout: timeout read. read error = Connection reset by
> peer.
> [2003/10/15 08:17:43, 0] smbd/oplock.c:oplock_break(794)
>   oplock_break: receive_smb error (Connection reset by peer)
>   oplock_break failed for file HONDE OORLASTE.doc (dev = 27406, inode =
> 2861321, file_id = 3).
> [2003/10/15 08:17:43, 0] smbd/oplock.c:oplock_break(879)
>   oplock_break: client failure in break - shutting down this smbd.
> [2003/10/15 08:18:11, 0] lib/util_sock.c:read_data(436)
>   read_data: read failure for 4. Error = Connection reset by peer
> [2003/10/15 08:18:15, 0] smbd/oplock.c:request_oplock_break(1011)
>   request_oplock_break: no response received to oplock break request to pid
> 934 on port 1127 for dev = 27406, inode = 2861321, file_id = 3
> [2003/10/15 08:20:21, 0] lib/util_sock.c:read_data(436)
>   read_data: read failure for 4. Error = Connection reset by peer
> [2003/10/15 08:38:18, 0] lib/util_sock.c:read_data(436)
>   read_data: read failure for 4. Error = Connection reset by peer
> [2003/10/15 08:42:08, 0] lib/util_sock.c:read_data(436)
>   read_data: read failure for 4. Error = Connection reset by peer
> [2003/10/15 08:49:09, 0] lib/util_sock.c:read_data(436)
>   read_data: read failure for 4. Error = Connection reset by peer
> 
> There have been a lot more reboots that don't appear in the log - don't know
> why.
> 
> smb.conf :
> # Global parameters
> [global]
>         workgroup = MATZIKAMA
>         netbios name = BSD1
>         encrypt passwords = Yes
>         unix password sync = Yes
>         preferred master = Yes
>         domain master = Yes
>         admin users = %S
>         create mask = 0777
>         directory mask = 0777
> 
> [homes]
>         valid users = %S
>         read only = No
>         browseable = No
> 
> [shared]
>         path = /usr/home/shared
>         read only = No
>         guest ok = Yes
>         vfs object = /usr/local/lib/samba/recycle.so
>         vfs options = /usr/local/etc/recycle.conf.default
> 
> [printers]
>         path = /var/spool/samba
>         guest ok = Yes
>         printable = Yes
>         browseable = No
> [hp5000]
>         comment = Hp 5000 at Amanda
>         path = /var/spool/lpd/hp5000
>         read only = No
>         guest ok = Yes
>         printable = Yes
>         printer name = hp5000
>         oplocks = No
> ..... and six more printers identical to this one.
> 
> The problem appeared about 2 months after i upgraded to 2.2.8a
> 
> I have set the permissions on the users files to 777 and checked ownership
> just to be sure. Still does the same.
> I'm not sure if the problem lies on samba office xp or win98. All antivirus
> software on the clients have been disabled.
> 
> Any help is needed urgently.
> Thanks in advance leon.
> 
> 
> _______________________________________________
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"


-- 
Bill Moran
Potential Technologies
http://www.potentialtech.com



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040611110948.5ddb4e14.wmoran>