I have an application that uses K5 authentication. Specifically, we are using CorporateTime with K5. For the most part, the authentication works the way I would expect and there are no problems. However, I have a few users who are behind personal firewalls or routers that are using network address translation (NAT). In that situation, they are able to get a K5 ticket using Leash32 but then we see an authentication failure when they start CorporateTime.
Is there a way to get the K5 authentication to work when using NAT? David Resler, Ohio University
msg02807/pgp00000.pgp
Description: PGP signature
