• Willkommen im Linux Club - dem deutschsprachigen Supportforum für GNU/Linux. Registriere dich kostenlos, um alle Inhalte zu sehen und Fragen zu stellen.

Samba Fehler: Server stopped responding

cavessa

Newbie
Hallo,

bei meinem Ubuntu Server mit Squid Anbindung kommt es immer wieder zu Verbindungsabbrüche. In der Samba Logfile steht folgender Fehler:

Code:
[2010/02/25 14:38:23,  0] lib/util_sock.c:read_socket_with_timeout(1014)
  read_socket_with_timeout: timeout read. read error = Connection reset by peer.
[2010/02/25 14:38:23,  0] libsmb/clientgen.c:cli_receive_smb(165)
  Receiving SMB: Server stopped responding
[2010/02/25 14:38:23,  0] rpc_client/cli_pipe.c:rpc_api_pipe(914)
  rpc_api_pipe: host zs01.Domain.local, pipe \NETLOGON, fnum 0x4000 returned critical error. Error was Read error: Connection reset by peer
[2010/02/25 14:38:36,  1] rpc_client/cli_pipe.c:rpc_pipe_destructor(2362)
  rpc_pipe_destructor: cli_close failed on pipe host zs01.Domain.local, pipe \samr, fnum 0xc002. Error was Read error: Success
[2010/02/25 14:38:36,  1] rpc_client/cli_pipe.c:rpc_pipe_destructor(2362)
  rpc_pipe_destructor: cli_close failed on pipe host zs01.Domain.local, pipe \lsarpc, fnum 0x800f. Error was Read error: Success
[2010/02/25 14:38:36,  1] rpc_client/cli_pipe.c:rpc_pipe_destructor(2362)
  rpc_pipe_destructor: cli_close failed on pipe host zs01.Domain.local, pipe \NETLOGON, fnum 0x4000. Error was Read error: Success
[2010/02/25 14:52:41,  0] libsmb/clientgen.c:cli_receive_smb(165)
  Receiving SMB: Server stopped responding
[2010/02/25 14:52:41,  0] rpc_client/cli_pipe.c:rpc_api_pipe(914)
  rpc_api_pipe: host zs01.Domain.local, pipe \NETLOGON, fnum 0xc048 returned critical error. Error was Call timed out: server did not respond after 10000 milliseconds
[2010/02/25 14:53:01,  1] rpc_client/cli_pipe.c:rpc_pipe_destructor(2362)
  rpc_pipe_destructor: cli_close failed on pipe host zs01.Domain.local, pipe \samr, fnum 0x42. Error was Call timed out: server did not respond after 1000 milliseconds
[2010/02/25 14:53:01,  1] rpc_client/cli_pipe.c:rpc_pipe_destructor(2362)
  rpc_pipe_destructor: cli_close failed on pipe host zs01.Domain.local, pipe \lsarpc, fnum 0x3e. Error was Call timed out: server did not respond after 500 milliseconds
[2010/02/25 14:53:01,  1] rpc_client/cli_pipe.c:rpc_pipe_destructor(2362)
  rpc_pipe_destructor: cli_close failed on pipe host zs01.Domain.local, pipe \NETLOGON, fnum 0xc048. Error was Call timed out: server did not respond after 500 milliseconds

Was ist das für ein Fehler?

smb.conf:

Code:
[global]

## Browsing/Identification ###

# Change this to the workgroup/NT-domain name your Samba server will part of
workgroup = DOMAIN
security = ADS
realm = DOMAIN.LOCAL
password server = 172.16.190.1

# winbind separator = +
idmap uid = 10000-20000
idmap gid = 10000-20000
winbind enum users = yes
winbind enum groups = yes
template homedir = /home/%U
template shell = /bin/bash
client use spnego = yes
client ntlmv2 auth = yes
encrypt passwords = yes
winbind use default domain = yes
restrict anonymous = 2
# to avoid the workstation from
# trying to become a master browser
# on your windows network add the
# following lines
domain master = no
local master = no
preferred master = no
os level = 0

Kann mir da vielleicht jemand helfen?

Gruß
 

stka

Guru
Das Problem wird der winbind sein. aber auch vielleicht dein .local siehe hier:
http://www.it-administrator.de/lexikon/multicast-dns.html
Läuft der nscd? Wenn ja, dann schalte den mal ab, denn winbind und nscd mögen sich nicht wenn du deinen Samba in einen ADS einbindest.
Auch das könnte helfen:
http://forum.univention.de/viewtopic.php?f=22&t=940
 
Oben