[Samba] Errors

[John H Terpstra]

On Thu, 20 Mar 2003, Davide Parise wrote:

> It often happen to me that I try to open a file on a samba (2.2.8, but was
> the same with 3) and the share is not avaliable. I get this errors:
>
> [2003/03/16 13:24:47, 0] lib/util_sock.c:get_socket_addr(958)
>   getpeername failed. Error was Transport endpoint is not connected
> [2003/03/17 08:43:14, 0] lib/util_sock.c:get_socket_addr(958)
>   getpeername failed. Error was Transport endpoint is not connected
> [2003/03/18 06:21:36, 0] lib/util_sock.c:get_socket_addr(958)
>   getpeername failed. Error was Transport endpoint is not connected
> [2003/03/19 09:23:49, 0] lib/util_sock.c:get_socket_addr(958)
>   getpeername failed. Error was Transport endpoint is not connected
> [2003/03/20 09:18:56, 0] lib/util_sock.c:get_socket_addr(958)
>   getpeername failed. Error was Transport endpoint is not connected
>
>
> If then I try twice or three time everything works.
>
> Any idea?

Too much guessing going on here. Crystal ball is worn out. Maybe you can
give some more information. Things like your smb.conf file and how you
start samba (ie: inetd or running as daemons) would help us to help you.

- John T.

>
> THX
>
> Davide Parise
> E-Mail: d.parise at iskranet.it
> Cel.: +39 3333063640
> FAX:  +39 06233241981
>
>

-- 
John H Terpstra
Email: jht at samba.org