similar to: getpeername failed. Error was Transport endpoint is not connected (3.0.37)

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

Hi All, Samba 3.0.37 is working on my Solaris 10 (Sun Fire T5520) Sparc server but /var/samba/log/smbd.log displayed the following error: $ tail -f log.smbd smbd version 3.0.37 started. Copyright Andrew Tridgell and the Samba Team 1992-2009 [2011/03/15 11:04:44, 0] auth/auth_util.c:(844) create_builtin_administrators: Failed to create Administrators [2011/03/15 11:04:44, 0]

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

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

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

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]

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 using Samba 3.0.7, OpenLDAP 2.2.17, smbldap-tools-0.8.5 It has been configured pdc with tls. tls work fine: ldapsearch -x -ZZ -h ldap.domain.com.br -D cn=suport,dc=domain,dc=com,dc=br -L -W ... ... # numResponses: 20 # numEntries: 19 my user has been found and accept password in the ldap root@terra:~# id fernando.ribeiro uid=1000(fernando.ribeiro)

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)

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

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

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.

Hello, I tried to google this, but haven't found anything really helpful so far. I get stuff like this at one Samba-3.0.9-Domain-Member-Server: > [2005/03/06 13:30:47, 1] smbd/service.c:make_connection_snum(647) > fre2003 (192.168.86.11) connect to service users initially as user fre (uid=1006, gid=1000) (pid 31447) > [2005/03/06 13:31:57, 1] smbd/service.c:close_cnum(835) >

Hi, I running samba 3.0.13 on RH9, and share a folder in a mix network workstations (W2k, DOS, Win98SE, NT4) and I have set following smb.conf file: netbios name = NETBIOSNAME os level = 16 wins server = 10.90.17.80 socket options = IPTOS_LOWDELAY TCP_NODELAY SO_KEEPALIVE workgroup = DOMAIN realm = DOMAIN.COM security = ADS password server

The following is special to sshd 3.9p1 under ReliantUnix 5.45. It does not occur under ReliantUnix 5.43 nor under Solaris 5.8: `pwd`/sshd-3.9 -e -D -d -d -d Now connecting from outside [...] debug1: inetd sockets after dupping: 3, 3 debug1: get_port() calls get_sock_port(3) debug1: getpeername failed: Operation not supported on transport endpoint lsof proves FD 3 is an established TCP

Hello All I used to back up a Mssql database (about 55GB) to a samba share without any problems. The samba server "Server-A" was running version 3.4.7 We just got one of those "Netgear ReadyNas3200" things and I tried to backup up to a share there which sometimes works and sometimes not in wich case I get the following error: ----------------snip--------------- [2010/10/08

Well, I WAS puzzled by this persistent error. Then I stumbled onto something and I might have fixed it. It looks like with an XP client, XP might be trying to renegotiate which port to talk (445 or 139) over at the start of every transaction. Whichever one answers first is used for the rest of the transfer. I added this to smb.conf and restarted samba: smb ports = 139 I can't tell if

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

Hi, I got no replies to my last post "win 7 client can't map drive: getpeername failed" Anyway I've dug a little deeper on the server side by setting log level 10 and found the error: "Transport endpoint is not connected" Basically I compared the logs (several thousand lines!) from two windows 7 clients, one of which always works (the good client) and one which

Hello, I use SAMBA under OpenBSD 2.8. When the clients log in some times they have a reject : Authentificate Failure... And in the log we can observe the same time : getpeername failed. Error was Socket is not connected ? Can somebody help me please ? Thanks -------------- next part -------------- HTML attachment scrubbed and removed