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

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

2002 May 23
0
Semaphore Timeout on from Win2K to Samba
I have been using Samba w/out any problems what so ever for the longest time, but today, I cannot connect to the linux box (shows up in network neighborhood as 'LINUXSERVER'), but when I try to connect from a win2K machine (which normally connects w/NO problems). Here is the output from /var/log/messages (appears the problem is in smbd) May 23 11:34:14 fileserver nmbd[1423]: [2002/05/23
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.
2002 Nov 23
2
The smbd ran away with the spoon...
It seems that my smbd process got fuxed somehow. It appears to have take up all the file handles, and there were over 130 smbd processes running on the system. I'm not entirely sure what happened. My first thought is that something bad happened between the server and the Windows client that's running Kaza (with a couple hundred mid-download files) and it just spiraled out of control,
2005 Jul 06
1
getpeername failed, Error was Transport endpoint is not connected
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]
2003 Apr 12
1
Client Disconnects
Hi, I'm running samba 2.2.7 on redhat advanced server with approximately 40 win2k clients and having a serious problem with the clients. Intermittently the clients will lose their connection to the server for approximately 30 seconds. It's like the socket connection is being reset or something. Here's a sample output from a client log file: [2003/04/12 15:13:08, 0]
2003 Dec 15
0
Samba 3.0 ACL, Windows Credentials
This is probably a hot topic, and if this has been beaten to the ground, forgive me. I'm not a regular part of the Samba community. Although I have been using Samba for years, I now have to use it in a corporate environment utilizing some of it's more modern features. Let me just say, that it's been several hours of testing/troubleshooting to get where I am now. (And I don't
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
2008 Oct 13
1
Server Maps by IP but not by Name for Domain Users
Hey all, I've got an issue with my Samba server. I can't seem to get file shares to map using Server Name, but I can get them to map using IP Address. Here is my smb.conf: [global] workgroup = ADMIN server string = Snap Server timestamp logs = yes dos filetimes = yes dos filemode = yes inherit acls = yes name cache timeout = 0 winbind uid = 101-6000000 winbind gid =
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 Feb 10
2
smb log error-Transport end point/getpeername
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
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) >
2001 Dec 13
4
Severe problem with Samba
Dear All, we are experiencing severe problems with Samba 2.2.0 (with quota support) running on a dual processor (400MHz) Sun E450 running Solaris 2.7. This is used as a central file server for student diskspace, accessed by approx 1200 PCs running NT 4. Up until recently we experienced some, what we assume to be, loading issues with connections during the middle of the day being slow.
2003 Dec 08
0
is the domain-name in smb.conf case-sensitive?
hi list, i try since weeks to authenticate my linux-clients against my samba-server. This works very fine with 2 windoze-cliens. but i still cannot authenticate with my linux-clients. i am @office now, thats wy i ask instead to test: i heard, winbind is used to authenticate linux-clients against the samba-server. the wbinfo -u gives me back: DOMAIN-user (i use the minus as separator) so i
2003 Oct 31
1
What may be causing these errors?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 knorr smbd[5439]: [2003/10/31 10:27:02, 0] lib/util_sock.c:get_socket_addr(919) knorr smbd[5439]: getpeername failed. Error was Transport endpoint is not connected knorr smbd[5439]: [2003/10/31 10:27:02, 0] lib/util_sock.c:write_socket_data(388) knorr smbd[5439]: write_socket_data: write failure. Error = Connection reset by peer knorr smbd[5439]:
2003 Jul 17
1
write_socket: Error writing 4 bytes to socket 5: ERRNO =Connection reset by peer
Hi Kristis, Kristis Makris wrote on Friday, 18 July 2003 9:19 a.m.: > [2003/07/17 12:16:06, 0] lib/util_sock.c:get_socket_addr(900) > getpeername failed. Error was Transport endpoint is not connected > [2003/07/17 12:16:06, 0] lib/util_sock.c:write_socket_data(388) > write_socket_data: write failure. Error = Connection reset by peer > [2003/07/17 12:16:06, 0]
2006 Mar 14
1
Transport endpoint not connected
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
2001 Feb 12
0
Transport endpoint is not connected
I administer Samba 2.0.7 on Debian Linux (kernel 2.2.17, libc6 2.2). When trying to mount samba shares from Windows 98 workstations sometime the process failed with error message: [...] [2001/02/12 17:32:21, 1] smbd/server.c:main(641) smbd version 2.0.7 started. Copyright Andrew Tridgell 1992-1998 [2001/02/12 17:32:21, 1] smbd/files.c:file_init(216) file_init: Information only: requested
2004 Jan 27
1
Lots of errors
My log files are getting quite big because of all the errors I get in a day. Here is a snipet: Jan 27 10:03:06 localhost smbd[17694]: [2004/01/27 10:03:06, 0] lib/util_sock.c:get_socket_addr(919) Jan 27 10:03:06 localhost smbd[17694]: getpeername failed. Error was Transport endpoint is not connected Jan 27 10:03:06 localhost smbd[17694]: [2004/01/27 10:03:06, 0]
2003 Jan 14
0
Broken pipes
Using Samba 2.2.7a on FreeBSD 4.7-STABLE. #uname -a FreeBSD fileserver1.smartrafficenter.net 4.7-STABLE FreeBSD 4.7-STABLE #0: Mon Dec 16 19:41:03 EST 2002 toor@fileserver1.smartrafficenter.net:/usr/obj/usr/src/sys/FILESERVER1 i386 All day long, constantly, I get the following messages in syslog: Jan 14 13:37:55 fileserver1 smbd[57969]: [2003/01/14 13:37:55, 0]
2003 Jan 20
0
Syslog error messages
Using Samba 2.2.7a on FreeBSD 4.7-STABLE. #uname -a FreeBSD fileserver1.smartrafficenter.net 4.7-STABLE FreeBSD 4.7-STABLE #0: Mon Dec 16 19:41:03 EST 2002 +toor@fileserver1.smartrafficenter.net:/usr/obj/usr/src/sys/FILESERVER1 i386 All day long, constantly, I get the following messages in syslog: Jan 14 13:37:55 fileserver1 smbd[57969]: [2003/01/14 13:37:55, 0]