On Fri, 21 Jul 2000, Steven Boothe wrote:
> Date: Fri, 21 Jul 2000 15:00:24 -0700
> From: Steven Boothe <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: Re: [expert] OpenSSH won't accept connections?
>
> On Fri, 21 Jul 2000, you wrote:
> > > ...
> > ...
> > but in your case, when I ssh to the IP your logs show, it seems to wait
> > for a long time.
>
> That's probably because that IP address is behind a firewall...
>
Nope, I can ssh outta here fine to at least 2 machines not behind
firewalls.
> > I gotta run out for dinner soon, could you run an nmap on your system?
>
> Wow, running nmap was an awsome idea (thanks)! Just look at this output:
> "
your're welcome
> Starting nmap V. 2.30BETA17 by [EMAIL PROTECTED] ( www.insecure.org/nmap/ )
> Interesting ports on (63.196.197.254):
> Port State Service
> 25/tcp open smtp
> 113/tcp open auth
>
> TCP Sequence Prediction: Class=random positive increments
> Difficulty=1562052 (Good luck!)
> Remote operating system guess: Linux 2.1.122 - 2.2.14
>
Maybe sshd isn't running, check by running "ps ax"
> Nmap run completed -- 1 IP address (1 host up) scanned in 0 seconds
> "
> What do you make of that? Nothing's open on port 22??? Yet I have the
> "ListenAdress" variable set to "63.196.197.0", and now I've even set
> hosts.allow to ALL:ALL, and hosts.deny to <null>. Not to mention that
> /etc/rc.d/init.d/sshd status == running...
>
> This is really odd...?
>
Either sshd is not running, or due to some error. Try to look at the sshd
logs, maybe in /var/log/messages. Also, if you can, stop sshd, then run it
on a terminal windows/console. This allows you to interactively see any
errors present, run "sshd -d" to enable debugging to get the logging of
what is happening as the client tries to connect to the daemon. This
should help quite a bit. If none of these seem to work, change your
mandrake security level using msec, "msec 0" I think. But do remember to
change it back later. Another problem I had before was that firewalling
was turned on in linuxconf, and that disabled all outside services, it
essentially locked me out of remote usage of my machine. That may be also
a possible cause. Good luck!
--
Regards,
Ellick Chan
[EMAIL PROTECTED]
Jul 21
