similar to: recv failure for 4: error = connection reset by peer

Hi! I always get the following messages. What does this mean? smbd[20233]: [2005/04/27 09:58:13, 0] lib/util_sock.c:read_socket_data(384) smbd[20233]: read_socket_data: recv failure for 4. Error = Connection reset by peer Thanks in advance Annette

Hi, I run Samba 2.0.5a on Linux 2.2.12 (Slackware). My clients get an error regularly (Windows95) "Network path not found" and then they lose their connection completely. The server logs the following: [1999/09/07 17:30:01, 1] smbd/service.c:make_connection(521) sbit12 (137.56.40.139) connect to service sbitdata as user sbit (uid=1000, gid=100) (pid 134) [1999/09/07 17:33:10, 0]

Got a wireless A network. 1 client is connected to a wireless access point, which is running WPA-PSK (TKIP) Several times each day, client Windows XP machine loses connection, on the Samba server, log file only shows: [2005/10/19 14:00:53, 0] lib/util_sock.c:read_socket_data(384) read_socket_data: recv failure for 4. Error = Connection reset by peer Other than Samba, which client pc is

Hello all, I'm having troubles with a samba 2.2.2 server (on debian). Some clients are having problems connecting, and are filling the logs with messages like those below. This isn't the first time I've had this problem, nor is it the first site. This is a win98 box I'm having troubles with now - it fails trying to log onto the domain... although I'm fairly sure it affects

Hello, I just upgraded from 2.05a to 2.0.7 on a RH 6.0 system, upgraded one of the workstations to win2k pro, and didn't change anything to my smb.conf.

I recently upgraded my Linux install (Debian potato to woody) and now Samba is no longer playing nice with Windows 2000. I can use smbclient on the samba machine to connect to itself, so at least that's working. The error from Windows is: "The semaphore timeout period has expired.". I deleted the smb.log file at one point in an effort to reset it. I figured it'd be created

Hello, I have a samba server serving som e shares to a heavily loaded web- server. There a four shares fg 60Gb each. Approx. once a day, one of the shares die (it tends to be the one under the harddest strain). The server log says: [2000/05/01 17:59:52, 0] smbd/service.c:make_connection(336) samba logged in as admin user (root privileges) [2000/05/01 17:59:52, 1]

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Setup: Samba 3.0.7-1 on Debian (3.0.9 broke Excel Shared Files, not upgrading unless that bug is squashed, resurrected, re-squashed, burned, etc.) Win2k Pro box running OnStream Echo backup software. Problem: Connection to the share disconnects during backup. Software repeatedly retries last file, fills up tape with partial copies of file,

I?m using SAMBA 3.0.4-6.3E as a PDC. I have Win98, WinNT4 and Win2000 clients successfully joined to the domain. But I can?t get an XP box to join. The XP machine can ?see? shares on the SAMBA PDC but strangely does not show up in network neighbourhood. You can find it if you search for it. The PDC is just using smbpasswd, no LDAP The machine add line in my smb.conf is as follows..... add

On a server that has been running smoothly since it was setup, and with no changes to configurations or network or anything, users cannot save a shared QuickBooks file. they have been regularly using, updating and saving to this file for a few months. All users are able to create and update other files in the same share. I have not confirmed if they are able to create and update new QuickBooks

I am using the defaults that came with the samba RPM package on Mandrake 10.1. For socket options, it has: socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 Is that something that may fix the problem if I change it? Pablo mschwartz@dcscorp.net wrote: >Pablo, you might have incorrectly set some settings in smb.conf. Check >your settings for socket options. I don't mess

Hello I'm working with samba 2.2.8 on Solaris 5.8, and I often have this error: 2004/07/07 15:23:34, 0] lib/util_sock.c:(479) read_socket_data: recv failure for 4. Error = Connection timed out [2004/07/08 00:23:46, 0] lib/util_sock.c:(479) read_socket_data: recv failure for 4. Error = Connection reset by peer This is very bad, because applications running through Samba shares work very

John Wilkes wrote: > I can't get samba to work reliably. Win98 machines can map a network > drive via Samba, but writing large files to the Linux box fails. I get > error messages that all are some variation on this ... > [2000/02/20 22:38:31, 6] lib/util_sock.c:write_socket(560) > write_socket(6,39) wrote 39 > [2000/02/20 22:38:31, 10] lib/util_sock.c:read_socket_data(468)

Hi ! Starting the smbd, I get the following output in samba.log and i cannot connect to samba (from Win95): [1999/10/05 09:47:27, 2] interface.c:(213) Added interface ip=129.103.47.94 bcast=129.103.47.255 nmask=255.255.255.0 [1999/10/05 09:47:27, 1] files.c:(216) file_init: Information only: requested 10000 open files, 1014 are available. [1999/10/05 09:47:27, 2] server.c:(716) Changed

I am having some problems getting a samba server to work with Windows 2000 Active Directory. I am at the point where I can successfully list all users and groups, using the wbinfo command, and was able to join the domain with the net join ads ... command. I can also see the computer in my network neighborhood ... however, when I click on it .. it prompts for a username / password .. and

I have seen posts concerning this in the archives, but with no real solution. I've seen it first-hand twice now. I am running Debian Woody, with us3.samba.org's Samba 3 sources added to my apt-sources. 3.0.2a was the first version of Samba installed. The SMB.conf is used off of a previous "Test" system, then updated to reflect changes in the network as it stands now. The

In problem-fixing, the "nicest" problems are those reproducible on demand. Alas, this one is not nice. System: Samba 2.0.6 on Solaris 2.7 (also see similar on Solaris 2.6). Symptom (user perspective): PC suddenly, spontaneously freezes and eventually the connection times out. Symptom (log file): [2000/02/15 09:27:30, 0] ../lib/util_sock.c:read_socket_data(474)

Hello, I have two error messages on user.log as follow : 1. [2001/11/26 14:41:07, 0] smbd/oplock.c:oplock_break(813) oplock_break: no break received from client within 30 seconds. oplock_break failed for file aa1/EMI/SIGVM00 (dev = 302, inode = 194716). [2001/11/26 14:41:07, 0] smbd/oplock.c:oplock_break(859) oplock_break: client failure in oplock break in file aa1/EMI/SIGVM00 2.

Samba gives read_socket_data: recv failure for 4 when trying to write or read with NT4 WS, why? Samba 2.0.7, NT WS 4.0 sp6, Slackware 7.0 (glibc 2.1.2), linux kernel 2.2.15 with crypto patch patch-int-2.2.14.1. Samba configured/compiled with the following switches: --with-smbmount --with-syslog Most of the time writing to, or copying from samba shares, hangs, then fails. Trying to copy

Using Gentoo with kernel 2.6.1 and 2.6.3 and Samba 2.2.8a and 3.0.2a. Mostly when I transfer large (100+MB) files from a WinXP machine to the Samba server I get the following error: [smbd] lib/util_sock.c:read_socket_data(342)_ [smbd] read_socket_data: recv failure for 34944. Error = Connection reset by peer_ The WinXP machines also say "Delayed write failed. The data has been