[Samba] 3.0.22-solaris10 - Please help !

[Pierre MARC]

Hi Andrea,

Thanks for your anwer, but I don't think that is the same problem.
In my case, there isn't any firewall between the samba pdc and the
windows clients.
I suppose some mismatch between the sockets calls from samba and
solaris...
But as I'm not a programmer, it's very difficult to me to explain the
trouble.
Le ven 16/06/2006 à 16:51, Andrea Battaglia a écrit :

> Hi Pierre,
> 
> I don't know about the 'set socket option' issue, but the broken pipe,
> write failure and client locking all look familiar to me.  I posted a
> message about them a couple of days ago.  In my case, it was a problem
> with my firewall settings - in particular, using the 'established'
> option on an ipfw rule caused some packets from the client to be
> rejected at port 445.
> 
> Here's my original message for reference...
> 
> ------------------------
> 
> Over the last few weeks I've had problems using Samba on a FreeBSD.
> Windows XP clients (that's all I have) would experience intermittent
> long delays (lockups, freezing) when accessing the samba shares using
> Windows Explorer or any other applications.  This occurred both directly
> when browsing the network neighborhood, and when accessing the share
> through a letter drive mapping.
>  
> Here's a snippet of my log file showing the smbd errors:
>  
> Jun 13 17:41:04 foobar smbd[544]: [2006/06/13 17:41:04, 0]
> lib/util_sock.c:read_data(529)
> Jun 13 17:41:04 foobar kernel: Jun 13 17:41:04 foobar smbd[544]:
> [2006/06/13 17:41:04, 0] lib/util_sock.c:read_data(529)
> Jun 13 17:41:04 foobar smbd[544]:   read_data: read failure for 4 bytes
> to client 192.168.0.108. Error = Operation timed out
> Jun 13 17:41:04 foobar kernel: Jun 13 17:41:04 foobar smbd[544]:
> read_data: read failure for 4 bytes to client 192.168.0.108. Error =
> Operation timed out
> Jun 13 17:41:04 foobar smbd[544]: [2006/06/13 17:41:04, 0]
> lib/util_sock.c:write_data(557)
> Jun 13 17:41:04 foobar kernel: Jun 13 17:41:04 foobar smbd[544]:
> [2006/06/13 17:41:04, 0] lib/util_sock.c:write_data(557)
> Jun 13 17:41:04 foobar smbd[544]:   write_data: write failure in writing
> to client 192.168.0.108. Error Broken pipe
> Jun 13 17:41:04 foobar kernel: Jun 13 17:41:04 foobar smbd[544]:
> write_data: write failure in writing to client 192.168.0.108. Error
> Broken pipe
> Jun 13 17:41:04 foobar smbd[544]: [2006/06/13 17:41:04, 0]
> lib/util_sock.c:send_smb(765)
> Jun 13 17:41:04 foobar kernel: Jun 13 17:41:04 foobar smbd[544]:
> [2006/06/13 17:41:04, 0] lib/util_sock.c:send_smb(765)
> Jun 13 17:41:04 foobar smbd[544]:   Error writing 75 bytes to client.
> -1. (Broken pipe)
> Jun 13 17:41:04 foobar kernel: Jun 13 17:41:04 foobar smbd[544]:   Error
> writing 75 bytes to client. -1. (Broken pipe)
>  
> For a short while, the XP clients were also experiencing problems with
> mapped drive letters not reconnecting or losing their connection.  This
> dialog would appear:
>  
>     An error occurred while reconnecting G: to \\foobar\folder.
>     Microsoft Windows Network:
>     The local device name is already in use.
>     The connection has not been restored.
>  
> I came across this posting
> http://lists.freebsd.org/pipermail/freebsd-ipfw/2005-July/001925.html
> and added some logging to my ipfw firewall, which showed that some
> packets coming from the clients to port 445 were being denied by a rule
> with the 'established' option..  I removed the rule with the ipfw
> established option.  This corrected all the symptoms I indicated above.
>  
> # This rule causes problems with Windows Networking clients
> # ipfw -q add 00235 deny log tcp from any to any in established
>  
> System info...
>  
> FreeBSD 6.1-RELEASE GENERIC i386
> 
> samba-3.0.22,1      A free SMB and CIFS client and server for UNIX
> 
> Andy
> 
> -----Original Message-----
> From: samba-bounces+andrea=kobayashi.ca at lists.samba.org
> [mailto:samba-bounces+andrea=kobayashi.ca at lists.samba.org] On Behalf Of
> Pierre MARC
> Sent: Friday, June 16, 2006 10:45 AM
> To: samba at lists.samba.org
> Subject: [Samba] 3.0.22-solaris10 - Please help !
> 
> Hi !!
> 
> 
> I have already sent this message to the list, but, as I have not
> received
> any replies, I am trying again !!
> 
> 
> I have Samba 3.0.22 running as PDC on solaris10.
> 
> Each time a windows client (XP SP2 or W2003) opens an explorer to access
> a share, I see in the log.smbd :
> 
> [2006/06/15 01:28:08, 0] lib/util_sock.c:get_peer_addr(1225)
>   getpeername failed. Error was Invalid argument
> [2006/06/15 01:28:08, 0] lib/util_sock.c:set_socket_options(261)
>   Failed to set socket option SO_KEEPALIVE (Error Invalid argument)
> [2006/06/15 01:28:08, 0] lib/util_sock.c:set_socket_options(261)
>   Failed to set socket option TCP_NODELAY (Error Invalid argument)
> [2006/06/15 01:28:08, 0] lib/util_sock.c:get_peer_addr(1225)
>   getpeername failed. Error was Invalid argument
> 
> And in same time in the log.%R :
> 
> [2006/06/15 01:28:08, 0] lib/util_sock.c:write_data(557)
>   write_data: write failure in writing to client 192.168.202.5. Error
> Broken pipe
> [2006/06/15 01:28:08, 0] lib/util_sock.c:send_smb(765)
>   Error writing 4 bytes to client. -1. (Broken pipe)
> 
> And it seems the windows explorer freezes in the same time, with
> sometime an mrxsmb event message.
> 
> I've seen that the getpeername message is not a problem. OK for that.
> 
> But I haven't seen any answer about the set socket option (Error invalid
> argument).
> What does it means ?
> Is it a real problem ?
> Is it particular to solaris ?
> I have found similar questions in the samba list, since Jan-2005, but
> ... no answer.
> 
> Please, help !
> -- 
> Pierre MARC <pierre.marc at id3.eu>
> id3 Semiconductors

-- 
Pierre MARC <pierre.marc at id3.eu>
id3 Semiconductors