Hi!
I've set up a Samba server (running winbind) as a Win domain member
server.
Users authenticated from win domain and mapped to NIS
uids and gids.
Everything was working well, but the next morning winbind
stopped to respond.
I reset it, so now I get wbinfo, ypbind (ypcat) results
ok as before, but users suddenly cannot authenticate any more.
They get the NT_STATUS_ACCESS_DENIED error.
My <client>.log files are empty, winbindd files say that
server is not responding.
[2004/09/28 14:00:10, 0] rpc_client/cli_pipe.c:rpc_api_pipe(435)
cli_pipe: return critical error. Error was Call timed out: server did
not respond after 10000 milliseconds
[2004/09/28 14:00:20, 0] rpc_client/cli_pipe.c:rpc_api_pipe(435)
cli_pipe: return critical error. Error was Call timed out: server did
not respond after 10000 milliseconds
Could that mean that the smb server is not a domain member any more.
I've got no access to the Win PDF at the time.
Thanks,
Borut
I've set up a Samba server (running winbind) as a Win domain member
server.
Users authenticated from win domain and mapped to NIS
uids and gids.
Everything was working well, but the next morning winbind
stopped to respond.
I reset it, so now I get wbinfo, ypbind (ypcat) results
ok as before, but users suddenly cannot authenticate any more.
They get the NT_STATUS_ACCESS_DENIED error.
My <client>.log files are empty, winbindd files say that
server is not responding.
[2004/09/28 14:00:10, 0] rpc_client/cli_pipe.c:rpc_api_pipe(435)
cli_pipe: return critical error. Error was Call timed out: server did
not respond after 10000 milliseconds
[2004/09/28 14:00:20, 0] rpc_client/cli_pipe.c:rpc_api_pipe(435)
cli_pipe: return critical error. Error was Call timed out: server did
not respond after 10000 milliseconds
Could that mean that the smb server is not a domain member any more.
I've got no access to the Win PDF at the time.
Thanks,
Borut