Displaying 2 results from an estimated 2 matches for "magosanyi1a313".
2009 May 28
0
wbinfo -K not working
...em, so here I am.
This problem is a showstopper for me. (I can login by changing pam_winbind
to pam_krb5, but this does not cache credentials, so I cannot work at home.)
Additional informations I figured out:
- According to wireshark, winbind (wbinfo -K) tries to authenticate the
principal 'RESmagosanyi1a313' instead of 'magosanyi1a313'
- There are logs saying "Cannot resolve network address for KDC in requested
realm" and "Could not receive trustdoms", which may or may not related to
the problem. (see detailed logs below)
original problem:
Works:
kinit
wbinfo -u...
2009 May 29
0
solution: wbinfo -K not working
...roblem is a showstopper for me. (I can login by changing pam_winbind
> to pam_krb5, but this does not cache credentials, so I cannot work at home.)
>
> Additional informations I figured out:
> - According to wireshark, winbind (wbinfo -K) tries to authenticate the
> principal 'RESmagosanyi1a313' instead of 'magosanyi1a313'
> - There are logs saying "Cannot resolve network address for KDC in
> requested realm" and "Could not receive trustdoms", which may or may not
> related to the problem. (see detailed logs below)
>
> original problem:
>...