Re: [Samba] Connection reset by peer
Hallo, Sam, Du (persip) meintest am 01.08.08: > i'm getting reports from our users that copying files to/from > location on our samba server results in a error... > * > **read_data: read failure for 4 bytes to client 192.168.0.5 Error = > Connection reset by peer* When does this happen? Most times (or ever) I find this message when the user shuts down his (Windows) machine. Viele Gruesse! Helmut -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Connection reset by peer
What error message do your users get? The error message you mentioned can be ignored. Sometimes I get the same message, but I have no problems with copying files or logging in to my domain. Please attach your smb.conf file, so that we can see where the problem is and not just guess, what the problem can be. Regards Gergely Kiss -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Connection reset by peer
hi all i'm getting reports from our users that copying files to/from location on our samba server results in a error... * **read_data: read failure for 4 bytes to client 192.168.0.5 Error = Connection reset by peer* -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Connection reset by peer
Hi, We are seeing this on our Fedora Core 2 machine when accessing the share from a Windows 2003 box. Any help will be greatly appreciated. This is the smb.conf file : [global] smb passwd file = /etc/samba/smbpasswd passwd program = /usr/bin/passwd %u pam password change = yes obey pam restrictions = yes encrypt passwords = yes unix password sync = no security = share socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 preferred master = no server string = Samba Server load printers = no username map = /etc/samba/user.map log file = /var/log/samba/%m.log name resolve order = host smb ports = 139 [samba] path = /samba writable = yes guest ok = yes guest account = root This is the error : Aug 4 13:34:35 Server nmbd[26773]: Samba name server Server has stopped being a local master browser for workgroup WORKGROUP on subnet 10.140.18.178 Aug 4 13:34:35 Server nmbd[26773]: Aug 4 13:34:35 Server nmbd[26773]: * Aug 4 13:34:52 Server nmbd[26773]: [2006/08/04 13:34:52, 0] nmbd/nmbd_become_lmb.c:become_local_master_stage2(396) Aug 4 13:34:52 Server nmbd[26773]: * Aug 4 13:34:52 Server nmbd[26773]: Aug 4 13:34:52 Server nmbd[26773]: Samba name server Server is now a local master browser for workgroup WORKGROUP on subnet 10.140.18.178 Aug 4 13:34:52 Server nmbd[26773]: Aug 4 13:34:52 Server nmbd[26773]: * Aug 4 13:41:35 Server nmbd[26773]: [2006/08/04 13:41:35, 0] nmbd/nmbd_incomingdgrams.c:process_local_master_announce(311) Aug 4 13:41:35 Server nmbd[26773]: process_local_master_announce: Server Dell1 at IP 10.140.19.48 is announcing itself as a local master browser for workgroup WORKGROUP and we think we are master. Forcing election. Aug 4 13:41:35 Server nmbd[26773]: [2006/08/04 13:41:35, 0] nmbd/nmbd_become_lmb.c:unbecome_local_master_success(149) Aug 4 13:41:35 Server nmbd[26773]: * Aug 4 13:41:35 Server nmbd[26773]: Aug 4 13:41:35 Server nmbd[26773]: Samba name server Server has stopped being a local master browser for workgroup WORKGROUP on subnet 10.140.18.178 Aug 4 13:41:35 Server nmbd[26773]: Aug 4 13:41:35 Server nmbd[26773]: * Aug 4 13:41:53 Server nmbd[26773]: [2006/08/04 13:41:53, 0] nmbd/nmbd_become_lmb.c:become_local_master_stage2(396) Aug 4 13:41:53 Server nmbd[26773]: * Aug 4 13:41:53 Server nmbd[26773]: Aug 4 13:41:53 Server nmbd[26773]: Samba name server Server is now a local master browser for workgroup WORKGROUP on subnet 10.140.18.178 Aug 4 13:41:53 Server nmbd[26773]: Aug 4 13:41:53 Server nmbd[26773]: * Aug 4 14:04:38 Server gdm[1881]: Maximum number of open XDMCP sessions from host :::127.0.0.1 reached Aug 4 14:33:09 Server smbd[31523]: [2006/08/04 14:33:09, 0] lib/util_sock.c:write_socket_data(430) Aug 4 14:33:09 Server smbd[31523]: write_socket_data: write failure. Error = Connection reset by peer Aug 4 14:33:09 Server smbd[31523]: [2006/08/04 14:33:09, 0] lib/util_sock.c:write_socket(455) Aug 4 14:33:09 Server smbd[31523]: write_socket: Error writing 51 bytes to socket 22: ERRNO = Connection reset by peer Aug 4 14:33:09 Server smbd[31523]: [2006/08/04 14:33:09, 0] lib/util_sock.c:send_smb(647) Aug 4 14:33:09 Server smbd[31523]: Error writing 51 bytes to client. -1. (Connection reset by peer) Thanks, Sameer. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Connection reset by peer
Hi all, Well I'm having the following problem : The internet connection in my office is down and after that I am having some problems in my samba. I really don't know if the problems are happening because my internet is down. I am unable to transfer "large" files throught the network. and looking at the log files i receive this message: "Error = Connection reset by peer " A friend told me to put the machine info at /etc/hosts but doesn't seems to help I put the following thing in /etc/hosts : 10.0.0.50 renan renan Thanks all -- Renan Mathias Fernandes Engenharia de Computação - PUC Campinas uin: 735093 mail: [EMAIL PROTECTED] site: http://renan.soulivre.org -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Connection reset by peer
On Wed, Apr 27, 2005 at 10:00:29AM +0200, Annette Bitz wrote: > 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 It means the client (peer) dropped the connection. We (smbd) don't know why. Look at your clients/network hardware etc. Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Connection reset by peer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Annette, maybe you have problems with your network interface card. Try to exchange this part of hardware. Greets, Holger Annette Bitz wrote: | 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 -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCb0j+O0QDuZMdP0sRAhXeAJ9Kh9+ruDFsaOo7JeJa4QvII5iT6wCfQUCE 5TDAhTD1vJv/HIu7O1lTGas= =ua37 -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Connection reset by peer
On Wednesday 27 April 2005 11:00, Annette Bitz wrote: > 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 This means that remote host closed TCP connection by sending a RST packet. Normally, when you, for example, download a file via http, remote host closes connection with FIN when it finished sending all data. -- vda -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] 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 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Connection reset by peer
Hi Tom, This particular server is running samba 3.0.7-1.3E.1 on RH 3.0. The domain is running AD in mixed mode, (I'll include the smb.conf below), and I believe the Windows server is Windows 2003. Our clients are a mix of Win2k and WinXp. The server is running Clearcase and the clients access the Vobs via Samba. They are primarily running snapshot views. We have had several issues come up over the last few weeks, (coincidentally when the domain was migrated to Windows AD). The most recent are intermittent problems when "password server not available" shows up in the logs and these particular errors show up, (connection reset by peer... etc...). We recently received a report from a user that he/she will get incomplete snapshot view updates, and/or the update operation itself runs very slowly. During the incomplete view updates the user will get messages like "can't open input file" from Clearcase. We're thinking that there is some sort of authentication problem happening, however, we haven't been able to determine what has been causing all of these problems which are mainly intermittent. I'm hoping that by understanding what is causing these connections errors we'll get to root cause on the others as well. One thing to note, we are also running Samba 2.2.7a on a few RedHat 9 servers which are also running Clearcase. These servers are experiencing the same exact issues and are getting the same errors... These machines have been running with this config for over 1 year and have not had any problems until recently. [global] workgroup = ICD netbios name = VALHALLA security = domain password server = seneca wins server = 131.101.17.18 131.101.17.61 server string = Linux ClearCase Server %v %h log file = /var/log/samba/%m.log log level = 6 max log size = 4000 username map = /etc/samba/smbusers read raw = no oplocks = no kernel oplocks = no level2 oplocks = no create mask = 0774 directory mask = 0775 map archive = No preserve case = yes dont descend = /view deadtime = 0 strict locking = no domain master = no preferred master = no [vobs] path = /export/vobs browsable = yes writable = yes public = yes comment = "Vobs" csc policy = disable "Thomas M. Skeren III" <[EMAIL PROTECTED]> 12/23/2004 08:39 PM To: [EMAIL PROTECTED] cc: [EMAIL PROTECTED] Subject:Re: [Samba] Connection reset by peer [EMAIL PROTECTED] wrote: What are you doing? What configuration. What network configuration? >Hi, > >We continuously see these errors in our logs. I've done some searches on >this but nothing seems to point to anything specific. > >Any ideas? > >-John > > >Dec 23 20:14:41 valhalla smbd[3574]: [2004/12/23 20:14:41, 0] >lib/util_sock.c:get_peer_addr(1000) >Dec 23 20:14:41 valhalla smbd[3574]: getpeername failed. Error was >Transport endpoint is not connected >Dec 23 20:14:41 valhalla smbd[3574]: [2004/12/23 20:14:41, 0] >lib/util_sock.c:get_peer_addr(1000) >Dec 23 20:14:41 valhalla smbd[3574]: getpeername failed. Error was >Transport endpoint is not connected >Dec 23 20:14:41 valhalla smbd[3574]: [2004/12/23 20:14:41, 0] >lib/util_sock.c:write_socket_data(430) >Dec 23 20:14:41 valhalla smbd[3574]: write_socket_data: write failure. >Error = Connection reset by peer >Dec 23 20:14:41 valhalla smbd[3574]: [2004/12/23 20:14:41, 0] >lib/util_sock.c:write_socket(455) >Dec 23 20:14:41 valhalla smbd[3574]: write_socket: Error writing 4 bytes >to socket 5: ERRNO = Connection reset by peer > > -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Connection reset by peer
[EMAIL PROTECTED] wrote: What are you doing? What configuration. What network configuration? Hi, We continuously see these errors in our logs. I've done some searches on this but nothing seems to point to anything specific. Any ideas? -John Dec 23 20:14:41 valhalla smbd[3574]: [2004/12/23 20:14:41, 0] lib/util_sock.c:get_peer_addr(1000) Dec 23 20:14:41 valhalla smbd[3574]: getpeername failed. Error was Transport endpoint is not connected Dec 23 20:14:41 valhalla smbd[3574]: [2004/12/23 20:14:41, 0] lib/util_sock.c:get_peer_addr(1000) Dec 23 20:14:41 valhalla smbd[3574]: getpeername failed. Error was Transport endpoint is not connected Dec 23 20:14:41 valhalla smbd[3574]: [2004/12/23 20:14:41, 0] lib/util_sock.c:write_socket_data(430) Dec 23 20:14:41 valhalla smbd[3574]: write_socket_data: write failure. Error = Connection reset by peer Dec 23 20:14:41 valhalla smbd[3574]: [2004/12/23 20:14:41, 0] lib/util_sock.c:write_socket(455) Dec 23 20:14:41 valhalla smbd[3574]: write_socket: Error writing 4 bytes to socket 5: ERRNO = Connection reset by peer -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Connection reset by peer
Hi, We continuously see these errors in our logs. I've done some searches on this but nothing seems to point to anything specific. Any ideas? -John Dec 23 20:14:41 valhalla smbd[3574]: [2004/12/23 20:14:41, 0] lib/util_sock.c:get_peer_addr(1000) Dec 23 20:14:41 valhalla smbd[3574]: getpeername failed. Error was Transport endpoint is not connected Dec 23 20:14:41 valhalla smbd[3574]: [2004/12/23 20:14:41, 0] lib/util_sock.c:get_peer_addr(1000) Dec 23 20:14:41 valhalla smbd[3574]: getpeername failed. Error was Transport endpoint is not connected Dec 23 20:14:41 valhalla smbd[3574]: [2004/12/23 20:14:41, 0] lib/util_sock.c:write_socket_data(430) Dec 23 20:14:41 valhalla smbd[3574]: write_socket_data: write failure. Error = Connection reset by peer Dec 23 20:14:41 valhalla smbd[3574]: [2004/12/23 20:14:41, 0] lib/util_sock.c:write_socket(455) Dec 23 20:14:41 valhalla smbd[3574]: write_socket: Error writing 4 bytes to socket 5: ERRNO = Connection reset by peer -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Connection reset by peer / The network is busy
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 server is fairly bare, with just minimal packages installed. It's only use is for file-sharing and one Access database sharing. (Soon it will also host a MySQL database, hence the horsepower.) It is on a Tyan 2880S motherboard with dual Broadcom GbE ethernet cards, TG3 module. Kernel is 2.4.25-K7-SMP custom, Samba is 3.0.2a I went to copy files over from our old server to the new one via the network... System 1 (pdr, Win98SE) Select files, copy, select new directory on new server, paste. Files copy, re-map network drive, everything's happy. System 2 (My computer, Win2k Pro) Same as above. Slower because my laptop is a piece of garbage, but it's always been that way, even copying local to server. System 3 (Server, Win2k Pro) Same as above for "programs" share, used for network copies of various programs we use. (ACT, MS Office, etc.) 5.7GB worth of information. Was doubling as a test to make sure the two systems can see each other, as the old server will be used as a jury-rigged nightly-updated mirror in case of panic. System 4 (lab, Win98SE, Via Rhine II NIC) Same as above. Gets about 1/2 way through copying files (800MB of Excel files), and the following occurs: Client beeps: "Cannot create or replace [filename]: The network is busy. Server log: "[2004/03/26 15:06:23, 0] lib/util_sock.c:read_socket_data(342) read_socket_data: recv failure for 4. Error = Connection reset by peer At which point, the client needs to be completely rebooted before it will re-connect to the server. Added the new server to the WINS list of the client, and started using a domain logon. Error persisted. On this last try, I decided to monitor the progress with smbstatus while the files copied over. First time I ran smbstatus, the client beeped, and the error occured immediately, much sooner in the process than normal. I've tried everything I can think of. We don't have problems of this nature with that system connecting to the old server (Win2k Pro. We were a tiny company then.) I would just break it up into smaller sections, but I would rather fix the problem than workaround if possible. Right now I'm moving over less-used information. However, we are stretching the limits of the old server rapidly, and need to finish the transition soon. The last time I noticed this problem was using Samba 2.999 on Xandros 1.0. Same network, using it as a testbed. Reformatting the system and re-installing Xandros from scratch worked like a charm. Purge / re-install of Samba did not. However, at this point a purge/reinstall of the OS is not an option. Going back to Xandros is also not an option, as it was causing other problems. Also, last time stress-testing Samba by streaming an MP3/OGG playlist would cause this several times a day. I tried the same earlier with no problems from pdr. I'm not ruling out a network problem, but it would be nice to find out more about the specific error so I know where to focus my troubleshooting. ***Begin smb.conf*** [global] workgroup=DM.NET server string=%h server (Samba %v) load printers=no printcap name=cups printing=cups print command=lp -d %p %s; rm %s # invalid users=root log file=/var/log/samba/log.%m max log size= syslog=0 security=USER encrypt passwords=yes socket options=TCP_NODELAY dns proxy=no passwd program=/usr/bin/passwd %u passwd chat=*EntersnewsUNIXspassword:* %nn *RetypesnewsUNIXspassword:* %nn . obey pam restrictions=yes preserve case=yes case sensitive=no short preserve case=yes os level=65 domain master=yes prefered master=yes wins support=yes local master=yes domain logons=yes name resolve order=lmhosts wins bcast host add user script=/usr/sbin/useradd -d /dev/null -g 100 -s /bin/false -M %u veto oplock files=/*.mdb/*.xls/*.mp3/*.ogg/ passdb backend = tdbsam guest username map = /etc/samba/users.map interfaces = eth0 [lab] public=no browseable=yes path=/shared/lab writeable=yes write list=[userlist removed] valid users=[userlist removed] max connections=0 available=yes create mask=0666 directory mask=0777 Chad Vincent Owner RhiannonWEB Phone: 330-283-4681 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba