Cannot resolve network address for KDC in requested (error 220)

[Edward Murrell]

This is a really fast response, since I'm about to disappear out the
door for Xmas.

Probably cause.
a) krb5.conf doesn't have kdc address
b) DNS doesn't have kdc address
c) address specified for kdc is internal address (eg kdc.local.lan.only)
d) address specified for kdc no longer exists for some strange reason
(broken DNS server?)
e) The routers are screwing up the DNS.  Try manually setting the DNS
servers manually to your ISPs servers.

Cheers
Edward


ttenhave at mail.med.upenn.edu wrote:
> Hello,
>
> I'm a new user of Kerberos 5 by way of Leash
> at the University of Pennsylvania in order
> to access their mail server with Thunderbird.
> I apologize if this issue has already been
> addressed on this listserv. If so, if someone
> can point me to the corresponding thread, that would
> be great.
>
> I have Leash/Kerberos on my laptop and it works
> fine at Penn and also in other wireless environments
> such as a local coffee shop. However, when I'm at
> home, Kerberos 5 cannot access the Penn server for some
> reason (the error message is below). I have a 
> Action Tec DSL modem/router using
> Verizon DSL. My neighbor has a similar setup but 
> a different brand DSL modem/router. My wireless
> does not work with Kerberos 5 on either DSL modem.
>
> Here is the error message I get at home with the
> same laptop that works fine with Kerberos 5 
> other wireless environments: 
>
> "Ticket initialization failed"
>
> "Keberos 5: Cannot resolve network address for KDC in requested
> realm (error 220)"
>
>
> Tom Tenhave
> University of Pennsylvania
>
>