PDA

Archiv verlassen und diese Seite im Standarddesign anzeigen : Samba trennt TCP/IP Verbindung



killer23
22.03.05, 13:40
Hallo zusammen,

ich hab einen SLES 9 auf einem Dell Rechner mit GB Netzkarte. Ssoweit läuft auch alles toll bis auf der Samba trennt die Verbindung regelmäßig mit folgendem log:


Mar 22 14:25:48 ds1 smbd[29769]: [2005/03/22 14:25:48, 0] lib/util_sock.c:get_peer_addr(978)
Mar 22 14:25:48 ds1 smbd[29769]: getpeername failed. Error was Transport endpoint is not connected
Mar 22 14:25:48 ds1 smbd[29769]: [2005/03/22 14:25:48, 0] lib/util_sock.c:write_socket_data(413)
Mar 22 14:25:48 ds1 smbd[29769]: write_socket_data: write failure. Error = Connection reset by peer
Mar 22 14:25:48 ds1 smbd[29769]: [2005/03/22 14:25:48, 0] lib/util_sock.c:write_socket(438)
Mar 22 14:25:48 ds1 smbd[29769]: write_socket: Error writing 4 bytes to socket 5: ERRNO = Connection reset by peer
Mar 22 14:25:48 ds1 smbd[29769]: [2005/03/22 14:25:48, 0] lib/util_sock.c:send_smb(630)
Mar 22 14:25:48 ds1 smbd[29769]: Error writing 4 bytes to client. -1. (Connection reset by peer)
Mar 22 14:25:48 ds1 smbd[29771]: [2005/03/22 14:25:48, 0] lib/util_sock.c:get_peer_addr(978)
Mar 22 14:25:48 ds1 smbd[29771]: getpeername failed. Error was Transport endpoint is not connected
Mar 22 14:25:48 ds1 smbd[29771]: [2005/03/22 14:25:48, 0] lib/util_sock.c:get_peer_addr(978)
Mar 22 14:25:48 ds1 smbd[29771]: getpeername failed. Error was Transport endpoint is not connected
Mar 22 14:25:48 ds1 smbd[29771]: [2005/03/22 14:25:48, 0] lib/util_sock.c:write_socket_data(413)
Mar 22 14:25:48 ds1 smbd[29771]: write_socket_data: write failure. Error = Connection reset by peer
Mar 22 14:25:48 ds1 smbd[29771]: [2005/03/22 14:25:48, 0] lib/util_sock.c:write_socket(438)
Mar 22 14:25:48 ds1 smbd[29771]: write_socket: Error writing 4 bytes to socket 5: ERRNO = Connection reset by peer
Mar 22 14:25:48 ds1 smbd[29771]: [2005/03/22 14:25:48, 0] lib/util_sock.c:send_smb(630)
Mar 22 14:25:48 ds1 smbd[29771]: Error writing 4 bytes to client. -1. (Connection reset by peer)
Mar 22 14:25:51 ds1 dhcpd: DHCPREQUEST for 192.168.0.6 from 00:11:11:91:31:86 via eth0
Mar 22 14:25:51 ds1 dhcpd: DHCPACK on 192.168.0.6 to 00:11:11:91:31:86 via eth0
Mar 22 14:25:51 ds1 smbd[29849]: [2005/03/22 14:25:51, 0] lib/util_sock.c:get_peer_addr(978)
Mar 22 14:25:51 ds1 smbd[29849]: getpeername failed. Error was Transport endpoint is not connected
Mar 22 14:25:51 ds1 smbd[29849]: [2005/03/22 14:25:51, 0] lib/util_sock.c:write_socket_data(413)
Mar 22 14:25:51 ds1 smbd[29849]: write_socket_data: write failure. Error = Connection reset by peer
Mar 22 14:25:51 ds1 smbd[29849]: [2005/03/22 14:25:51, 0] lib/util_sock.c:write_socket(438)
Mar 22 14:25:51 ds1 smbd[29849]: write_socket: Error writing 4 bytes to socket 5: ERRNO = Connection reset by peer
Mar 22 14:25:51 ds1 smbd[29849]: [2005/03/22 14:25:51, 0] lib/util_sock.c:send_smb(630)
Mar 22 14:25:51 ds1 smbd[29849]: Error writing 4 bytes to client. -1. (Connection reset by peer) #

wäre toll wenn mir einer von euch helfen kann was hier das problem ist.

gruß Axel

emba
23.03.05, 17:18
nicht der samba trennt, sondern der client

sind sicherlich 2k/xp client, die eine session zu 139 bzw. 445 aufmachen und dann eine der beiden schließen, nachdem sie erfolgreich connected sind

greez