/krb5.jabber.keytab
-d kerberos-ha.domain.net
kprop: Client not found in Kerberos database while getting initial
ticket
when trying to kprop the jabber realm. A tcpdump shows no traffic to
the secondary, so this looks like a local issue on the primary. In the
Jabber realm, I have
On 10/26/2011 01:08 PM, fafaforza wrote:
# kprop -r JABBER.DOMAIN.NET -f DUMP.FILE -s /etc/krb5.jabber.keytab
-d kerberos-ha.domain.net
kprop: Client not found in Kerberos database while getting initial
ticket
You didn't mention what version of Kerberos you're using. If it's
On 10/26/2011 1:51 PM, Greg Hudson wrote:
On 10/26/2011 01:08 PM, fafaforza wrote:
# kprop -r JABBER.DOMAIN.NET -f DUMP.FILE -s /etc/krb5.jabber.keytab
-d kerberos-ha.domain.net
kprop: Client not found in Kerberos database while getting initial
ticket
You didn't mention
Date:Sun, 26 Jun 2011 21:42:13 +0200
To: kerberos@mit.edu
From:Jaap Winius jwin...@umrk.nl
Subject: Client not found in Kerberos database
Hi folks,
My site uses Debian squeeze for both workstations and servers with MIT
Kerberos 1.8.3 for authentication. Although
Quoting Marcus Watts m...@umich.edu:
The example you posted appears to have a leading space on the kerberos
principal name. Of course, that could be just the result of reformatting
via your mail client. Generally speaking, control characters including
backspace could result in invisible
It looks like you're right! Every time I see this error occur together
with a correctly spelled name, it includes one or more leading spaces.
However, I find it difficult to imagine that the users are doing this
intentionally. Could it be due to a problem with gdm, the display
manager
version 3.0.10 started.
Copyright Andrew Tridgell and the Samba Team 1992-2004
[2007/05/30 19:14:49, 0]
/SourceCache/samba/samba-100.7/samba/source/libads/kerberos.c:ads_kinit_password(146)
kerberos_kinit_password host/ [EMAIL PROTECTED] failed: Client not
found in Kerberos database
[2007/05/30 19
(Have_KRB5_H and etc.), but no connection..
If i test the conn with:
kinit [EMAIL PROTECTED]
kinit(v5): Client not found in Kerberos database while getting initial
credentials
And if i test with:
kinit [EMAIL PROTECTED]
kinit(v5): Cannot resolve network address for KDC in requested realm while
getting
kadmin
It works from the root account but not from my own. How do I add the
commandline 'kadmin' client to the database?
I've been reading through TFM and any other info I can find but I don't see
a lot of descriptive information for adding users etc to the database, so
I've been
I get this from typing 'kadmin' on the commandline of the KDC server itself.
I have my own account on there which I can log into from gkadmin.
Client not found in Kerberos database while initializing kadmin interface
Regards,
Jason.
--
Jason Oakley +612 82821434
Open
10 matches
Mail list logo