Hello all,

I just installed slackware 9.1 and did all of the updates. I can't seem to ssh into it though- i get
a connection time out message. i've tried stopping and restarting sshd, with no luck. I am able to access the internet np and I can ssh into other servers, but have no access to mine. Can anyone give me a suggestion on how to fix this, or where to begin to look?

thank,

plan9 (as in the movie, not the os!)

Well what's your current network setup? Where are you trying to SSH FROM? Is it from a machine that is on your LAN or off site somewhere? Routers? Firewalls? Once we get a little more info, might can help further. Also, check made sure sshd is running. You could do a netstat and see if port 22 is listening. That may be your problem too. Let us know....

just to furher what AUSanders79 was saying, home networking can be a nightmare due to firewalls getting in the way. Check if ssh is working locally by:

$ netstat -l

you should see:

tcp 0 0 *:ssh *:* LISTEN

then ssh from the machine to itself

$ ssh localhost

if both of the above are working fine, then the problem is between the two machines.

Steve

Edit: You might want to read this great piece by shilo about getting ssh to work, it may help :)

Hi there,

I can ssh to localhost but, can't ssh to it from any machine on the network.

Tried >> netstat -l and had

tcp 0 0 *.ssh *:* LISTEN

...

ANY HELP????????????

Have you killed any firewalls at both ends? Maybe you've blocked some local network traffic. Disconnect from the internet if you don't feel save (but obviously don't disconnect from the network - I assume you're on a router of some sort), then retry with all firewalls down.

How about port forwarding 22 and getting a friend to ssh to your box?

Steve

you may need to add the other machines to your /etc/hosts.allow its probably inetd getting in the way.

What is the output of:

iptables -L

?

Thanks to all the responses, it was in fact a firewall issue.

Glad you got it resolved, at which end was the firwewall? On the server or on your main machine?

Steve

It was on my end, my rc.firewall script was blocking all incomming connections, where i thought that
it was allowing incomming ssh ones.

9

well I kinda have the same question

I'm trying to set up my ssh, I followed the steps from silho and everything works on LAN, but it doesn't if anyone from outside my local network tries to connect ...

I thought it was the firewall in my router but port 22 is forwarded for that PC so this should work fine

same as port 80
I'm running the noip software so when I let people connect to username.no-ip.org they DO have access to any website in my htdocs dir
but this doesn't work with ssh anymore, cuz it worked before I reinstalled slack (on 10.0 now ;-) )

I've taken a look at this file, and it's empty, some comment here and there but nothing that's not commented...

any help would be appreciated ;-)

first off go to /etc/syslog.conf and add this line

*.* /dev/tty6

then at the command prompt type this command as root
/etc/rc.d/rc.syslog restart

now hit <CTRL>+<F6> now you can watch all your logs on tty6 when you log in it with ssh or ftp or http or everything this will tell you what is happening. If its inet.d getting in the way you will see some logs about tcp wrappers and a rejected login. If its iptables just look for iptable logs going to port 22.

ok, this lot is not cool ...

@ local when I have logged in: it say accepted password for blablabla

when I let a user log in from the internet, it says thesame thing BUT putty always gives them: programm causes internal error
every time, with each and every one of them ...
stil nowherez

I do see that it shows:

Accepted password for "username" from "ip" port "different from 22" ssh2

well ssh2 is a setting in my (hardware) router but I don't understand why it shows a different port then 22?

I edited my hosts.allow file to accept
ALL: ALL

didn't do anything

editing it like this:
22: ALL

gives me the following error when somebody tries to connect

I think the prob come from your router config, it is normal that client use other port than 22 from their side, but will connect on 22 in your side (same behaviour with ftp, http...)

Have you a ' nat list ' command or similar in your router to see if output connection request on port 22 is forwarded to your machine ?