search for: wrongdomain

...configured krb5.conf is in use, winbind will - do SRV lookups, followed by A lookups for the correct list of DCs - connect to one of the DCs, authenticate, and send an RPC_NETLOGON DsrEnumerateDomainTrusts request - get a response to that request, that lists (in order) DEADDOMAIN1, DEADDOMAIN2, WRONGDOMAIN, and DOMAIN (where WRONGDOMAIN is the NT4 domain, DOMAIN is correct, and DEADDOMAINs are trusted domains that no longer exist - I'm not sure why they're still trusted, but I'm told it's necessary) - send a NetrGetAnyDCName request for WRONGDOMAIN to correct DC - get a NetrGet...

...LID_HANDLE (0xc0000008) error messsage was: Invalid handle Could not authenticate user DOMAIN+user with challenge/response Perhaps this is just an error in usage, but I have also tried many other variations (e.g. just user%password, DOMAIN+user - typing password when prompted, etc.) If I use WRONGDOMAIN+user the error does change to NT_STATUS_NO_SUCH_USER, but DOMAIN+wronguser still gives INVALID_HANDLE. The only log entries that seem to correlate to these attempts are in /var/log/log.wb-DOMAIN: [2010/08/17 10:52:48.288391, 2] winbindd/winbindd_pam.c:1724(winbindd_dual_pam_auth) Plain-text...