[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: KDC not found even after connection was made

Thank you very much for the suggestions. Unfortunately I already have all
these, too. I didn't know it is relevant to my problem so I didn't notice
it - sorry.

I see the problem somwhere in the communication protocol, but not sure
what exactlz it means: kdc logs the connection was made but nothing more.
Client claims no kdc was found. So probably a wrong diagnostic on the
client side and poor log entries on the server side ? This could sound
curious, but I have no other explanation for now and do not know how to
resolve this. It is very important to me to migrate from krb4 network to
something more supported bz other applications. Somebody told me heimdail
is far better than MIT-krb5, so I am trying to get the better one to work


  David Komanek

On Mon, 13 Oct 2003, Johan Danielsson wrote:

> David Komanek <xdavid@lib-eth.natur.cuni.cz> writes:
> > [ktutil]
> >         dns_lookup_realm = false
> >         dns_lookup_kdc = false
> These should go in the [libdefaults] section. With this flag off, it
> still looks for kerberos.realm (but not for SRV records); we should
> probably change this.
> >         kdc = e.f.g.h
> And this should go in [realms]. See krb5.conf(5).
> You might need an "admin_server = host" there also.
> [realms]
>         YOUR.REALM = {
>                 kdc = e.f.g.h
>                 admin_server = e.f.g.h  <-- if this is correct
>         }
> > Could be the problem different architecture (littleendian/bigendian)
> > of both machines?
> No.
> > Or the ssl version used (master - internal functions of heimdal,
> > slave - openssl 0.9.7c) ?
> Not very likely.
> /Johan