Re: ssh login issue
- From: Chris Petrik <chris@xxxxxxxx>
- Date: Thu, 09 Feb 2006 11:01:58 GMT
On Tue, 05 Apr 2005 20:16:36 +0100, Michael Hopkins
<michael.hopkins@xxxxxxxxxxxxxxxxxxxx> wrote:
On 27/3/05 2:37 am, in article MPG.1cafd85d7bc6367b9896e1@xxxxxxxxxxxxxxxxx,
"Dan Swartzendruber" <dswartz@xxxxxxxxxx> wrote:
In article <BE6BCB52.3665D%michael.hopkins@xxxxxxxxxxxxxxxxxxxx>,
michael.hopkins@xxxxxxxxxxxxxxxxxxxx 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?
TIA
Michael
_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
_/ _/ _/_/_/ Hopkins Research Ltd
_/ _/ _/ _/
_/_/_/_/ _/_/_/ http://www.hopkins-research.com/
_/ _/ _/ _/
_/ _/ _/ _/ 'touch the future'
_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
try taking Rdns off as a lot of problems start by a misconfigured
named not able to rdns domains
.
- Follow-Ups:
- Re: ssh login issue
- From: The Doctor
- Re: ssh login issue
- Prev by Date: NDIS and WPA
- Next by Date: Re: sshd attacks
- Previous by thread: NDIS and WPA
- Next by thread: Re: ssh login issue
- Index(es):
Relevant Pages
|
|