[Samba] Winbindd problems ... nevers answered ?
Phibee Network operation Center
noc at phibee.net
Tue Jun 7 08:28:51 GMT 2005
Hi
i have 3 PDC on my network, and after reboot the first PDC, my winbindd
can't call with it :
[root at gw squid]# wbinfo -t
checking the trust secret via RPC calls failed
error code was NT_STATUS_INVALID_COMPUTER_NAME (0xc0000122)
Could not check secret
[2005/06/07 10:20:30, 3]
nsswitch/winbindd_misc.c:winbindd_interface_version(261)
[22308]: request interface version
[2005/06/07 10:20:30, 3]
nsswitch/winbindd_misc.c:winbindd_priv_pipe_dir(297)
[22308]: request location of privileged pipe
[2005/06/07 10:20:30, 3]
nsswitch/winbindd_misc.c:winbindd_check_machine_acct(41)
[22308]: check machine account
[2005/06/07 10:20:30, 3] nsswitch/winbindd_cm.c:cm_get_ipc_userpass(109)
cm_get_ipc_userpass: No auth-user defined
[2005/06/07 10:20:31, 0] rpc_client/cli_netlogon.c:cli_nt_setup_creds(256)
cli_nt_setup_creds: request challenge failed
[2005/06/07 10:20:31, 3] nsswitch/winbindd_cm.c:cm_prepare_connection(387)
schannel refused - continuing without schannel
(NT_STATUS_INVALID_COMPUTER_NAME)
[2005/06/07 10:20:31, 0] rpc_client/cli_netlogon.c:cli_nt_setup_creds(256)
cli_nt_setup_creds: request challenge failed
[2005/06/07 10:20:31, 3]
nsswitch/winbindd_misc.c:winbindd_check_machine_acct(68)
could not open handle to NETLOGON pipe
[2005/06/07 10:20:31, 2]
nsswitch/winbindd_misc.c:winbindd_check_machine_acct(98)
Checking the trust account password returned
NT_STATUS_INVALID_COMPUTER_NAME
i restart winbindd and now i have
[root at gw samba]# wbinfo -t
checking the trust secret via RPC calls succeeded
[root at gw samba]#
only whith a stop/start
1- Why Winbindd don't "reconnect" to the PDC when he lose the connection ?
2- Why he don't sent the request to the second PDC when the first are died ?
3- Can i put a script for auto detection if the connexion are good ?
4- Into my smb.conf, i have :
security = domain
password server = *
i can specify a list of IP/PDC for he sent the request ?
Please help me to understand this problems.
More information about the samba
mailing list