Fw: [Samba] Errors in samba 2.2.4

[Rene Dauter]

> Hi,
> the problem Netikular has, i have to on some Windows NT Workstations.
Jeremy
> Allison says, that this is just a network problem, but we can`t change the
> network structure. Can we change something on the clients to resolve this
> problem, like Time Out parameter or something else.
>
> Best regards
> René
>
> On Mon, May 06, 2002 at 01:25:26PM -0600, Netikular wrote:
> >I just downloaded and installed samba 2.2.4 on freebsd 4.5.  I am running
> >this freebsd server as a PDC and file storage server for 4 windows 2000
> >computers and 1 windows 98 (the win98 computer is not part of the Domain)
> >
> >I was wondering if anyone has any suggestions as to what would cause
errors
> >of the following types
> >
> >oplock errors
> >[2002/05/06 12:06:08, 0] smbd/oplock.c:oplock_break(758)
> >   oplock_break: receive_smb error (Connection reset by peer)
> >   oplock_break failed for file Databases/IPV Invent.mdb (dev = 37406,
> >inode
> >= 6578201, file_id = 113).
> >[2002/05/06 12:06:09, 0] smbd/oplock.c:oplock_break(843)
> >   oplock_break: client failure in break - shutting down this smbd.
>
> Yes, this means the client disconnected rather than replying to a
> valid break packet. We don't know why.
>
> >[2002/05/06 12:06:41, 0] smbd/oplock.c:request_oplock_break(981)
> >   request_oplock_break: no response received to oplock break request to
> >pid
> >54124 on port 1886 for dev = 37406, inode = 6578201, file_id = 113
>
> As does this.
>
> >and read failures.
> >[2002/05/06 12:11:01, 0] lib/util_sock.c:read_data(434)
> >   read_data: read failure for 4. Error = Connection reset by peer
> >[2002/05/06 12:37:09, 0] lib/util_sock.c:write_socket_data(497)
> >   write_socket_data: write failure. Error = Broken pipe
> >[2002/05/06 12:37:09, 0] lib/util_sock.c:write_socket(522)
> >   write_socket: Error writing 75 bytes to socket 5: ERRNO = Broken pipe
>
> As do all of the above. The common factor here is "Connection reset by
> peer".
> "Peer" here means your clients - they are dropping the connections. With
> a network sniffer trace you would see this.
>
> I'm thinking of just changing the messages in Samba to say something like
:
>
> "Client XXXX disconnected without warning: Please investigate your network
> or
> client software to determine why it did this".
>
> It looks like you have some network problems.
>
> Regards,
>
> Jeremy Allison,
> Samba Team.
>
>
> _________________________________________________________________
> Senden und empfangen Sie MSN Hotmail über Ihren PocketPC:
> http://pocketpc.msn.de
>
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  http://lists.samba.org/mailman/listinfo/samba
>