Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 4 Sep 2001 11:16:23 +1200
From:      "Juha Saarinen" <juha@saarinen.org>
To:        "'Conrado Vardanega'" <cvspam@ig.com.br>, "'Chris BeHanna'" <behanna@zbzoom.net>
Cc:        <freebsd-stable@freebsd.org>
Subject:   RE: Access disallowed through ssh
Message-ID:  <01b101c134ce$7294db70$0a01a8c0@den2>
In-Reply-To: <NDBBLGPICDCECKDGFCGFAECPCKAA.cvspam@ig.com.br>

next in thread | previous in thread | raw e-mail | index | archive | help
Do 

	ssh -v

to get the debugging output. Might help you discover what's going on --
could be a protocol mismatch, for instance.

-- 

Juha 

:: -----Original Message-----
:: From: owner-freebsd-stable@FreeBSD.ORG 
:: [mailto:owner-freebsd-stable@FreeBSD.ORG] On Behalf Of 
:: Conrado Vardanega
:: Sent: Tuesday, 4 September 2001 11:09
:: To: Chris BeHanna
:: Cc: freebsd-stable@freebsd.org
:: Subject: Re: Access disallowed through ssh
:: 
:: 
:: Ok, there is more information about the problem:
:: 
::   -- its NOT the hosts.allow, its "ALL : ALL : allow" and I 
:: don't even have
:: a PARANOID line there.
:: 
::   -- its NOT firewall matter, I've no firewall rules at this 
:: machine and
:: people can "telnet 200.193.xx.xx 22" and get tcp sessions 
:: open. Therefore
:: the Network Layer is ok.
:: 
::   --  its NOT reverse/unmatching dns entry. Both, public and private
:: addresses, are named and they're all matching correctly.
:: 
:: Thanks!
:: 
:: Conrado
:: 


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?01b101c134ce$7294db70$0a01a8c0>