Samba - varovne hlasky

[URBAN Leos]

Tady posilam informaci o tom, ze se to asi da opravdu tise ignorovat.
Je to z diskuzni skupiny linux.samba od pana Daniela Pavla.
Ja jeste dodam, ze ten port 445 jde v registrech zrejme zakazat:
http://www.petri.co.il/what_is_port_445_in_w2kxp.htm

A ted slibena citace:
I've seen this issue come up over and over on the mailing list, and yet
never make it in the FAQ.  At some point I've slammed into it as well,
and had to solve it.

Don't exactly remember where I've found the solution, but it goes
something like this:

Windows (XP?) tries to connect on both ports 139 and 445, not knowing
what SMB version the remote machine supports.   When it makes a
successful connection on one of the ports (139), it drops the other, and
samba gets noisy about it.

It you have a mixed windows environment (XP's, and older ones), you
might need both ports open.  But if you only have XP's, you can safely put a
         smb ports = 139
in your samba.conf file, and the useless messages will dissapear.  Even
if you have a mixed environment, you should probably try this and see
how it goes.

I am quite sure I got the actual technical details rather wrong -- I've
read about this a long time ago, so please, somebody correct me.
However, I am also quite sure the solution works :).


URBAN Leos napsal(a):
> Ahoj,
> rad bych se optal zda nekdo nema vice informaci o nasledujicim:
> 
> Samba 3.0.14a (FC4) v pocitacove siti asi 15 pececek (mix Win98, 
> Win2000, WinXP) pise cas od casu (nekolikrat denne) nasledujici hlasky:
> 
> lib/util_sock.c:get_peer_addr(1150)
> getpeername failed. Error was Transport endpoint is not connected
> lib/util_sock.c:get_peer_addr(1150)
> getpeername failed. Error was Transport endpoint is not connected
> lib/access.c:check_access(328)
> lib/util_sock.c:get_peer_addr(1150)
> getpeername failed. Error was Transport endpoint is not connected
> Denied connection from  (0.0.0.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
> lib/util_sock.c:write_socket_data(430)
> write_socket_data: write failure. Error = Connection reset by peer
> lib/util_sock.c:write_socket(455)
> write_socket: Error writing 5 bytes to socket 24: ERRNO = Connection 
> reset by peer
> lib/util_sock.c:send_smb(647)
> Error writing 5 bytes to client. -1. (Connection reset by peer)
> 
> Zajimava je adresa: 0.0.0.0 ??
> 
> Narozdil od ruznych zprav na internetu i tady nedochazi k zadnemu 
> viditelnemu omezeni. Samba nepada, nikdo si nestezuje na ztraty dat, 
> server vypada dikybohu stabilni.
> 
> Na internetu jsou ruzne typy, jeden z nich se mi libi :-)
> Je to udajne zpusobeno soubeznym odesilanim paketu na portech 445 a 139 
> od klienta s tim, ze jak dostane klient Windows odpoved, uzavre OBA 
> porty. Jenze samba se snazi vyridit i ten druhy pozadavek ale port je 
> jiz uzavren. Proto chybova hlaska.
> 
> Otazka je, jestli to neni necim jinym a neni to predzvest nejake 
> katastrofy....
> 
> Mate nekdo nejakou zkusenost?
> 
> Diky moc,
> Leos