[33039] in Kerberos

home help back first fref pref prev next nref lref last post

Re: Kerberos5 + SSH Questions

daemon@ATHENA.MIT.EDU (Lee Eric)
Tue Jan 4 07:34:10 2011

MIME-Version: 1.0
In-Reply-To: <20110104121743.GA4219@talktalkplc.com>
Date: Tue, 4 Jan 2011 20:34:05 +0800
Message-ID: <AANLkTinQ67y7VOwGNh_5NANBQkYnP9-Z3RDjJTLTGG6g@mail.gmail.com>
From: Lee Eric <openlinuxsource@gmail.com>
To: Brian Candler <B.Candler@pobox.com>
Cc: kerberos@mit.edu
Content-Type: text/plain; charset="iso-8859-1"
Errors-To: kerberos-bounces@mit.edu
Content-Transfer-Encoding: 8bit

Thanks, Brian. It looks like it was a host name problem. And I have
correct that. It works well.

Regards,

Eric

On Tue, Jan 4, 2011 at 8:17 PM, Brian Candler <B.Candler@pobox.com> wrote:
> On Tue, Jan 04, 2011 at 07:31:37PM +0800, Lee Eric wrote:
>> So how do I know what client/server gets the idea of the server host
>> name? It looks like reverse map works well and they can get the same
>> IP/Address.
>
> On the server, type "hostname". If it returns anything other than
> ns.herdingcat.internal, correct it. Depending on your O/S this may be
> something like
>
> # echo "ns.herdingcat.internal" >/etc/hostname
> # hostname ns.herdingcat.internal
>
> On both the client and server, check that
>
> $ dig ns.herdingcat.internal
> $ dig -x 172.16.14.1
>
> give the right results (names maps to IP, and IP maps to name).
>
> Check /etc/hosts on both machines. Either there should be no entry for this
> box, or if there is one, the FQDN should be the first listed name.
>
> 172.16.14.1 ns.herdingcat.internal     # OK
> 172.16.14.1 ns.herdingcat.internal ns  # OK
> 172.16.14.1 ns ns.herdingcat.internal  # WRONG
>
> Regards,
>
> Brian.
>

________________________________________________
Kerberos mailing list           Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos


home help back first fref pref prev next nref lref last post