Hi,
Thanks for your help! It turned out that because both the Kerberos server and client are on the same machine, the packets that the server sends out gets looped back -- so they don't travel all the way down the IP stack. In order for our client application to work, the packet needs to be processed by certain parts of the driver, so we're working on that problem now... Again, thanks for your time and help!
Monica
Sam Hartman <[EMAIL PROTECTED]>wrote:
You almost certainly have some sort of routing or IP misconfiguration,
host name resolution problem or something like that.
In future, please do not remove details like IP addresses etc
from your logs especially in situations where they might actually be
useful to someone debugging your problem. If your identity or
security requirements are such that you cannot even post your address
or realm name, then perhaps you should hire someone and get them to
sign an NDA rather than posting to a news group.
I suspect that especially on Linux somehow localhost (127.0.0.1) is
somehow involved either in the KDC request or the KDC response. This
could be because resolving your kdc yields 127.0.0.1 on the KDC
itself, because of some routing rules, or because of something I'm not
thinking of.
________________________________________________
Kerbero! ! s mailing list [EMAIL PROTECTED]
http://mailman.mit.edu/mailman/listinfo/kerberos
Do You Yahoo!?
Yahoo! Health - Feel better, live better
