Re: ssh login issue
From: Thomas Koellmann (koellmann_at_gmx.net)
Date: 04/09/05
- Next message: Torfinn Ingolfsen: "Re: Adding a disk"
- Previous message: Rudolf Polzer: "Re: Audio & SBLive"
- In reply to: Michael Hopkins: "Re: ssh login issue"
- Next in thread: Justins local account: "Re: ssh login issue"
- Reply:(deleted message) Justins local account: "Re: ssh login issue"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sat, 09 Apr 2005 11:54:29 +0200
Michael Hopkins <michael.hopkins@hopkins-research.com> writes:
> On 27/3/05 2:37 am, in article MPG.1cafd85d7bc6367b9896e1@news.giganews.com,
> "Dan Swartzendruber" <dswartz@druber.com> wrote:
>
>> In article <BE6BCB52.3665D%michael.hopkins@hopkins-research.com>,
>> michael.hopkins@hopkins-research.com says...
>>>
>>>
>>> Hi all
>>>
>>> Anyone know why this is happening when I remotely ssh in to a 5.3p amd64
>>> server called Athlon?
>>>
>>> reverse mapping checking getaddrinfo for athlon failed - POSSIBLE BREAKIN
>>> ATTEMPT!
>>>
>>> It lets me in fine after I supply the password.
>>
>> I believe this is a DNS issue. It's taking the IP address you're
>> connecting from and trying to reverse back to the name and then
>> verifying the forward address. I think this message means that the
>> second step is failing. What I mean is: let's say you're connecting
>> from 10.1.2.3. It does a reverse lookup and comes up with xxx.foo.com.
>> It then does a forward lookup on xxx.foo.com to make sure the IP address
>> matches, but it doesn't (either different or no forward name.) It's
>> basically harmless in your case, I think.
>
> People have suggested a mis-configured named setup, so now that is switched
> off and all hostnames are stored in /etc/hosts. The local network is small
> (3 machines) and all external access is via the combined network router/ADSL
> modem which links everything together. The IP for this router is the only
> entry in /etc/resolv.conf at each end.
>
> I'm not sure if the ssh setup at one or both ends is to blame or if it's
> somewhere in the network setup. Does anyone have any suggestions on where
> to look for the problem or diagnostic tools/logs that will help point to the
> solution?
Just make sure that when
thk@starbuck:~$ nslookup athlon
gives
Address: 192.168.250.250
the reverse lookup agrees to that:
thk@starbuck:~$ nslookup 192.168.250.250
250.250.168.192.in-addr.arpa name = athlon
Mit schönem Gruß
- Thomas
-- I had a funny feeling as I saw the house disappear, as though I had written a poem and it was very good and I had lost it and would never remember it again. - Raymond Chandler, The High Window /* PGP key auf Wunsch per e-mail || PGP key sent on request */
- Next message: Torfinn Ingolfsen: "Re: Adding a disk"
- Previous message: Rudolf Polzer: "Re: Audio & SBLive"
- In reply to: Michael Hopkins: "Re: ssh login issue"
- Next in thread: Justins local account: "Re: ssh login issue"
- Reply:(deleted message) Justins local account: "Re: ssh login issue"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|