scp -r ssh cx refused

Fraser Campbell fraser-eicrhRFjby5dCsDujFhwbypxlwaOVQ5f at public.gmane.org
Fri Jul 30 02:15:00 UTC 2004


On July 29, 2004 09:48 pm, Chris Aitken wrote:

> >The most obvious answer I can think of is that sshd is not running on
> >192.168.0.3.
>
> I see in the GUI 'Service Configuration' sshd is not even listed. Same
> in /usr/sbin/ntsysv

GUI tools suck compared to what you can do on the command line.  Forget the 
gui, if you depend on guis to tell yourself about the system you will always 
be struggling and you'll never *really* understand what's going on.

Is ssh running (ps auxw | grep sshd)?  Is something listening on port 22 
(netstat -ntl | grep :22)?  Is that something on listening on port 22 really 
your sshd process (look at options to netstat for showing you the programs 
that are listening)?

Is sshd installed, use your package management tools to show you that (rpm, 
dpkg, etc.), use locate, etc.

If sshd is listening on port 22, is it listening on 0.0.0.0 (good) or 
192.168.0.3 (also fine) or on some other address only (bad).

If it is listening but you can't connect then what about firewall rules?  Did 
you install firewall rules or activate a firewall script somewhere, did you 
allow incoming ssh connections?

What does /etc/hosts.allow and /etc/hosts.deny say?  Look at the man pages for 
those files if you don't understand.

Presuming that you do have ssh running also check the logfiles (Alex 
mentioned /var/log/messages, there may be others that are relevant).  Do an 
"ls -lrt" in /var/log to see what files are being appended to as you attempt 
connections, "tail -f" those files to see what errors or debugging info is 
being placed there for you benefit.

There's a lot of great material out there for learning what makes a Linux 
system tick.  You cannot learn from a GUI and manuals from SuSe, Mandrake, 
Redhat, et al are mostly useless crap focused on the GUI, package management 
and system installation.  Check out the Linux System Administrators Guide 
(http://www.tldp.org/LDP/sag/html/index.html) and the  Linux Network 
Administrator's Guide (http://www.tldp.org/LDP/nag2/index.html) they're both 
excellent and just as relevant today as when they were first published over 
10 years ago.  There are probably many other good LDP guides but the above 
two are the two that got me started and they were worth every penny of the 
$60 they cost me to print long ago.

-- 
Fraser Campbell <fraser-Txk5XLRqZ6CsTnJN9+BGXg at public.gmane.org>                 http://www.wehave.net/
Georgetown, Ontario, Canada                               Debian GNU/Linux
--
The Toronto Linux Users Group.      Meetings: http://tlug.ss.org
TLUG requests: Linux topics, No HTML, wrap text below 80 columns
How to UNSUBSCRIBE: http://tlug.ss.org/subscribe.shtml





More information about the Legacy mailing list