Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 1 reply
  • Subscribers 3 subscribers
  • Views 8790 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

kinit succeeded but ads_sasl_spnego_krb5_bind failed

torrentho
Hello All,
Thanks in Advance,

After the join in domain windows 2003 we have receiving below error continually.
We have one domain and one additional domain controller. 
Please help or give some suggestion.



2012:07:21-12:54:55 FW_INTRA_HO [daemon:err] winbindd[10616]: kinit succeeded but ads_sasl_spnego_krb5_bind failed: Cannot contact any KDC for requested realm
2012:07:21-12:55:12 FW_INTRA_HO [daemon:err] winbindd[10437]: [2012/07/21 12:55:12.844876, 0] libads/sasl.c:912(ads_sasl_spnego_bind)


This thread was automatically locked due to age.
Parents
  • 0
    Sounds like you pointed the configuration to your FQDN of the DC. Unless you pointed Astaro to the internal DNS servers on the DC, it will be unable to resolve the hostname of your DC.

    Either change the configuration to look at IP address for your DC, or point the DNS configuration to the DNS service on your DC.

    Kerberos errors are almost always DNS related.
Reply
  • 0
    Sounds like you pointed the configuration to your FQDN of the DC. Unless you pointed Astaro to the internal DNS servers on the DC, it will be unable to resolve the hostname of your DC.

    Either change the configuration to look at IP address for your DC, or point the DNS configuration to the DNS service on your DC.

    Kerberos errors are almost always DNS related.
Children
No Data