[LUGOS] Problemi s sambo
Davor Guttierrez
davor at guttierrez.org
Thu May 20 16:28:15 CEST 2004
Hi
Ali je možno da je problem zaradi master browser electiona?
Kaj če bi v [global] dodal še os level = 254.
LP,
D.
On Thu, 2004-05-20 at 14:10, tomaz at sms-send.net wrote:
> Zdravo,
>
> ena mašina mi bo vse živce pobrala :(
>
> Zadeva je sledeča, Fedora Core 1 z zadnjimi popravki, samba-3.0.4-1.FC1.
> Problem je v tem, da ko se winXP klient poskuša povezati preko sambe na to
> mašino, jo lepo vidi, ko klikne na njo vidi tudi share Ko pa klikne na
> katerega od sharov, explorer zmrzne za par minut (5-10). Po tem času pa
> prikaže vsebino shara in z datotekami je možno delati brez problema (tudi
> s poddirektoriji in drugimi share-i). Ko pa je povezava nekaj časa
> neaktivna, se pa celotna zgodba ponovi. Poskušal sem se povezati tudi
> preko total commanderja pa je ista zgodba.
>
> Pri vsem tem pa drugi protokoli delujejo brez problemov (http, ftp, ssh,
> swat, svn). Pred FC1 je na tej mašini bil Suse 7.0 s sambo 2.x.x z enakim
> problemom. Kasneje sem nadgradil Sambo na 3.0.1 , pa je bilo samo še
> slabše.
>
> Danes sem zamenjal celo NIC in ni imelo nobenega efekta.
>
> Če ima kako vezo, v mašini je še ISDN kartica, ki pa ni aktivna.
>
> smb.conf:
>
> [global]
> workgroup = RAZVOJ
> server string = Linux Fedora Core 1
> log file = /var/log/samba/smbd.log
> max log size = 50
> socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
> dns proxy = No
> ldap ssl = no
> create mask = 0774
> directory mask = 0775
>
> [homes]
> comment = Home Directories
> read only = No
> browseable = No
>
> [www]
> comment = Webi
> path = /www
> read only = No
>
> Na starem SuSe 7.0 ni v logu bilo nobene napake, FC1 pa javlja:
>
> [2004/05/20 14:07:18, 1] smbd/service.c:make_connection_snum(619)
> tomaz (192.168.0.11) connect to service prg initially as user tomazd
> (uid=500, gid=100) (pid 2593)
> [2004/05/20 14:08:11, 1] smbd/service.c:close_cnum(801)
> tomaz (192.168.0.11) closed connection to service prg
> [2004/05/20 14:09:18, 1] smbd/service.c:make_connection_snum(619)
> tomaz (192.168.0.11) connect to service prg initially as user tomazd
> (uid=500, gid=100) (pid 2593)
> [2004/05/20 14:10:27, 1] smbd/service.c:close_cnum(801)
> tomaz (192.168.0.11) closed connection to service prg
> [2004/05/20 14:25:47, 0] lib/util_sock.c:get_peer_addr(978)
> getpeername failed. Error was Transport endpoint is not connected
> [2004/05/20 14:25:47, 0] lib/util_sock.c:get_peer_addr(978)
> getpeername failed. Error was Transport endpoint is not connected
> [2004/05/20 14:25:47, 0] lib/util_sock.c:write_socket_data(413)
> write_socket_data: write failure. Error = Connection reset by peer
> [2004/05/20 14:25:47, 0] lib/util_sock.c:write_socket(438)
> write_socket: Error writing 4 bytes to socket 7: ERRNO = Connection
> reset by peer
> [2004/05/20 14:25:47, 0] lib/util_sock.c:send_smb(630)
> Error writing 4 bytes to client. -1. (Connection reset by peer)
> [2004/05/20 14:46:47, 0] lib/util_sock.c:get_peer_addr(978)
> getpeername failed. Error was Transport endpoint is not connected
> [2004/05/20 14:46:47, 0] lib/util_sock.c:get_peer_addr(978)
> getpeername failed. Error was Transport endpoint is not connected
> [2004/05/20 14:46:47, 0] lib/util_sock.c:write_socket_data(413)
> write_socket_data: write failure. Error = Connection reset by peer
> [2004/05/20 14:46:47, 0] lib/util_sock.c:write_socket(438)
> write_socket: Error writing 4 bytes to socket 24: ERRNO = Connection
> reset by peer
> [2004/05/20 14:46:47, 0] lib/util_sock.c:send_smb(630)
> Error writing 4 bytes to client. -1. (Connection reset by peer)
>
>
> Malo sem gledal tudi po groups.google.com, pa očitno nisem edini s tem
> problemom:
> http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&threadm=9kn1he%24i5d%241%40news.imp.ch&rnum=1&prev=/groups%3Fq%3DSamba%2Bmakes%2BExplorer%2Bcrash%26hl%3Den%26lr%3D%26ie%3DUTF-8%26selm%3D9kn1he%2524i5d%25241%2540news.imp.ch%26rnum%3D1
>
> Lp,Tomaz
--
Lep pozdrav,
Davor Guttierrez
http://www.d-mashina.net
davor at guttierrez.org
davor.guttierrez at d-mashina.net
"sounds like a Windows problem, try calling Microsoft support"
More information about the lugos-list
mailing list