|
|
|
|
| kinit(v5): Client not found in Kerberos database while getting initial credentials |
|---|
|
Problem:
I'm trying to configure a Linux server with Samba to run as member of a Windows domain. After configuring and starting krb5kdc and kadmin, I try to run "kinit" but get the following error message:
kinit(v5): Client not found in Kerberos database while getting initial credentials
|
|
Solution:
kinit doesn't know what login name to use, so it tries the current user (probably root) but that login name does not exist in the KDC database because that's a Windows domain controller. Try using a login name that Windows knows about:
$ kinit Administrator@LAN.ATC.NO
Password for Administrator@LAN.ATC.NO:
If you specify the correct password, you should now have a kerberos ticket in the cache:
$ klist
Ticket cache: FILE:/tmp/krb5cc_0
Default principal: Administrator@LAN.ATC.NO
Valid starting Expires Service principal
05/11/09 17:26:16 05/12/09 03:24:38 krbtgt/LAN.ATC.NO@LAN.ATC.NO
renew until 05/12/09 17:26:16
Finally, try "kinit" again without no parameters:
$ kinit
Password for Administrator@LAN.ATC.NO:
This solution worked for me on two completely different networks, but please keep in mind that there are about two million other things that could be wrong, so don't blame me if it doesn't work for you. Would love to hear about it either way though :-)
|
|
|
|
|
|
This is free technical advice without any warranties.
Use at your own risk. Solutions offered may not apply to your particular problem at all.
Opinions and views expressed in the articles are the authors' personal
and may not necessarily reflect or coincide with those of Ano-Tech Computers.
We take no responsibility if anything bad happens from following any of
the intructions given. If you don't understand and accept this, please
contact us for personal assistance instead.
To read our full disclaimer, go
here.
We welcome anyone who is willing to contribute to this public knowledge base,
contact siteadmin@atc.no
if you have information you would like to share. The idea is not to replace
the commercial support sites, but to publish those hard-to-find
solutions you've found yourself looking for over and over again.
Show all articles
