The behavior is that of a lack of network connectivity. I don't know what the cause of the problem is but I am attempting to help you narrow it down. Is there traffic being exchanged with the kaserver?
If so, are there responses being sent back? If there is no traffic being sent, then the question becomes why not? Andrew Radamis wrote: > But it works with out issue with 1.4.1, with no other changes to the > system. I tried 1.4.2 and had the same issue. As soon as I downgrade > back to 1.4.1 it works again. I can login to the machine as soon as > the login box appears. System authentication is on an NT domain, using > Samba. The Samba PDC and BDC are also the AFS servers, so I don't think > it's a network conductivity issue. > > Andrew > On 12/13/06, *Jeffrey Altman* <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > You privately sent the event log entries. > I see nothing in there that is wrong. > Although I must wonder whether or not the machine > actually has network access at the time it is > failing. > > The error indicates that none of the KdC addresses > that are being contacted are responding. You might > want to monitor traffic with a tcpdump on the server > to see whether in fact you are getting traffic to > the kaservers that you are expecting to see. > > Jeffrey Altman > > >
smime.p7s
Description: S/MIME Cryptographic Signature
