Primary domain's status in winbindd child process is not consistent with the parent winbindd process.

[Jeremy Allison]

On Mon, Jun 02, 2008 at 09:20:55PM -0600, Bo Yang wrote:
> 
> It will. function call stack is showed below:
> 
> winbindd_dual_pam_auth() ----> winbindd_dual_pam_auth_samlogon() [because domain B(Pb, trusted domain) is online] ---->
> 
> because we are domain member, not DC, contact_domain = find_our_domain(); and then result = cm_connect_netlogon(contact_domain, &netlogon_pipe);
> 
> ie, cm_connect_netlogon() is called to contact the primary domain(domain A) ------> init_dc_connection(), here is the problem. If the status of primary domain is not 
> updated in Pb, the status is always initialized and offline. Please have a look at 
> 
>         if (domain->initialized && !domain->online) {
>                 /* We check for online status elsewhere. */
>                 return NT_STATUS_DOMAIN_CONTROLLER_NOT_FOUND;
>         }
> in init_dc_connection(), which always returns NT_STATUS_DOMAIN_CONTROLLER_NOT_FOUND.
> 
> Please keep in touch if there is anything I was wrong or I didn't explain clearly.

Ok, that makes perfect sense - thanks for the explaination.

Jeremy.