[Samba] Winbindd and idletimeout on the LDAP server

Mikael M. Hansen mhansen at cs.aau.dk
Mon Nov 20 14:12:59 GMT 2006


Hi

We have a problem with samba (winbind) when we enable idletimeout on the
OpenLDAP servers. If it is set we sometimes get an error:

mhansen at scenic32:~> smbclient -Umhansen //cups/p6
Password:
session setup failed: NT_STATUS_IO_TIMEOUT

The log entries (log.wb-DOMAIN)on the DOMAIN MEMBER server (cups in this
case) are:

[2006/11/20 14:24:07, 0] rpc_client/cli_pipe.c:rpc_api_pipe(790)
  rpc_api_pipe: Remote machine BDC pipe \NETLOGON fnum 0x7357returned
critical error. Error was Call timed out: server did not respond after
10000 milliseconds
[2006/11/20 14:24:07, 1] libsmb/clientgen.c:cli_rpc_pipe_close(376)
  cli_rpc_pipe_close: cli_close failed on pipe \NETLOGON, fnum 0x7357 to
machine BDC.  Error was Call timed out: server did not respond after
10000 milliseconds

It should be said that we sometimes also see the same errors when the
connection is successful. I would like to include some more debug info
from the BDC/PDC server involved in the connection. But I need some info
on which part of samba to increase the log for.



If we remove the idletimeout from the ldap servers we no longer get this
type of errors.

Is it possible that samba does not check if the connection to the LDAP
is still valid (not closed on the server side) and returns an error -
due to the timeout - to the client rather than re-establishing the
connection?


-- 
MVH / Best regards

Mikael M. Hansen             	



More information about the samba mailing list