samba - Oct 2010 - Random winbind cannot check secret errors

Hi All,

Debian Lenny, Samba 3.4.8

Every 5 minutes I have a script running checking that it can still talk
to the AD domain controllers (2008 R2) using the command wbinfo -t. This
was running without error for many months, until recently it will
randomly not be able to communicate with the DC and will provide the
error 

"error: code was NT_STATUS_UNSUCCESSFUL (0xc0000001) 
Could not check secret"

This doesn't appear to affect connectivity (or if it does it hasn't been
caught) and it is always working correctly again by the time the next
check runs (5 minutes). The windows logs dont show anything.

Any ideas? Is the check too aggressive? Does anyone else monitor
winbindd in another way to see if it has lost trust with its DC?

Regards,
Mark

Anyone with views on this? How do you monitor that your file servers can
connect to your domain controllers?

On Thu, Oct 14, 2010 at 12:43:24PM +0100, Mark Adams
wrote:
> Hi All,
> 
> Debian Lenny, Samba 3.4.8
> 
> Every 5 minutes I have a script running checking that it can still talk
> to the AD domain controllers (2008 R2) using the command wbinfo -t. This
> was running without error for many months, until recently it will
> randomly not be able to communicate with the DC and will provide the
> error 
> 
> "error: code was NT_STATUS_UNSUCCESSFUL (0xc0000001) 
> Could not check secret"
> 
> This doesn't appear to affect connectivity (or if it does it hasn't
been
> caught) and it is always working correctly again by the time the next
> check runs (5 minutes). The windows logs dont show anything.
> 
> Any ideas? Is the check too aggressive? Does anyone else monitor
> winbindd in another way to see if it has lost trust with its DC?
> 
> Regards,
> Mark
> -- 
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba