AIX

Hmm,

When you use telnet you run

Code:

telnet ldap.123.com 88

Tell me the output of this

Also, I am seeing that the

Code:

mkkrb5clnt

syntax is not correctly followed, I specifically mentioned use caps for ONLY '-r' flag and also '-D' is missing.

Make sure you unconfigure 1st.

Also, play around, after you run the above configuration, if it still gives you error try the below

Code:

mkuser -R KRB5Afiles registry= KRB5Afiles SYSTEM= KRB5Afiles PassLine

Then try

Code:

kinit PassLine

I have no kerberos in my environment to check the different scenarios.

Let me know what it comes up with.

I was able to successfully telnet via ldap.123.com 88.

About the command syntax - some docs have used mkkrb5clnt, and others have used config.krb5 (the IBM doc you linked, for example, uses config.krb5.) Is there a reason to use one over the other?

I'll go ahead and unconfigure the current settings and rebuild it, but if I should be starting with one vs the other, it'd be helpful to understand why.

---------- Post updated at 01:39 PM ---------- Previous update was at 01:32 PM ----------

Also, because it may be helpful, this is what the AD admin ran on their end -

Code:

ktpass -princ host/testunix.ABC.123.com@123.COM -mapuser testunix -pass password -kvno 3 -out C:\some\folder\testunix.keytab

That's the keytab I merged with krb5.keytab. It appears, from the IBM doc, that ptype is missing. I don't know that they ran the ktpass.exe within the 123.com domain, but I can verify this.

Keep it simple, just follow the IBM doc, make sure you are following the proper syntax. Since you are just configuring Kerberos.

My Kerberos configuration was integrated with LDAP, it was so complex setup.

Just unconfigure and follow IBM steps.

Will do. I'm trying to arrange some time with the AD admin, because I'd like to create a new keytab and everything. Basically walk through the entire doc from a fresh perspective, because I'm tired of beating my head against a wall here

I know how it feel like!

Also, look at the system logs, what error it is throwing.

Code:

/etc/syslog.conf, is the file to find out the location of log files.

Open a new terminal and run

Code:

tail -f <log file>

to view live logs.


Let me know what you finds out.