Re: [Samba] getpeername failed error when signedcommunicationspolicy enabled
On 12/19/2011 02:05 PM, Jeremy Allison wrote: On Fri, Dec 16, 2011 at 02:00:17PM -0500, Allen Chen wrote: I have the same message in samba log file, even though I set up log level = 0. My Samba 3.4.5 PDC is listening on both ports 139 and 445 under CentOS 5.6 32bits. Here is the message: [2011/10/26 16:02:05, 0] lib/util_sock.c:539(read_fd_with_timeout) [2011/10/26 16:02:05, 0] lib/util_sock.c:1491(get_peer_addr_internal) getpeername failed. Error was Transport endpoint is not connected read_fd_with_timeout: client 0.0.0.0 read error = Connection reset by peer. [2011/10/26 16:02:05, 0] lib/util_sock.c:1491(get_peer_addr_internal) getpeername failed. Error was Transport endpoint is not connected [2011/10/26 16:02:05, 0] lib/util_sock.c:1491(get_peer_addr_internal) getpeername failed. Error was Transport endpoint is not connected I have lots of the same messages in samba log file(exactly the same as above). I use compiled samba 3.4.5 PDC on CentOS 5.6 32bit with 200 XP clients. I googled and try to fix it without success. The good thing is that nobody complains. We're going to need debug level 10 log output to even begin to look into this. Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] getpeername failed error when signed communications policy enabled
We've found a solution for this and it turns out to be a setting at the Windows end: If you add the value AllowGuestAuthWhenSigningRequired = 1 to the registry key HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanWorkstation\Param eters and then reboot the machine it all seems to work. Apparently this is new behaviour in Windows 2008: http://social.msdn.microsoft.com/Forums/en/os_fileservices/thread/832d395b-6 e6f-4658-8dbb-120138a4cd7c David -Original Message- From: Jeremy Allison [mailto:j...@samba.org] Sent: 15 December 2011 18:06 To: Hilton, David Cc: Jeremy Allison; samba@lists.samba.org Subject: Re: [Samba] getpeername failed error when signed communications policy enabled On Thu, Dec 15, 2011 at 09:10:11AM +, Hilton, David wrote: No, the only error that we see is the getpeername failed error in the Samba log for the client machine that is trying to print the job. Then I doubt it's a signing issue (which makes it strange). What does a debug level 10 say ? Jeremy. smime.p7s Description: S/MIME cryptographic signature -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] getpeername failed error when signed communications policy enabled
On Wed, Jan 04, 2012 at 10:02:45AM +, Hilton, David wrote: We've found a solution for this and it turns out to be a setting at the Windows end: If you add the value AllowGuestAuthWhenSigningRequired = 1 to the registry key HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanWorkstation\Param eters and then reboot the machine it all seems to work. Apparently this is new behaviour in Windows 2008: http://social.msdn.microsoft.com/Forums/en/os_fileservices/thread/832d395b-6 e6f-4658-8dbb-120138a4cd7c Oh thanks for figuring that out - much appreciated ! Looks like it's actually a Windows bug then. Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] getpeername failed error when signed communications policy enabled
No, the only error that we see is the getpeername failed error in the Samba log for the client machine that is trying to print the job. David. -Original Message- From: Jeremy Allison [mailto:j...@samba.org] Sent: 14 December 2011 22:12 To: Hilton, David Cc: samba@lists.samba.org Subject: Re: [Samba] getpeername failed error when signed communications policy enabled On Wed, Dec 07, 2011 at 11:01:50AM +, Hilton, David wrote: Hi, I'm looking for help with an issue that we are seeing with the following configuration: We are using Samba (3.5.12-72.fc15) to share out CUPS printers from a Fedora 15 machine. However, a requirement of the system is that these printers are not directly visible from client systems (Windows 7 SP1 32-bit), so instead we are sharing them out from a Windows print server (Windows 2008 R2 SP1). So the clients connect to print queues on the Windows print server, which in turn forwards the print jobs on to CUPS. The issue we are seeing occurs when a policy change is made on the Windows 2008 R2 print server. If the Microsoft network client: Digitally sign communications (always) policy setting is enabled, we see the following behaviour: - Applications running on the print server can print normally. - Applications running on client machines fail to print. When a print job fails we see the following in the samba log for the client machine: [2011/12/07 10:43:23.381798, 2] auth/auth.c:304(check_ntlm_password) check_ntlm_password: authentication for user [XXX] - [XXX] - [XXX] succeeded [2011/12/07 10:43:39.760399, 0] lib/util_sock.c:474(read_fd_with_timeout) [2011/12/07 10:43:39.760476, 0] lib/util_sock.c:1441(get_peer_addr_internal) getpeername failed. Error was Transport endpoint is not connected read_fd_with_timeout: client 0.0.0.0 read error = Connection reset by peer. The smb.conf file that we are using is as follows: [global] #--authconfig--start-line-- # Generated by authconfig on 2011/12/05 17:22:13 # DO NOT EDIT THIS SECTION (delimited by --start-line--/--end-line--) # Any modification may be deleted or altered by authconfig in future workgroup = LOW password server = LOWDC security = user idmap uid = 16777216-33554431 idmap gid = 16777216-33554431 template shell = /bin/false winbind use default domain = false winbind offline logon = false server signing = auto log level = 2 log file = /var/log/samba.log.%m max log size = 50 debug timestamp = yes #--authconfig--end-line-- load printers = yes printing = cups printcap name = cups [printers] comment = All Printers path = /var/spool/samba browseable = no guest ok = yes writable = no printable = yes printer admin = root, @ntadmins, @smbprintadm use client driver = yes If the Microsoft network client: Digitally sign communications (always) setting is disabled it all works OK, but disabling this policy setting is not an allowed option at present. That sounds like a signing error - do you see such in the Samba logs ? Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] getpeername failed error when signed communicationspolicy enabled
On Fri, Dec 16, 2011 at 02:00:17PM -0500, Allen Chen wrote: I have the same message in samba log file, even though I set up log level = 0. My Samba 3.4.5 PDC is listening on both ports 139 and 445 under CentOS 5.6 32bits. Here is the message: [2011/10/26 16:02:05, 0] lib/util_sock.c:539(read_fd_with_timeout) [2011/10/26 16:02:05, 0] lib/util_sock.c:1491(get_peer_addr_internal) getpeername failed. Error was Transport endpoint is not connected read_fd_with_timeout: client 0.0.0.0 read error = Connection reset by peer. [2011/10/26 16:02:05, 0] lib/util_sock.c:1491(get_peer_addr_internal) getpeername failed. Error was Transport endpoint is not connected [2011/10/26 16:02:05, 0] lib/util_sock.c:1491(get_peer_addr_internal) getpeername failed. Error was Transport endpoint is not connected We're going to need debug level 10 log output to even begin to look into this. Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] getpeername failed error when signed communicationspolicy enabled
Jeremy Allison wrote: On Wed, Dec 07, 2011 at 11:01:50AM +, Hilton, David wrote: Hi, I'm looking for help with an issue that we are seeing with the following configuration: We are using Samba (3.5.12-72.fc15) to share out CUPS printers from a Fedora 15 machine. However, a requirement of the system is that these printers are not directly visible from client systems (Windows 7 SP1 32-bit), so instead we are sharing them out from a Windows print server (Windows 2008 R2 SP1). So the clients connect to print queues on the Windows print server, which in turn forwards the print jobs on to CUPS. The issue we are seeing occurs when a policy change is made on the Windows 2008 R2 print server. If the Microsoft network client: Digitally sign communications (always) policy setting is enabled, we see the following behaviour: - Applications running on the print server can print normally. - Applications running on client machines fail to print. When a print job fails we see the following in the samba log for the client machine: [2011/12/07 10:43:23.381798, 2] auth/auth.c:304(check_ntlm_password) check_ntlm_password: authentication for user [XXX] - [XXX] - [XXX] succeeded [2011/12/07 10:43:39.760399, 0] lib/util_sock.c:474(read_fd_with_timeout) [2011/12/07 10:43:39.760476, 0] lib/util_sock.c:1441(get_peer_addr_internal) getpeername failed. Error was Transport endpoint is not connected read_fd_with_timeout: client 0.0.0.0 read error = Connection reset by peer. The smb.conf file that we are using is as follows: [global] #--authconfig--start-line-- # Generated by authconfig on 2011/12/05 17:22:13 # DO NOT EDIT THIS SECTION (delimited by --start-line--/--end-line--) # Any modification may be deleted or altered by authconfig in future workgroup = LOW password server = LOWDC security = user idmap uid = 16777216-33554431 idmap gid = 16777216-33554431 template shell = /bin/false winbind use default domain = false winbind offline logon = false server signing = auto log level = 2 log file = /var/log/samba.log.%m max log size = 50 debug timestamp = yes #--authconfig--end-line-- load printers = yes printing = cups printcap name = cups [printers] comment = All Printers path = /var/spool/samba browseable = no guest ok = yes writable = no printable = yes printer admin = root, @ntadmins, @smbprintadm use client driver = yes If the Microsoft network client: Digitally sign communications (always) setting is disabled it all works OK, but disabling this policy setting is not an allowed option at present. That sounds like a signing error - do you see such in the Samba logs ? Jeremy. I have the same message in samba log file, even though I set up log level = 0. My Samba 3.4.5 PDC is listening on both ports 139 and 445 under CentOS 5.6 32bits. Here is the message: [2011/10/26 16:02:05, 0] lib/util_sock.c:539(read_fd_with_timeout) [2011/10/26 16:02:05, 0] lib/util_sock.c:1491(get_peer_addr_internal) getpeername failed. Error was Transport endpoint is not connected read_fd_with_timeout: client 0.0.0.0 read error = Connection reset by peer. [2011/10/26 16:02:05, 0] lib/util_sock.c:1491(get_peer_addr_internal) getpeername failed. Error was Transport endpoint is not connected [2011/10/26 16:02:05, 0] lib/util_sock.c:1491(get_peer_addr_internal) getpeername failed. Error was Transport endpoint is not connected Allen -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] getpeername failed error when signed communications policy enabled
On Thu, Dec 15, 2011 at 09:10:11AM +, Hilton, David wrote: No, the only error that we see is the getpeername failed error in the Samba log for the client machine that is trying to print the job. Then I doubt it's a signing issue (which makes it strange). What does a debug level 10 say ? Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] getpeername failed error when signed communications policy enabled
On Wed, Dec 07, 2011 at 11:01:50AM +, Hilton, David wrote: Hi, I'm looking for help with an issue that we are seeing with the following configuration: We are using Samba (3.5.12-72.fc15) to share out CUPS printers from a Fedora 15 machine. However, a requirement of the system is that these printers are not directly visible from client systems (Windows 7 SP1 32-bit), so instead we are sharing them out from a Windows print server (Windows 2008 R2 SP1). So the clients connect to print queues on the Windows print server, which in turn forwards the print jobs on to CUPS. The issue we are seeing occurs when a policy change is made on the Windows 2008 R2 print server. If the Microsoft network client: Digitally sign communications (always) policy setting is enabled, we see the following behaviour: - Applications running on the print server can print normally. - Applications running on client machines fail to print. When a print job fails we see the following in the samba log for the client machine: [2011/12/07 10:43:23.381798, 2] auth/auth.c:304(check_ntlm_password) check_ntlm_password: authentication for user [XXX] - [XXX] - [XXX] succeeded [2011/12/07 10:43:39.760399, 0] lib/util_sock.c:474(read_fd_with_timeout) [2011/12/07 10:43:39.760476, 0] lib/util_sock.c:1441(get_peer_addr_internal) getpeername failed. Error was Transport endpoint is not connected read_fd_with_timeout: client 0.0.0.0 read error = Connection reset by peer. The smb.conf file that we are using is as follows: [global] #--authconfig--start-line-- # Generated by authconfig on 2011/12/05 17:22:13 # DO NOT EDIT THIS SECTION (delimited by --start-line--/--end-line--) # Any modification may be deleted or altered by authconfig in future workgroup = LOW password server = LOWDC security = user idmap uid = 16777216-33554431 idmap gid = 16777216-33554431 template shell = /bin/false winbind use default domain = false winbind offline logon = false server signing = auto log level = 2 log file = /var/log/samba.log.%m max log size = 50 debug timestamp = yes #--authconfig--end-line-- load printers = yes printing = cups printcap name = cups [printers] comment = All Printers path = /var/spool/samba browseable = no guest ok = yes writable = no printable = yes printer admin = root, @ntadmins, @smbprintadm use client driver = yes If the Microsoft network client: Digitally sign communications (always) setting is disabled it all works OK, but disabling this policy setting is not an allowed option at present. That sounds like a signing error - do you see such in the Samba logs ? Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] getpeername failed error when signed communications policy enabled
Hi, I'm looking for help with an issue that we are seeing with the following configuration: We are using Samba (3.5.12-72.fc15) to share out CUPS printers from a Fedora 15 machine. However, a requirement of the system is that these printers are not directly visible from client systems (Windows 7 SP1 32-bit), so instead we are sharing them out from a Windows print server (Windows 2008 R2 SP1). So the clients connect to print queues on the Windows print server, which in turn forwards the print jobs on to CUPS. The issue we are seeing occurs when a policy change is made on the Windows 2008 R2 print server. If the Microsoft network client: Digitally sign communications (always) policy setting is enabled, we see the following behaviour: - Applications running on the print server can print normally. - Applications running on client machines fail to print. When a print job fails we see the following in the samba log for the client machine: [2011/12/07 10:43:23.381798, 2] auth/auth.c:304(check_ntlm_password) check_ntlm_password: authentication for user [XXX] - [XXX] - [XXX] succeeded [2011/12/07 10:43:39.760399, 0] lib/util_sock.c:474(read_fd_with_timeout) [2011/12/07 10:43:39.760476, 0] lib/util_sock.c:1441(get_peer_addr_internal) getpeername failed. Error was Transport endpoint is not connected read_fd_with_timeout: client 0.0.0.0 read error = Connection reset by peer. The smb.conf file that we are using is as follows: [global] #--authconfig--start-line-- # Generated by authconfig on 2011/12/05 17:22:13 # DO NOT EDIT THIS SECTION (delimited by --start-line--/--end-line--) # Any modification may be deleted or altered by authconfig in future workgroup = LOW password server = LOWDC security = user idmap uid = 16777216-33554431 idmap gid = 16777216-33554431 template shell = /bin/false winbind use default domain = false winbind offline logon = false server signing = auto log level = 2 log file = /var/log/samba.log.%m max log size = 50 debug timestamp = yes #--authconfig--end-line-- load printers = yes printing = cups printcap name = cups [printers] comment = All Printers path = /var/spool/samba browseable = no guest ok = yes writable = no printable = yes printer admin = root, @ntadmins, @smbprintadm use client driver = yes If the Microsoft network client: Digitally sign communications (always) setting is disabled it all works OK, but disabling this policy setting is not an allowed option at present. - David smime.p7s Description: S/MIME cryptographic signature -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] 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) [2011/03/10 21:10:04, 0] lib/util_sock.c:(1224) write_data: write failure in writing to client 0.0.0.0. Error Broken pipe Error writing 5 bytes to client. -1. (Broken pipe) It would be very much appreciate some guidances on how to resolve this issue. Thanks, Jack -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] getpeername failed. Error was Transport endpoint is notconnected (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) [2011/03/10 21:10:04, 0] lib/util_sock.c:(1224) write_data: write failure in writing to client 0.0.0.0. Error Broken pipe Error writing 5 bytes to client. -1. (Broken pipe) It would be very much appreciate some guidances on how to resolve this issue. This error is very old, and seems to be related to samba binding to multiple ports (139 and 445). You only need 445 in most modern worlds, unless you're a PDC from what I can tell. I stuck this in my smb.conf file: # restrict ports to avoid # getpeername failed. Error was Transport endpoint is not connected and # Error writing 4 bytes to client. -1. (Transport endpoint is not connected) # errors from port 139 legacy mode - PDC may need 139 open smb ports = 445 -=Andrew -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] getpeername failed. Error was Transport endpoint is notconnected (3.0.37)
I find I have to have both ports open- then again my main samba servers are configured as DC's. I don't know about member servers, but DC file server are using SMB-over-NetBIOS-over-IP (NT4 style) - I don't think they can support pure SMB-over-TCP/IP. I had tried setting to 139 only- I think some XP and Win 7 clients make an initial connection to port 445 then get redirected. If I disabled Netbios on the XP clients, they can't connect to a samba DC. -Original Message- From: samba-boun...@lists.samba.org [mailto:samba-boun...@lists.samba.org] On Behalf Of Andrew Masterson Sent: Thursday, March 10, 2011 1:56 PM To: Jack Bush; samba@lists.samba.org Subject: Re: [Samba] getpeername failed. Error was Transport endpoint is notconnected (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) [2011/03/10 21:10:04, 0] lib/util_sock.c:(1224) write_data: write failure in writing to client 0.0.0.0. Error Broken pipe Error writing 5 bytes to client. -1. (Broken pipe) It would be very much appreciate some guidances on how to resolve this issue. This error is very old, and seems to be related to samba binding to multiple ports (139 and 445). You only need 445 in most modern worlds, unless you're a PDC from what I can tell. I stuck this in my smb.conf file: # restrict ports to avoid # getpeername failed. Error was Transport endpoint is not connected and # Error writing 4 bytes to client. -1. (Transport endpoint is not connected) # errors from port 139 legacy mode - PDC may need 139 open smb ports = 445 -=Andrew -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] 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 18:13:42 samba smbd[21646]: [2011/02/18 18:13:42.423085, 2] lib/interface.c:340(add_interface) Feb 18 18:13:42 samba smbd[21646]: added interface eth0 ip=fe80::250:56ff:fe97:3374%eth0 bcast=fe80:::::%eth0 netmask=::::: Feb 18 18:13:42 samba smbd[21646]: [2011/02/18 18:13:42.423232, 2] lib/interface.c:340(add_interface) Feb 18 18:13:42 samba smbd[21646]: added interface eth0 ip=192.168.200.2 bcast=192.168.200.255 netmask=255.255.255.0 Feb 18 18:13:42 samba smbd[21646]: [2011/02/18 18:13:42.424046, 2] smbd/reply.c:554(reply_special) Feb 18 18:13:42 samba smbd[21646]: netbios connect: name1=SAMBA 0x20 name2=PC2009-03 0x0 Feb 18 18:13:42 samba smbd[21646]: [2011/02/18 18:13:42.424135, 2] smbd/reply.c:565(reply_special) Feb 18 18:13:42 samba smbd[21646]: netbios connect: local=samba remote=pc2009-03, name type = 0 Feb 18 18:13:42 samba smbd[21646]: [2011/02/18 18:13:42.424320, 0] lib/util_sock.c:675(write_data) Feb 18 18:13:42 samba smbd[21646]: [2011/02/18 18:13:42.424352, 0] lib/util_sock.c:1432(get_peer_addr_internal) 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 Feb 18 18:13:42 samba smbd[21646]: [2011/02/18 18:13:42.425301, 0] smbd/process.c:79(srv_send_smb) Feb 18 18:13:42 samba smbd[21646]: Error writing 4 bytes to client. -1. (Transport endpoint is not connected) Feb 18 18:13:42 samba smbd[21647]: [2011/02/18 18:13:42.427012, 2] printing/print_cups.c:550(cups_async_callback) Feb 18 18:13:42 samba smbd[21647]: cups_async_callback: failed to read a new printer list Feb 18 18:13:42 samba smbd[21647]: [2011/02/18 18:13:42.427239, 2] lib/interface.c:340(add_interface) Feb 18 18:13:42 samba smbd[21647]: added interface eth0 ip=fe80::250:56ff:fe97:3374%eth0 bcast=fe80:::::%eth0 netmask=::::: Feb 18 18:13:42 samba smbd[21647]: [2011/02/18 18:13:42.427480, 2] lib/interface.c:340(add_interface) Feb 18 18:13:42 samba smbd[21647]: added interface eth0 ip=192.168.200.2 bcast=192.168.200.255 netmask=255.255.255.0 Feb 18 18:13:43 samba smbd[21647]: [2011/02/18 18:13:43.886294, 2] smbd/sesssetup.c:1391(setup_new_vc_session) Feb 18 18:13:43 samba smbd[21647]: setup_new_vc_session: New VC == 0, if NT4.x compatible we would close all -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] getpeername failed
Hello all, I have a simple share on samba 3.2.5-4lenny13 defined like this : [global] workgroup = MYDOMAIN realm = MYDOMAIN.ORG server string = %h server security = ADS obey pam restrictions = Yes load printers = No idmap uid = 1-2 idmap gid = 1-2 winbind enum users = Yes winbind enum groups = Yes winbind use default domain = Yes [myshare] comment = myshare path = /home/myshare valid users = MYDOMAIN\myuser1, MYDOMAIN\myuser2 write list = MYDOMAIN\myuser1, MYDOMAIN\myuser2 force group = mygroup read only = No I can mount it from a linux for any user. I can access it from a Windows7 for myuser1 (admin on AD). getent passwd | grep myuser2 return myuser2. But I have this message for myuser2 (not admin) on W7 : getpeername failed. Error was Noeud final de transport n'est pas connecté read_socket_with_timeout: client 0.0.0.0 read error = Aucun chemin d'accès pour atteindre l'hôte cible. I browsed Google and the only response I saw was an upgrade of samba but I can't (need to be in stable Debian version), and it doesn't explain why myuser1 can connect. Please CC me because I'm not subscribed. Thank's in advance. -- David Dumortier -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] getpeername failed.
Hi everyone. Does anyone can tell me what does mean this message? getpeername failed. Error was Noeud final de transport n'est pas connecté [2010/09/13 08:31:00, 0] lib/util_sock.c:get_peer_addr(1224) my /var/log/smbd.log is full with this such message. -- Olivier Pavilla S.C.I.R.C. Orléans (Bourgogne) - I.U.F.M. Centre-Val de Loire 72 Rue du Faubourg Bourgogne -45044 ORLEANS Cedex 1 Tel : 02-38-49-26-20 , mailto:olivier.pavi...@univ-orleans.fr signature.asc Description: OpenPGP digital signature -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] 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 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] getpeername failed. Error was Invalid argument
This is the first time I've noticed this with Samba 3.2.8 on Irix: [2009/02/19 16:40:15, 1] smbd/service.c:make_connection_snum(1194) eowyn (161.253.154.245) signed connect to service warburg initially as user warburg (uid=123, gid=20) (pid 13408) [2009/02/19 17:20:06, 0] lib/util_sock.c:read_socket_with_timeout(936) [2009/02/19 17:20:06, 0] lib/util_sock.c:get_peer_addr_internal(1675) getpeername failed. Error was Invalid argument read_socket_with_timeout: client 0.0.0.0 read error = Invalid argument. [2009/02/19 17:20:06, 1] smbd/service.c:close_cnum(1402) eowyn (161.253.154.245) closed connection to service warburg What's going on with this read socket with timeout thing? Is it that the client disconnected from the network before disconnecting from the share? ---Jason Mader, National Crash Analysis Center, The George Washington University, VA Campus -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] getpeername failed
After a year of running a stable Samba connection, I can no longer connect to my Linux server. The error getpeername failed. Error was Transport endpoint is not connected shows in the error log. What would (could) be the cause of this, and where do I start troubleshooting? Thanks for any tips. Gerry -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Samba getpeername failed problem
Hi, About 10 days ago, I started looking at the getpeername failed. Error was Transport endpoint is not connected message appearing on our logs. This message was being produced very frequently during the day and somewhat less frequently at night. Anyone can help me to fix it ?? Here're message info ! Our configuration is samba 3.0.10a Our network has about 60 XP Pro PC's and 100 w2k PC's. Jul 17 21:08:42 subf1 smbd[4309]: [2006/07/17 21:08:42, 0] lib/util_sock.c:read_socket_data(384) Jul 17 21:08:42 subf1 smbd[4309]: read_socket_data: recv failure for 4. Error was Bad file descriptor Jul 17 21:08:44 subf1 smbd[4316]: [2006/07/17 21:08:44, 0] lib/util_sock.c:read_socket_data(384) Jul 17 21:08:44 subf1 smbd[4316]: read_socket_data: recv failure for 4. Error was Bad file descriptor Jul 17 21:08:45 subf1 smbd[4318]: [2006/07/17 21:08:45, 0] lib/util_sock.c:read_socket_data(384) Jul 17 21:08:45 subf1 smbd[4318]: read_socket_data: recv failure for 4. Error was Bad file descriptor Jul 17 21:08:48 subf1 smbd[4349]: [2006/07/17 21:08:48, 0] lib/util_sock.c:read_socket_data(384) Jul 17 21:08:48 subf1 smbd[4349]: read_socket_data: recv failure for 4. Error was Bad file descriptor Jul 17 21:08:51 subf1 smbd[4371]: [2006/07/17 21:08:51, 0] lib/util_sock.c:get_peer_addr(1000) testparm -s Load smb config files from /etc/samba/smb.conf Processing section [db6] Loaded services file OK. Invalid combination of parameters for service db6. Level II oplocks can only be set if oplocks are also set. # Global parameters [global] workgroup = XEON server string = Samba Server security = SHARE guest account = xeon log level = 3 log file = /etc/samba/smb.log max log size = 50 max mux = 150 max xmit = 204800 max ttl = 1296000 change notify timeout = 120 keepalive = 10 socket options = TCP_NODELAY SO_SNDBUF=8192 SO_RCVBUF=8192 SO_KEEPALIVE load printers = No os level = 68 preferred master = No local master = No dns proxy = No wins proxy = Yes read only = No cups options = raw case sensitive = Yes map archive = No oplocks = No [db6] path = /db6/test force user = joe force group = user guest ok = Yes Best regards, Alen Fang CGCG Inc.. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] getpeername failed
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 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 System Events =-=-=-=-=-=-= [2006/06/16 08:12:37, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 08:12:38, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 08:12:38, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 08:12:38, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 08:24:34, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 08:36:31, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 08:36:31, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 08:36:31, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 08:36:31, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 08:40:53, 1] lib/util_sock.c:open_socket_out(774) [2006/06/16 08:40:53, 1] libsmb/cliconnect.c:cli_connect(1330) [2006/06/16 08:45:55, 1] lib/util_sock.c:open_socket_out(774) [2006/06/16 08:45:55, 1] libsmb/cliconnect.c:cli_connect(1330) ... [2006/06/16 08:59:01, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 08:59:01, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 08:59:01, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 08:59:01, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 09:04:28, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 09:04:29, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 09:04:29, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 09:06:22, 1] lib/util_sock.c:open_socket_out(774) [2006/06/16 09:06:23, 1] libsmb/cliconnect.c:cli_connect(1330) [2006/06/16 09:09:59, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 09:10:00, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 09:14:41, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 09:22:02, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 09:33:58, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 09:33:58, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 09:33:58, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 09:33:58, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 09:33:58, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 09:42:14, 1] lib/util_sock.c:open_socket_out(774) [2006/06/16 09:42:14, 1] libsmb/cliconnect.c:cli_connect(1330) [2006/06/16 09:45:54, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 09:45:54, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 09:45:54, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 09:47:16, 1] lib/util_sock.c:open_socket_out(774) [2006/06/16 09:47:16, 1] libsmb/cliconnect.c:cli_connect(1330) [2006/06/16 09:57:47, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 10:02:39, 1] lib/util_sock.c:open_socket_out(774) [2006/06/16 10:02:39, 1] libsmb/cliconnect.c:cli_connect(1330) [2006/06/16 10:07:01, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 10:09:47, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 10:09:47, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 10:21:44, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 10:27:56, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 10:33:40, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 10:33:41, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 10:33:41, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 10:33:41, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 10:38:24, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 10:45:37, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 10:45:37, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 10:48:52, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 10:49:06, 1] lib/util_sock.c:open_socket_out(774) [2006/06/16 10:49:06, 1] libsmb/cliconnect.c:cli_connect(1330) [2006/06/16 10:57:33, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 10:57:34, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 11:09:30, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 11:09:30, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 11:09:30, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 11:19:11, 1] lib/util_sock.c:open_socket_out(774) [2006/06/16 11:19:11, 1] libsmb/cliconnect.c:cli_connect(1330) [2006/06/16 11:21:27, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 11:21:27, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 11:21:27, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 11:32:29, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 11:32:30, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 11:33:31, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 11:39:36, 1] lib/util_sock.c:open_socket_out(774) [2006/06/16 11:39:36, 1] libsmb/cliconnect.c:cli_connect(1330) [2006/06/16
[Samba] getpeername failed
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 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 System Events =-=-=-=-=-=-= [2006/06/16 08:12:37, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 08:12:38, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 08:12:38, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 08:12:38, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 08:24:34, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 08:36:31, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 08:36:31, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 08:36:31, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 08:36:31, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 08:40:53, 1] lib/util_sock.c:open_socket_out(774) [2006/06/16 08:40:53, 1] libsmb/cliconnect.c:cli_connect(1330) [2006/06/16 08:45:55, 1] lib/util_sock.c:open_socket_out(774) [2006/06/16 08:45:55, 1] libsmb/cliconnect.c:cli_connect(1330) [2006/06/16 08:48:27, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 08:48:27, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 08:48:28, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 08:51:12, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 08:51:13, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 08:51:13, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 08:51:13, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 08:51:13, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 08:53:45, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 08:53:45, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 08:59:01, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 08:59:01, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 08:59:01, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 08:59:01, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 09:04:28, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 09:04:29, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 09:04:29, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 09:06:22, 1] lib/util_sock.c:open_socket_out(774) [2006/06/16 09:06:23, 1] libsmb/cliconnect.c:cli_connect(1330) [2006/06/16 09:09:59, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 09:10:00, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 09:14:41, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 09:22:02, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 09:33:58, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 09:33:58, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 09:33:58, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 09:33:58, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 09:33:58, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 09:42:14, 1] lib/util_sock.c:open_socket_out(774) [2006/06/16 09:42:14, 1] libsmb/cliconnect.c:cli_connect(1330) [2006/06/16 09:45:54, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 09:45:54, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 09:45:54, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 09:47:16, 1] lib/util_sock.c:open_socket_out(774) [2006/06/16 09:47:16, 1] libsmb/cliconnect.c:cli_connect(1330) [2006/06/16 09:57:47, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 10:02:39, 1] lib/util_sock.c:open_socket_out(774) [2006/06/16 10:02:39, 1] libsmb/cliconnect.c:cli_connect(1330) [2006/06/16 10:07:01, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 10:09:47, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 10:09:47, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 10:21:44, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 10:27:56, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 10:33:40, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 10:33:41, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 10:33:41, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 10:33:41, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 10:38:24, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 10:45:37, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 10:45:37, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 10:48:52, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 10:49:06, 1] lib/util_sock.c:open_socket_out(774) [2006/06/16 10:49:06, 1] libsmb/cliconnect.c:cli_connect(1330) [2006/06/16 10:57:33, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 10:57:34, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 11:09:30, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 11:09:30, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 11:09:30, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 11:19:11, 1]
[Samba] getpeername failed
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 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 System Events =-=-=-=-=-=-= [2006/06/16 08:12:37, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 08:12:38, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 08:12:38, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 08:12:38, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 08:24:34, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 08:36:31, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 08:36:31, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 08:36:31, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 08:36:31, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 08:40:53, 1] lib/util_sock.c:open_socket_out(774) [2006/06/16 08:40:53, 1] libsmb/cliconnect.c:cli_connect(1330) [2006/06/16 08:45:55, 1] lib/util_sock.c:open_socket_out(774) [2006/06/16 08:45:55, 1] libsmb/cliconnect.c:cli_connect(1330) [2006/06/16 08:48:27, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 08:48:27, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 08:48:28, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 08:51:12, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 08:51:13, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 08:51:13, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 08:51:13, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 08:51:13, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 08:53:45, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 08:53:45, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 08:59:01, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 08:59:01, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 08:59:01, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 08:59:01, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 09:04:28, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 09:04:29, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 09:04:29, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 09:06:22, 1] lib/util_sock.c:open_socket_out(774) [2006/06/16 09:06:23, 1] libsmb/cliconnect.c:cli_connect(1330) [2006/06/16 09:09:59, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 09:10:00, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 09:14:41, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 09:22:02, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 09:33:58, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 09:33:58, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 09:33:58, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 09:33:58, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 09:33:58, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 09:42:14, 1] lib/util_sock.c:open_socket_out(774) [2006/06/16 09:42:14, 1] libsmb/cliconnect.c:cli_connect(1330) [2006/06/16 09:45:54, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 09:45:54, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 09:45:54, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 09:47:16, 1] lib/util_sock.c:open_socket_out(774) [2006/06/16 09:47:16, 1] libsmb/cliconnect.c:cli_connect(1330) [2006/06/16 09:57:47, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 10:02:39, 1] lib/util_sock.c:open_socket_out(774) [2006/06/16 10:02:39, 1] libsmb/cliconnect.c:cli_connect(1330) [2006/06/16 10:07:01, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 10:09:47, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 10:09:47, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 10:21:44, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 10:27:56, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 10:33:40, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 10:33:41, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 10:33:41, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 10:33:41, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 10:38:24, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 10:45:37, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 10:45:37, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 10:48:52, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 10:49:06, 1] lib/util_sock.c:open_socket_out(774) [2006/06/16 10:49:06, 1] libsmb/cliconnect.c:cli_connect(1330) [2006/06/16 10:57:33, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 10:57:34, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 11:09:30, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 11:09:30, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16 11:09:30, 0] lib/util_sock.c:get_peer_addr(1150) [2006/06/16
[Samba] 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 opened for user root by (uid=0) Dec 18 14:00:04 constellation syslogd 1.4.1: restart. Dec 18 14:00:04 constellation crond(pam_unix)[8126]: session closed for user root Dec 18 14:01:01 constellation crond(pam_unix)[8136]: session opened for user root by (uid=0) Dec 18 14:01:02 constellation crond(pam_unix)[8136]: session closed for user root Dec 18 14:24:55 constellation smbd[8333]: [2005/12/18 14:24:55, 0] lib/util_sock.c:get_peer_addr(1150) Dec 18 14:24:55 constellation smbd[8333]: getpeername failed. Error was Transport endpoint is not connected Dec 18 14:24:55 constellation smbd[8333]: [2005/12/18 14:24:55, 0] lib/util_sock.c:write_socket_data(430) Dec 18 14:24:55 constellation smbd[8333]: write_socket_data: write failure. Error = Connection reset by peer Dec 18 14:24:55 constellation smbd[8333]: [2005/12/18 14:24:55, 0] lib/util_sock.c:write_socket(455) Dec 18 14:24:55 constellation smbd[8333]: write_socket: Error writing 4 bytes to socket 24: ERRNO = Connection reset by peer Thanks ! -- Franck -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[SAMBA] 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 opened for user root by (uid=0) Dec 18 14:00:04 constellation syslogd 1.4.1: restart. Dec 18 14:00:04 constellation crond(pam_unix)[8126]: session closed for user root Dec 18 14:01:01 constellation crond(pam_unix)[8136]: session opened for user root by (uid=0) Dec 18 14:01:02 constellation crond(pam_unix)[8136]: session closed for user root Dec 18 14:24:55 constellation smbd[8333]: [2005/12/18 14:24:55, 0] lib/util_sock.c:get_peer_addr(1150) Dec 18 14:24:55 constellation smbd[8333]: getpeername failed. Error was Transport endpoint is not connected Dec 18 14:24:55 constellation smbd[8333]: [2005/12/18 14:24:55, 0] lib/util_sock.c:write_socket_data(430) Dec 18 14:24:55 constellation smbd[8333]: write_socket_data: write failure. Error = Connection reset by peer Dec 18 14:24:55 constellation smbd[8333]: [2005/12/18 14:24:55, 0] lib/util_sock.c:write_socket(455) Dec 18 14:24:55 constellation smbd[8333]: write_socket: Error writing 4 bytes to socket 24: ERRNO = Connection reset by peer Thanks ! -- Franck -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [SAMBA] getpeername failed
Franck Y wrote: 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 opened for user root by (uid=0) Dec 18 14:00:04 constellation syslogd 1.4.1: restart. Dec 18 14:00:04 constellation crond(pam_unix)[8126]: session closed for user root Dec 18 14:01:01 constellation crond(pam_unix)[8136]: session opened for user root by (uid=0) Dec 18 14:01:02 constellation crond(pam_unix)[8136]: session closed for user root Dec 18 14:24:55 constellation smbd[8333]: [2005/12/18 14:24:55, 0] lib/util_sock.c:get_peer_addr(1150) Dec 18 14:24:55 constellation smbd[8333]: getpeername failed. Error was Transport endpoint is not connected Dec 18 14:24:55 constellation smbd[8333]: [2005/12/18 14:24:55, 0] lib/util_sock.c:write_socket_data(430) Dec 18 14:24:55 constellation smbd[8333]: write_socket_data: write failure. Error = Connection reset by peer Dec 18 14:24:55 constellation smbd[8333]: [2005/12/18 14:24:55, 0] lib/util_sock.c:write_socket(455) Dec 18 14:24:55 constellation smbd[8333]: write_socket: Error writing 4 bytes to socket 24: ERRNO = Connection reset by peer Thanks ! -- Franck Does this happen when you are doing something in particular? --Dennis -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [SAMBA] getpeername failed
Franck Y wrote: Hello, Thanks for your reply ! Not something in particular but i get more when i was doing a backup It s so weird. I think it something with acces to files u don t know and it pi**ing me off... Franck To my understanding Windows (XP at least) tries to connect to both port 139 and 445 (it sends the request to each port at basically the same time). If it receives a response on port 445 it will drop the connection to 139, but it doesn't do it gracefully and so the samba server just says connection reset by peer. The default behavoir of samba is to listen on both ports (since it's the default for windows). You can override it in smb.conf and tell samba to only listen on one of the ports. It could also be a problem with oplocks, but I'm not familiar with those at all so somebody else will have to chime in. --Dennis -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] getpeername failed. Error was Transport endpoint is not connected
Hello NG I'm trying without success to join a XP workstation in a Samba/openldap domain SuSE 9.3)and to connect this samba/ldap as fileserver. On samba machine I'm getting this errormessage: my var/log/samba/smbd: [2005/10/26 16:24:04, 0] lib/util_sock.c:get_peer_addr(1150) getpeername failed. Error was Transport endpoint is not connected [2005/10/26 16:26:28, 0] lib/util_sock.c:get_peer_addr(1150) getpeername failed. Error was Transport endpoint is not connected The errormessage of XP after the login machinejoining XP GUI is: couldn't found the username, but the NetBios Administratoraccount is existing. Can somebody help me, any idea? Best regards and many thanks Andreas -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] 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 11:02:10, 0] lib/access.c:check_access(328) [2005/10/04 11:02:10, 0] lib/util_sock.c:get_peer_addr(1150) getpeername failed. Error was Transport endpoint is not connected Denied connection from (0.0.0.0 http://0.0.0.0) [2005/10/04 11:02:10, 1] smbd/process.c:process_smb(1084) [2005/10/04 11:02:10, 0] lib/util_sock.c:get_peer_addr(1150) getpeername failed. Error was Transport endpoint is not connected Connection denied from 0.0.0.0 http://0.0.0.0 [2005/10/04 11:02:10, 0] lib/util_sock.c:write_socket_data(430) write_socket_data: write failure. Error = Connection reset by peer [2005/10/04 11:02:10, 0] lib/util_sock.c:write_socket(455) write_socket: Error writing 5 bytes to socket 27: ERRNO = Connection reset by peer [2005/10/04 11:02:10, 0] lib/util_sock.c:send_smb(647) Error writing 5 bytes to client. -1. (Connection reset by peer) -- Alexandre Novello -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[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 clients! Once the samba domain joined, I reboot the client machine and I try to log on to the domain. The later operation falls with an error message telling that it a connection cannot be opened. I check my smbd log file, it reports the following: [2005/08/24 09:49:09, 0] lib/util_sock.c:get_peer_addr(1150) getpeername failed. Error was Transport endpoint is not connected [2005/08/24 09:49:09, 0] lib/util_sock.c:write_socket_data(430) write_socket_data: write failure. Error = Connection reset by peer [2005/08/24 09:49:09, 0] lib/util_sock.c:write_socket(455) write_socket: Error writing 4 bytes to socket 25: ERRNO = Connection reset by peer [2005/08/24 09:49:09, 0] lib/util_sock.c:send_smb(647) Error writing 4 bytes to client. -1. (Connection reset by peer) Would you have any idea of what is going wrong there? Thank you ___ Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger Téléchargez cette version sur http://fr.messenger.yahoo.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Tr: [Samba] getpeername failed - PLEASE HELP
--- Bahya NASSR EDDINE [EMAIL PROTECTED] a écrit : Date: Wed, 24 Aug 2005 12:14:37 +0200 (CEST) De: Bahya NASSR EDDINE [EMAIL PROTECTED] À: 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 clients! Once the samba domain joined, I reboot the client machine and I try to log on to the domain. The later operation falls with an error message telling that it a connection cannot be opened. I check my smbd log file, it reports the following: [2005/08/24 09:49:09, 0] lib/util_sock.c:get_peer_addr(1150) getpeername failed. Error was Transport endpoint is not connected [2005/08/24 09:49:09, 0] lib/util_sock.c:write_socket_data(430) write_socket_data: write failure. Error = Connection reset by peer [2005/08/24 09:49:09, 0] lib/util_sock.c:write_socket(455) write_socket: Error writing 4 bytes to socket 25: ERRNO = Connection reset by peer [2005/08/24 09:49:09, 0] lib/util_sock.c:send_smb(647) Error writing 4 bytes to client. -1. (Connection reset by peer) Would you have any idea of what is going wrong there? Thank you ___ Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger Téléchargez cette version sur http://fr.messenger.yahoo.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba ___ Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger Téléchargez cette version sur http://fr.messenger.yahoo.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: Tr: [Samba] getpeername failed - PLEASE HELP
On Wednesday 24 August 2005 09:57, Bahya NASSR EDDINE wrote: --- Bahya NASSR EDDINE [EMAIL PROTECTED] a écrit Date: Wed, 24 Aug 2005 12:14:37 +0200 (CEST) De: Bahya NASSR EDDINE [EMAIL PROTECTED] À: 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 clients! Once the samba domain joined, I reboot the client machine and I try to log on to the domain. The later operation falls with an error message telling that it a connection cannot be opened. I check my smbd log file, it reports the following: [2005/08/24 09:49:09, 0] lib/util_sock.c:get_peer_addr(1150) getpeername failed. Error was Transport endpoint is not connected [2005/08/24 09:49:09, 0] lib/util_sock.c:write_socket_data(430) write_socket_data: write failure. Error = Connection reset by peer [2005/08/24 09:49:09, 0] lib/util_sock.c:write_socket(455) write_socket: Error writing 4 bytes to socket 25: ERRNO = Connection reset by peer [2005/08/24 09:49:09, 0] lib/util_sock.c:send_smb(647) Error writing 4 bytes to client. -1. (Connection reset by peer) Would you have any idea of what is going wrong there? Add to your smb.conf [globals]: smb ports = 139 If the problem persists, check your ether-switches, HUBS, network cables and ethernet cards. - John T. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] 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] lib/util_sock.c:get_peer_addr(1150) Jul 6 12:50:24 server4 smbd[27787]: getpeername failed. Error was Transport endpoint is not connected Jul 6 12:50:24 server4 smbd[27787]: [2005/07/06 12:50:24, 0] lib/util_sock.c:write_socket_data(430) Jul 6 12:50:24 server4 smbd[27787]: write_socket_data: write failure. Error = Connection reset by peer Jul 6 12:50:24 server4 smbd[27787]: [2005/07/06 12:50:24, 0] lib/util_sock.c:write_socket(455) Jul 6 12:50:24 server4 smbd[27787]: write_socket: Error writing 4 bytes to socket 5: ERRNO = Connection reset by peer Jul 6 12:50:24 server4 smbd[27787]: [2005/07/06 12:50:24, 0] lib/util_sock.c:send_smb(647) Jul 6 12:50:24 server4 smbd[27787]: Error writing 4 bytes to client. -1. (Connection reset by peer) Name resolve order in the smb.conf file: lmhosts hosts wins bcast Thanks Harry [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] 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] lib/util_sock.c:get_peer_addr(1150) Jul 6 12:50:24 server4 smbd[27787]: getpeername failed. Error was Transport endpoint is not connected Jul 6 12:50:24 server4 smbd[27787]: [2005/07/06 12:50:24, 0] lib/util_sock.c:write_socket_data(430) Jul 6 12:50:24 server4 smbd[27787]: write_socket_data: write failure. Error = Connection reset by peer Jul 6 12:50:24 server4 smbd[27787]: [2005/07/06 12:50:24, 0] lib/util_sock.c:write_socket(455) Jul 6 12:50:24 server4 smbd[27787]: write_socket: Error writing 4 bytes to socket 5: ERRNO = Connection reset by peer Jul 6 12:50:24 server4 smbd[27787]: [2005/07/06 12:50:24, 0] lib/util_sock.c:send_smb(647) Jul 6 12:50:24 server4 smbd[27787]: Error writing 4 bytes to client. -1. (Connection reset by peer) Name resolve order in the smb.conf file: lmhosts hosts wins bcast Thanks Harry [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] 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 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] getpeername failed. Error was Transport endpoint is not connected
I've already seen this in my logs... A little search on Google shows me that Windows XP client try try to connect to port 139 and 445 in parallel and drop the connection to port 139 if the connect to 445 is successful. In fact, no one was complaining about real network connection loss ... More informations here : http://www.linuxaa.com/ftopic6568.html Hope this helps. On Mon, 2005-04-18 at 03:58 -0300, Guido Lorenzutti wrote: 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 signature.asc Description: This is a digitally signed message part -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] getpeername failed. Error was Transport endpoint is not connected
man, 18.04.2005 kl. 08.58 skrev Guido Lorenzutti: 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? Correct your network problems; make sure that all computers in your network are reachable and booted. --Tonni -- Nothing sucksseeds like a pigeon without a beak ... mail: [EMAIL PROTECTED] http://www.billy.demon.nl They love us, don't they, They feed us, won't they ... -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] getpeername failed. Error was Transport endpoint is not connected
I've also seen a post somewhere (forgive, don't remember where somewhere is) suggesting that smb ports = 445 would corect this issue. So, which is it, 139 or 445? Dimitri On Monday 18 April 2005 05:55 am, Fabian Arrotin wrote: I've already seen this in my logs... A little search on Google shows me that Windows XP client try try to connect to port 139 and 445 in parallel and drop the connection to port 139 if the connect to 445 is successful. In fact, no one was complaining about real network connection loss ... More informations here : http://www.linuxaa.com/ftopic6568.html Hope this helps. On Mon, 2005-04-18 at 03:58 -0300, Guido Lorenzutti wrote: 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 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] getpeername failed. Error was Transport endpoint is not connected
I went around and around with this issue for months replacing cables, switches and nics on a couple of machines all to no avail. I played around with something I found in the archives: http://lists.samba.org/archive/samba/2004-April/084048.html Using iptables to drop port 445, I eliminated the errors. I have not seen the error return nor experienced any other negative impact on performance. Ed At 08:36 AM Monday, 4/18/2005, Dimitri Yioulos wrote -= I've also seen a post somewhere (forgive, don't remember where somewhere is) suggesting that smb ports = 445 would corect this issue. So, which is it, 139 or 445? Dimitri On Monday 18 April 2005 05:55 am, Fabian Arrotin wrote: I've already seen this in my logs... A little search on Google shows me that Windows XP client try try to connect to port 139 and 445 in parallel and drop the connection to port 139 if the connect to 445 is successful. In fact, no one was complaining about real network connection loss ... More informations here : http://www.linuxaa.com/ftopic6568.html Hope this helps. On Mon, 2005-04-18 at 03:58 -0300, Guido Lorenzutti wrote: 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 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba Ed Kasky ~ Randomly Generated Quote (194 of 477): Things may come to those who wait, but only the things left by those who hustle. - Abraham Lincoln -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] getpeername failed. Error was Transport endpoint is not connected
Are you sure? In wich scenario? I have a pdc on samba and when i check the netstat i have a lot of open conections with the 445 port on the smbd binary. Ed Kasky wrote: I went around and around with this issue for months replacing cables, switches and nics on a couple of machines all to no avail. I played around with something I found in the archives: http://lists.samba.org/archive/samba/2004-April/084048.html Using iptables to drop port 445, I eliminated the errors. I have not seen the error return nor experienced any other negative impact on performance. Ed At 08:36 AM Monday, 4/18/2005, Dimitri Yioulos wrote -= I've also seen a post somewhere (forgive, don't remember where somewhere is) suggesting that smb ports = 445 would corect this issue. So, which is it, 139 or 445? Dimitri On Monday 18 April 2005 05:55 am, Fabian Arrotin wrote: I've already seen this in my logs... A little search on Google shows me that Windows XP client try try to connect to port 139 and 445 in parallel and drop the connection to port 139 if the connect to 445 is successful. In fact, no one was complaining about real network connection loss ... More informations here : http://www.linuxaa.com/ftopic6568.html Hope this helps. On Mon, 2005-04-18 at 03:58 -0300, Guido Lorenzutti wrote: 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 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba Ed Kasky ~ Randomly Generated Quote (194 of 477): Things may come to those who wait, but only the things left by those who hustle. - Abraham Lincoln -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] getpeername failed
Hi, I'm seeing this a log in my logs: Apr 13 09:09:23 mail2 smbd[11431]: [2005/04/13 09:09:23, 0] lib/util_sock.c:get_peer_addr(1000) Apr 13 09:09:23 mail2 smbd[11431]: getpeername failed. Error was Transport endpoint is not connected Apr 13 09:09:23 mail2 smbd[11431]: Connection denied from 0.0.0.0 I would venture that this is because I got hosts deny = 0.0.0.0/0 in smb.conf, but I'm wondering if someone has a suggested loglevel / way to find out where these requests are comming from. It seems to me that this is either some kind of wierd broadcast, a hole in my firewall (most unlikely) or some misconfigured box somewhere. Has anyone seen something like this before and/or found the reason for the problem? Kind regards, Tarjei -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] 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 [EMAIL PROTECTED]:~# id fernando.ribeiro uid=1000(fernando.ribeiro) gid=1000(suporte) groups=1000(suporte),512(Domain Admins) [EMAIL PROTECTED]:~# smbclient -L ldap.domain.com.br -U fernando.ribeiro Password: Domain=[domain] OS=[Unix] Server=[Samba 3.0.7] ... WorkgroupMaster --- domain PDC my ldap.conf base dc=domain,dc=com,dc=br uri ldap://ldap.domain.com.br ssl start_tls port 389 TLS_CACERT /usr/local/ssl/cacert.pem rootbinddn cn=suporte,dc=domain,dc=com,dc=br nss_base_passwd ou=Usuarios,dc=domain,dc=com,dc=br?one nss_base_shadow ou=Usuarios,dc=domain,dc=com,dc=br?one nss_base_group ou=Grupos,dc=domain,dc=com,dc=br?one [global] workgroup = domain netbios name = PDC server string = PDC security = user encrypt passwords = yes load printers = yes log file = /var/log/samba/%m.log max log size = 50 log level = 5 os level = 255 local master = yes domain master = yes preferred master = yes domain logons = yes admin users = fernando.ribeiro, wesley.lago logon script = %U.bat logon path = \\%L\profiles\%U # wins support = no # wins proxy = no # dns proxy = no # name resolve order = wins lmhosts hosts bcast # smb ports = 137 138 139 445 # interfaces = 10.0.0.0/24 127.0.0.1 # bind interfaces only = Yes ldap passwd sync = yes ldap delete dn = Yes ldap port = 389 ldap ssl = start_tls passdb backend = ldapsam:ldap://ldap.domain.com.br/ ldap admin dn = cn=suporte,dc=domain,dc=com,dc=br ldap suffix = dc=domain,dc=com,dc=br ldap group suffix = ou=Grupos ldap user suffix = ou=Usuarios ldap machine suffix = ou=Computadores idmap uid = 1-15000 idmap gid = 1-15000 nt acl support = yes create mask = 600 directory mask = 0700 force directory mode = 0700 passwd chat = *New*password* %n\n *Retype*new*password* %n\n*passwd:*all*authentication*tokens*updated*successfully* socket options = TCP_NODELAY IPTOS_LOWDELAY SO_RCVBUF=8192 SO_SNDBUF=8192 add user script = /usr/local/sbin/smbldap-useradd -m %u add group script = /usr/local/sbin/smbldap-groupadd -p %g add machine script = /usr/local/sbin/smbldap-useradd -w %u delete user script = /usr/local/sbin/smbldap-userdel %u delete group script = /usr/local/sbin/smbldap-groupdel %g add user to group script = /usr/local/sbin/smbldap-groupmod -m %u %g delete user from group script = /usr/local/sbin/smbldap-groupmod -x %u %g set primary group script = /usr/local/sbin/smbldap-usermod -g %g %u dos charset = UTF-8 unix charset = UTF-8 cups server = 10.0.0.11 #use sendfile = no [homes] comment = Diretorio Home browseable = no writable = yes force user = %U [profiles] path = /home/profiles read only = No create mask = 0600 directory mask = 0700 browseable = No guest ok = Yes profile acls = Yes csc policy = disable force user = %U valid users = %U @Domain Admins [netlogon] path = /home/netlogon browseable = No read only = yes [printers] comment = Impressoras path = /var/spool/samba browseable = no guest ok = no writable = no printable = yes And while i try include a workstation (windows XP with SP2) it return this error: [2004/10/19 16:12:19, 0] lib/util_sock.c:get_peer_addr(1000) getpeername failed. Error was Transport endpoint is not connected [2004/10/19 16:12:19, 0] lib/util_sock.c:write_socket_data(430) write_socket_data: write failure. Error = Connection reset by peer [2004/10/19 16:12:19, 0] lib/util_sock.c:write_socket(455) write_socket: Error writing 4 bytes to socket 22: ERRNO = Connection reset by peer [2004/10/19 16:12:19, 0] lib/util_sock.c:send_smb(647) Error writing 4 bytes to client. -1. (Connection reset by peer) It created the windows$ entry in ldap: [EMAIL PROTECTED]:~# ldapsearch -x -ZZ -h ldap.domain.com.br -D cn=suporte,dc=domain,dc=com,dc=br uid=windows$ -W -LLL Enter LDAP Password: dn: uid=windows$,ou=Computadores,dc=domain,dc=com,dc=br objectClass: top objectClass: inetOrgPerson objectClass: posixAccount cn: windows$ sn: windows$ uid: windows$
Re: [Samba] getpeername failed. Error was Transport endpoint is not connected
It trying port 430 and 455? Why?? Palavras de Fernando Ribeiro [Tue, Oct 05, 2004 at 01:45:26PM -0300]: 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. Error was Transport endpoint is not connected [2004/10/05 12:51:26, 0] lib/util_sock.c:write_socket_data(430) write_socket_data: write failure. Error = Connection reset by peer [2004/10/05 12:51:26, 0] lib/util_sock.c:write_socket(455) write_socket: Error writing 4 bytes to socket 22: ERRNO = Connection reset by peer [2004/10/05 12:51:26, 0] lib/util_sock.c:send_smb(647) Error writing 4 bytes to client. -1. (Connection reset by peer) Anyone know why? My configuration has been in http://www.nerdgroup.org/doc/samba+ldap+qmail.txt Thanks -- Fernando Ribeiro - GPG-KEY: 0x8D7255F4 Linux Counter: #273768 - ICQ: 175630330 Linux Professional Institute - LPIC-1 Death the graph! Death the mouse! Death patents! Death closed standards! http://www.nerdgroup.org http://musb.nerdgroup.org -- Grandes mentes discutem idéias; Mentes medianas discutem eventos; Mentes pequenas discutem pessoas. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba -- Fernando Ribeiro - GPG-KEY: 0x8D7255F4 Linux Counter: #273768 - ICQ: 175630330 Linux Professional Institute - LPIC-1 Death the graph! Death the mouse! Death patents! Death closed standards! http://www.nerdgroup.org http://musb.nerdgroup.org -- Grandes mentes discutem idéias; Mentes medianas discutem eventos; Mentes pequenas discutem pessoas. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] 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. Error was Transport endpoint is not connected [2004/10/05 12:51:26, 0] lib/util_sock.c:write_socket_data(430) write_socket_data: write failure. Error = Connection reset by peer [2004/10/05 12:51:26, 0] lib/util_sock.c:write_socket(455) write_socket: Error writing 4 bytes to socket 22: ERRNO = Connection reset by peer [2004/10/05 12:51:26, 0] lib/util_sock.c:send_smb(647) Error writing 4 bytes to client. -1. (Connection reset by peer) Anyone know why? My configuration has been in http://www.nerdgroup.org/doc/samba+ldap+qmail.txt Thanks -- Fernando Ribeiro - GPG-KEY: 0x8D7255F4 Linux Counter: #273768 - ICQ: 175630330 Linux Professional Institute - LPIC-1 Death the graph! Death the mouse! Death patents! Death closed standards! http://www.nerdgroup.org http://musb.nerdgroup.org -- Grandes mentes discutem idéias; Mentes medianas discutem eventos; Mentes pequenas discutem pessoas. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] getpeername failed.
Recently I started getting these error messages in log.smbd... [2003/08/27 16:45:27, 0] lib/util_sock.c:get_socket_addr(919) getpeername failed. Error was Transport endpoint is not connected Any ideas on what it is trying to tell me? Spencer -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] getpeername failed
Hi, I'm using Samba 3.0beta2, and I am getting the following errors in log.smbd every time a machine connects: [2003/07/10 15:09:22, 0] lib/util_sock.c:get_socket_addr(895) getpeername failed. Error was Transport endpoint is not connected At the same time I get a log.0.0.0.0 file, as well as a log.machinename and log.ip.addr.of.machine file. I did some searching and found some reports saying that this was a DNS reverse lookup problem. However, I have checked and nslookup machinename works, as does nslookup ip.addr.of.machine (although it returns machinename.domainname. because that's what the W2K DNS server has defined automatically). WINS is not running on our network. The two machines in question (the server and the client machine connecting to it) are on the same domain and the same subnet - the client is running Windows 2000 Server and the Samba server is running on a fairly clean install of Red Hat Linux 9.0. There is no firewalling between the two machines. Samba 3.0beta2 was compiled from source. This problem does not appear to be adversely affecting Samba's operation, but it would be nice to figure out why it is occurring. Cheers, Paul - Paul Eggleton Ph:+64-9-4154790 Software Developer Fax: +64-9-4154791 CJN Technologies Ltd. DDI: +64-9-4154795 http://www.cjntech.co.nz Email: [EMAIL PROTECTED] - -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] getpeername failed
Anyone know what's up with this? Jun 20 09:48:37 alsi smbd[5235]: [2003/06/20 09:48:26, 0] lib/util_sock.c:get_socket_addr(895) Jun 20 09:48:37 alsi smbd[5235]: getpeername failed. Error was Transport endpoint is not connected Jun 20 09:48:37 alsi smbd[5235]: [2003/06/20 09:48:26, 0] lib/util_sock.c:write_socket_data(388) Jun 20 09:48:37 alsi smbd[5235]: write_socket_data: write failure. Error = Connection reset by peer Jun 20 09:48:37 alsi smbd[5235]: [2003/06/20 09:48:26, 0] lib/util_sock.c:write_socket(413) Jun 20 09:48:37 alsi smbd[5235]: write_socket: Error writing 4 bytes to socket 17: ERRNO = Connection reset by peer Jun 20 09:48:37 alsi smbd[5235]: [2003/06/20 09:48:26, 0] lib/util_sock.c:send_smb(574) Jun 20 09:48:37 alsi smbd[5235]: Error writing 4 bytes to client. -1. (Connection reset by peer) I have redhat 9, and did a rpm -Uvh to the latest release. I am now seeing these errors quite often (didn't before upgrade) and I've also noticed some names aren't resolving like: 192.168.1.102.log instead of machine1.log. Samba is not the wins server (looks to a windows machine). Security is share. Any thoughts would be helpful! t o n y A.G. (Tony) Nichols I.S. Manager Appalachian Log Structures Inc. www.applog.com [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
