<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On Aug 26, 2011, at 9:18, Steven Crothers wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">Are they logging in locally or via SSH?<br></span></blockquote><div><br></div>Locally. Remote logins via ssh work just fine as the home directory is auto-mounted and ssh can find its keys.</div><div><br></div><div>I think I solved the problem, but am out of the office today to fully test it. It involved setting the default realm and adding some encryption types to the /etc/krb5.conf file. What I still don't understand is what has changed in CentOS 6 that causes a kickstarted system not to be able to authenticate users whereas a CentOS 5 system can. I need to do a few more installs to track down the root cause, and then I'll post an update here.</div><div><br></div><div>Alfred</div><div><br></div></body></html>