Hello, I've been searching through the Samba archives attempting to find a resolution to intermittent Win2k -> Samba 2.2.2 for IRIX share failures. It seems that there have been numerous failures similar to mine reported with various versions of Samba and various OS's, but I've been unable to find a workable resolution. Intermittently when connecting to a Samba share from Win2k systems I receive the error "The specified network name is no longer available". After several (numerous) retries, the share will eventually be available, but not for long. It eventually disconnects again with these errors logged. [2001/12/14 09:52:43, 0] lib/util_sock.c:(1036) getpeername failed. Error was Invalid argument [2001/12/14 09:52:43, 0] lib/util_sock.c:(540) write_socket_data: write failure. Error = Broken pipe [2001/12/14 09:52:43, 0] lib/util_sock.c:(563) write_socket: Error writing 4 bytes to socket 11: ERRNO Broken pipe [2001/12/14 09:52:43, 0] lib/util_sock.c:(727) Error writing 4 bytes to client. -1. (Broken pipe) At the same time, there is absolutely no problem connecting to the same share from Windows NT4 systems. I'm currently running Samba 2.2.2 on an IRIX 6.5.9m server. I decided to try using something other than the default netbios name (dns name) in my smb.conf file and low and behold the Win2k systems have no problems connecting to the share as long as the netbios name is different than the dns hostname. Does anyone have experience with this Win2k -> Samba behavior? Thanks, Carrie
On Wed, Dec 19, 2001 at 05:15:50PM -0600, Carrie Knox wrote:> Hello, > > I've been searching through the Samba archives attempting to > find a resolution to intermittent Win2k -> Samba 2.2.2 for > IRIX share failures. It seems that there have been > numerous failures similar to mine reported with various > versions of Samba and various OS's, but I've been unable to > find a workable resolution. > > Intermittently when connecting to a Samba share from Win2k > systems I receive the error "The specified network name is > no longer available". After several (numerous) retries, > the share will eventually be available, but not for long. > It eventually disconnects again with these errors logged. > [2001/12/14 09:52:43, 0] lib/util_sock.c:(1036) > getpeername failed. Error was Invalid argument > [2001/12/14 09:52:43, 0] lib/util_sock.c:(540) > write_socket_data: write failure. Error = Broken pipe > [2001/12/14 09:52:43, 0] lib/util_sock.c:(563) > write_socket: Error writing 4 bytes to socket 11: ERRNO > Broken pipe > [2001/12/14 09:52:43, 0] lib/util_sock.c:(727) > Error writing 4 bytes to client. -1. (Broken pipe) > > At the same time, there is absolutely no problem connecting > > to the same share from Windows NT4 systems. > > I'm currently running Samba 2.2.2 on an IRIX 6.5.9m server. > > I decided to try using something other than the default > netbios name (dns name) in my smb.conf file and low and > behold the Win2k systems have no problems connecting to the > share as long as the netbios name is different than the dns > hostname. > > Does anyone have experience with this Win2k -> Samba > behavior? > Thanks,write_socket_data: write failure. Error = Broken pipe means the client has dropped the connection. Use tcpdump or some other TCP analysis tool to determine who sends the RST or FIN packet (and maybe why). This is at a layer below Samba. It may be an incompatibility at the TCP layer, although this is unlikely. But remember SMB traffic can stress TCP a lot - it transfers a lot more data and is a lot longer lived than the typical http request. Jeremy.
Just a guess, but it sounds like there may be some dns configuration issue with the ipaddress for your servername in DNS not being the same as the ip address configured on your system for the particular network card that samba is binding to. This is especially possible if you have multiple network cards with different ip addresses on your machine... What I am supposing is that your win2k machines are using dns for netbios name resolution, and determining the ip address for your machine (when it is using the dns name for its netbios name) from dns, and when it tries to get back to your server, it is communicating on an ip address (card) that is not the one that samba is binding to by default. When you use a different netbios name, then the win2k machine resolves the name via netbios broadcast, and gets the 'correct' address. Just a thought, Don -----Original Message----- From: Carrie Knox [mailto:knox@sgi.com] Sent: Thursday, December 20, 2001 10:53 AM To: Jeremy Allison Cc: samba@lists.samba.org Subject: Re: Win2k -> Samba 2.2.2 for IRIX Jeremy Allison wrote:> > > > I decided to try using something other than the default > > netbios name (dns name) in my smb.conf file and low and > > behold the Win2k systems have no problems connecting to the > > share as long as the netbios name is different than the dns > > hostname. > > > > Does anyone have experience with this Win2k -> Samba > > behavior? > > Thanks, > > write_socket_data: write failure. Error = Broken pipe > means the client has dropped the connection. Use tcpdump > or some other TCP analysis tool to determine who sends the > RST or FIN packet (and maybe why). This is at a layer below > Samba. It may be an incompatibility at the TCP layer, although > this is unlikely. But remember SMB traffic can stress TCP > a lot - it transfers a lot more data and is a lot longer > lived than the typical http request. > > Jeremy.Hello, Any ideas as to why the dropped connection only occurs when the Samba netbios name matches the Samba server's dns name? Thanks, Carrie -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Jeremy Allison wrote:> On Thu, Dec 20, 2001 at 01:26:45PM -0600, Carrie Knox wrote: > > > > It looks like Rst packets are coming from the Win2k client when the connection > > fails.... > > > > cfdhcp-87-3 -> cf3backup TCP D=445 S=2143 Syn Seq=4203875683 Len=0 Win=16384 > > > > cf3backup -> cfdhcp-87-3 TCP D=2143 S=445 Syn Ack=4203875684 Seq=1870848568 > > Len=0 Win=49152 > > cfdhcp-87-3 -> cf3backup TCP D=445 S=2143 Ack=1870848569 Seq=4203875684 > > Len=0 Win=17520 > > cfdhcp-87-3 -> cf3backup TCP D=139 S=2145 Rst Seq=4203813412 Len=0 Win=0 > > Yes, this packet is the client dropping the connection on port 139 via a RST. > It occurs just after the TCP 3 way handshake to open a connection to c3fbackup on port 445. > > What process is is listening on port 445 on this machine ? This is not Samba.... > > 445 is the "new" SMB port used by Win2k. > > Jeremy.I see. Do you know if there is something that I can configure within Samba to get it to listen on port 445 as well as port 139? or if there is something I should update within the OS configuration? or on the client? or? Thanks, Carrie
On Sat, Dec 22, 2001 at 10:09:33AM -0600, Carrie Knox wrote:> > I see. Do you know if there is something that I can configure within Samba to get it to > listen on port 445 as well as port 139? or if there is something I should update within the > OS configuration? or on the client? or?No, Samba does not yet listen on 445 (there are NetBIOS aliasing reasons for this). *Something* on your machine is accepting TCP connections on port 445, after which the client is dropping the 139 connection. I suggest you find out what it is.... Jeremy.