similar to: getpeername failed

Thanks for suggestion. That was, indeed, a problem on our network. Sorry for bothering you. BTW, "-r" option is not included in a man page, it doesn't seem to have any effect as well. 2015-12-11 5:47 GMT+03:00 Darren Tucker <dtucker at zip.com.au>: > On Wed, Dec 9, 2015 at 7:43 PM, Andrey Klimentev <andrei650816 at gmail.com> wrote: >> Hello, everybody.

I have a similar error, I can us XP workstation ad domain members, and they even use the shares, but two or threes times per day the connection resets, and I have to kill the smbd and start it again (only restart does not work). Take look at my LOG. Any idea? [2005/10/04 11:02:10, 0] lib/util_sock.c:get_peer_addr(1150) getpeername failed. Error was Transport endpoint is not connected [2005/10/04

Mates, I'm trying to solve some log errors I getting. I have samba 3.0.7 installed on Suse 9.0. It has been happening intermittently for several months. I don't know if this is XP client related or what. Any thoughts: The errors are: Feb 9 20:00:33 skyline smbd[14408]: [2005/02/09 20:00:33, 0] lib/util_sock.c:get_peer_addr(1000) Feb 9 20:00:33 skyline smbd[14408]: getpeername

I'm using samba 3.5.6 + PDC and connected to LDAP directory In log level 1 there is many entries like this : Feb 18 18:13:42 samba smbd[21646]: getpeername failed. Error was Transport endpoint is not connected Feb 18 18:13:42 samba smbd[21646]: write_data: write failure in writing to client 0.0.0.0. Error Connection reset by peer Is it a problem ? or just an informative event ? Feb 18

Hello all: When I was send data between two debian 5.0 system in windows network , I will get a error message below: lib/util_sock.c:read_socket_with_timeout(939) lib/util_sock.c:get_peer_addr_internal(1676) getpeername failed. Error was Transport endpoint is not connected read_socket_with_timeout: client 0.0.0.0 read error = No route to host. I try insert "smb ports = 139" to

Good Afternoon, I have Samba 2.2.1a running on a SPARC Solaris 2.7. All of a sudden I'm having a problem with one PC mapping Samba drives. In the log file for this PC I get the following error messages: [2001/12/11 12:47:22, 0] lib/util_sock.c:write_socket(565) write_socket: Error writing 4 bytes to socket 8: ERRNO = Broken pipe [2001/12/11 12:47:22, 0] lib/util_sock.c:send_smb(729)

Hi, I am discovering several error messages from one of our samba servers. Logcheck says: Security Events =-=-=-=-=-=-=-= getpeername failed. Error was Transport endpoint is not connected getpeername failed. Error was Transport endpoint is not connected getpeername failed. Error was Transport endpoint is not connected getpeername failed. Error was Transport endpoint is not connected

Hello, everybody. I've recently encountered a problem with OpenSSH server. Could you help me to troubleshoot it? I've configured 2 IP interfaces[1]: one with a public IP adress and one with a private address. When I connect[2] through the public interface (ens34), SSH works fine, but when I connect[3] through the private interface (ens32), I receive a rather cryptic message on my client

hi folks, i?m using samba 3.0.2a. in my system messages.log are some entrys like this Mar 16 11:59:29 lraprintbak smbd[1857]: =============================================================== Mar 16 11:59:29 lraprintbak smbd[1857]: [2006/03/16 11:59:29, 0] lib/fault.c:fault_report(37) Mar 16 11:59:29 lraprintbak smbd[1857]: INTERNAL ERROR: Signal 11 in pid 1857 (3.0.2a-SUSE) Mar 16 11:59:29

Hello experts After a total panic last weekend, now my LDAP+Samba is working fine, apparently. However, in my syslog, each one minute, still occurring errors like this: Apr 25 08:47:21 myserver smbd[10245]: [ID 702911 daemon.error] [2005/04/25 08:47:21, 0] lib/util_sock.c:set_socket_options(202) Apr 25 08:47:21 myserver smbd[10245]: [ID 702911 daemon.error] Failed to set socket option

Hi, this is my first foray in samba (and newsgroups) so go easy :) I'm trying to map a network drive from a windows 7 pro client to a QNAP NAS: net use s: \\qnap\share I've posted on several forums and got good advice but the problem remains. Rather than repost all the detail, please see my original posts: http://forum.qnap.com/viewtopic.php?f=185&t=74639

Hi All, ? I have a Solaris 10 server (Sun Fire T5520) that has recently been patched with Samba 3.0.37 but is not able to share any drives to Windows clients. Instead, the /var/samba/log/log.smbd is showing the following errros: ???? getpeername failed. Error was Transport endpoint is not connected ??? Denied connection from 0.0.0.0 (0.0.0.0) ??? [2011/03/10 21:10:04, 1] smbd/process.c:(1076)

I get this error message "getpeername failed. Error was Transport endpoint is not connected" in my logs very often. Any ideas how to fix it? Tnxs in advance

--- Bahya NASSR EDDINE <bahya_nassr@yahoo.fr> a ?crit : > Date: Wed, 24 Aug 2005 12:14:37 +0200 (CEST) > De: Bahya NASSR EDDINE <bahya_nassr@yahoo.fr> > ?: samba@lists.samba.org > Objet: [Samba] getpeername failed > > Hello there, > > I am using a samba 3 PDC with OpenLDAP directory. I > can't log on to my samba domain any more from my > windows

Hello, Using Samba 3.014 on SLES9 on a proliant Xeon server. All clients (XP) fixed IP addresses, Ip <> hostname in hosts table. During the boot of a XP client I receive these messages in the log file's Can anybody explain why or what is causing this. Most of the XP clients reporting none of these messages. Jul 6 12:50:24 server4 smbd[27787]: [2005/07/06 12:50:24, 0]

Dear All, Suse 10.2 Samba 3.2.8 How to get rid off the annoying: Samba getpeername failed. Error was Transport endpoint is not connected. I made iptables ?I INPUT 1 ?p tcp ?dport 445 ?j DROP and it finished. But this could not be the solution. Since the newer versions of samba this port makes sense and should be used. Did someone solve this? Greetings Daniel

Hi all, I'm using slackware 10, running samba-3.0.7, OpenLDAP-2.2.17 with ssl, tls and sasl2. While i trying include a workstation windows xp in the samba domain it return this: [2004/10/05 12:51:25, 0] lib/util_sock.c:send_smb(647) Error writing 4 bytes to client. -1. (Connection reset by peer) [2004/10/05 12:51:26, 0] lib/util_sock.c:get_peer_addr(1000) getpeername failed.

Hi all I'm in the prosess of upgrading to a new PDC + LDAP server (bigger and faster machine) replacing an older PIII machine My setup Debian Sarge, custom 2,6 kernel (enabling ext3 ACL's and CIFS support) running samba 3.0.14 Seems to be working fine as PDC + LDAP Master other than the following errors in smbd log... ------------- [2006/01/18 15:43:30, 0]

Hi! Before anything, here is my hardware/software informations : Hardware : -IBM x345, 1 CPU, 1G RAM, IBM ServeRAID controlle -6 HD used with LVM, 2 volume group, 12 logical volumes all running ext3 Software : -RedHat Linux Enterprise AS (Academic) 3.0 update 1 -Kernel 2.4.21-4.0.2.EL -samba-3.0.2-6.3E -Running an apache 2 web server -On normal use, there is only 10-15 computers

I have been getting flooded with the following error messages: smbd[8874]: getpeername failed. Error was Transport endpoint is not connected smbd[8874]: read_socket_data: recv failure for 4. Error = Connection reset by peer I can't figure out how to stop these smb errors short of shutting down samba. I have both an XP Pro and often a Win2000 box on my network and assume they're