similar to: getpeername failed, Error was Transport endpoint is not connected

Displaying 20 results from an estimated 1000 matches similar to: "getpeername failed, Error was Transport endpoint is not connected"

2004 Oct 05
1
getpeername failed. Error was Transport endpoint is not connected
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.
2018 Feb 02
1
How to trigger a resync of a newly replaced empty brick in replicate config ?
Hi, I simplified the config in my first email, but I actually have 2x4 servers in replicate-distribute with each 4 bricks for 6 of them and 2 bricks for the remaining 2. Full healing will just take ages... for a just single brick to resync ! > gluster v status home volume status home Status of volume: home Gluster process TCP Port RDMA Port Online Pid
2001 Dec 11
0
getpeername failed. Error was Transport endpoint is not connected
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)
2005 Oct 05
2
getpeername failed. Error was Transport endpoint is not connected
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
2011 Jan 14
1
mixing tcp/ip and ib/rdma in distributed replicated volume for disaster recovery.
Hi, we would like to build a gluster storage systems that combines our need for performance with our need for disaster recovery. I saw a couple of posts indicating that this is possible (http://gluster.org/pipermail/gluster-users/2010-February/003862.html) but am not 100% clear if that is possible Let's assume I have a total of 6 storage servers and bricks and want to spread them across 2
2004 Oct 19
1
"getpeername failed. Error was Transport endpoint is not connected", don't solve?
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)
2005 Mar 06
2
Transport endpoint is not connected
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) >
2011 May 10
3
ERROR: -91 after Kernel Upgrade
Hey guys, I have a OCFS2 Cluster mounted at 4 xen-server (gentoo). Today I upgraded the xen-kernel for tests at one server (server2) from 2.6.34-xen to 2.6.38-xen-r1. After reboot the server couldn''t mount the ocsfs2 device anymore. ocfs2-tools version: sys-fs/ocfs2-tools-1.4.3 Modules are loaded and /config type configfs and /dlm type ocfs2_dlmfs are mounted. server2 ~ # mount
2005 Dec 18
3
getpeername failed
Fellows, I need some help regarding this thing!1! I get tons of messages like this ? Can anyone help me with resolving this problem ? Dec 18 13:52:42 constellation smbd[8063]: [2005/12/18 13:52:42, 0] lib/util_sock.c:send_smb(647) Dec 18 13:52:42 constellation smbd[8063]: Error writing 4 bytes to client. -1. (Connection reset by peer) Dec 18 14:00:01 constellation crond(pam_unix)[8126]: session
2010 Sep 08
1
Authentication questions with domain
Hi there. I have a FreeBSD server running Samba 3.3, connected to a domain who's PDC is a MacOS 10.6 server running Samba 3.0.28 (ancient I know). Working all fine, except for one thing I find annoying. MacOS server has a concept of username alias. You can have as many aliases as you want, using any of those aliases are the same as using the primary one. It's rather well implemented in
2005 Aug 24
1
Tr: getpeername failed -> PLEASE HELP
--- 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
2009 May 28
0
Samba getpeername failed. Error was Transport endpoint is not connected
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
2011 Mar 10
1
getpeername failed. Error was Transport endpoint is not connected (3.0.37)
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)
2005 Apr 18
2
"getpeername failed. Error was Transport endpoint is not connected"
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
2010 Oct 28
0
How can I solve this problem that cause"getpeername failed. Error was Transport endpoint is not connected"
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
2011 Feb 18
0
getpeername failed. Error was Transport endpoint is not connected
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
2001 Mar 23
4
getpeername failed
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
2015 Dec 11
2
sshd "getpeername failed: Transport endpoint is not connected" error
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.
2015 Dec 09
2
Fwd: sshd "getpeername failed: Transport endpoint is not connected" error
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
2004 Aug 25
6
sshd 3.9p1 under Reliant Unix 5.45: getpeername: Operation not supported on transport endpoint
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