[SOLVED] Port 22: Connection refused!?

[zbormanchino]

Hey all,

Friday night I was working on some networking stuff between my two Fedora 14 boxes. I have my laptop and my desktop. on both machines I have "system-config-firewall 1.2.27" and "iptables" (i believe both come standard on F14?) I kept getting the same message as seen below before realizing perhaps I should check my firewall!

I added a rule for incoming and outgoing traffic on port 22 and was able to get in with no problems at all!
however today I can't ssh into anything... I can't use "Remote Desktop Viewer 2.31.4" to vnc into the machine anymore. I can't remember the exact error message at this time, it's something close to "Connection was terminated" or "Unable to connect" I can update this message later.

last night I foolishly uninstalled the system-config-firewall and then uninstalled iptables to see if it was a simple firewall issue.... totally hosed my system <insert smiley!>

After reinstalling and realizing I didn't backup my documents <insert smiley!...again...> I started reinstalling all of my applications. I'm still unable to use ssh and I've tried to ssh my own computer.

Is this possible?

# ssh 127.0.0.1
ssh: connect to host 127.0.0.1 port 22: Connection refused

[glennzo]

Is ssh running?

PHP Code:

service ssh status 


[zbormanchino]

[root@fedora micah]# service ssh status
ssh: unrecognized service


interesting... let me search yum for ssh

[kurtdriver]

Type this to start it.

service sshd start

[zbormanchino]

[root@fedora micah]# yum install openssh.x86_64
Loaded plugins: langpacks, presto, refresh-packagekit
Adding en_US to language list
Setting up Install Process
Package openssh-5.5p1-24.fc14.2.x86_64 already installed and latest version
Nothing to do
[root@fedora micah]# yum install openssh-clients.x86_64
Loaded plugins: langpacks, presto, refresh-packagekit
Adding en_US to language list
Setting up Install Process
Package openssh-clients-5.5p1-24.fc14.2.x86_64 already installed and latest version
Nothing to do



Interesting as well... Thoughts?

---------- Post added at 09:44 AM ---------- Previous post was at 09:42 AM ----------

[root@fedora micah]# service sshd status
openssh-daemon is stopped
[root@fedora micah]# service sshd start
Generating SSH2 RSA host key: [ OK ]
Generating SSH1 RSA host key: [ OK ]
Generating SSH2 DSA host key: [ OK ]
Starting sshd: [ OK ]

You sir are a genius!! What do I need to do in order have sshd start when the computer does?

---------- Post added at 09:50 AM ---------- Previous post was at 09:44 AM ----------

Disregard the last question. I'm going to mark this post as solved and go research my second question! Thanks again Kurt

[glennzo]

Crap! My bad! Should have been service sshd status.

PHP Code:

[glenn@server ~>$ service sshd status
openssh-daemon (pid  1493) is running... 


Set the daemon to on and then start it.

PHP Code:

chkconfig sshd on
service sshd start 


It will then start automatically at every boot.

[zbormanchino]

service sshd status
openssh-daemon (pid 1503) is running...


perfect thank you!

[andres29]

to the administrators, please help me about the port 22 refused/timeout for wan connection, but for lan it is working... i already closed my firewall, but still having port 22 refused/timeout problem.. is it possible that the problem is come from the internet service provider?

please help me.. thanks and god bless

[mehdi601f]

rm -rf /root/.ssh/*

service sshd stop
service sshd start

[flyingfsck]

First of all, you don't really need a firewall on a Linux machine, so you can safely disable it till you got things under control.

You say it works on the LAN. Therefore SSH is OK. You just have a firewall problem so turn it off to prove the point.

[zogthegreat]

hi mehdi601f,

To open port 22, open a terminal, switch to root and run the following command:

iptables -A INPUT -p tcp -m tcp --syn --dport 22 -j ACCEPT

Hit enter end exit your shell

Two good sources for configuring and managing iptables are:

http://wiki.centos.org/HowTos/Network/IPTables

http://www.linuxhomenetworking.com/w...s#.URLOImeym2g

Although I am sure that there is some sort of GUI to manage iptables, it really will help you in the long term if you learn how to manage and monitor your firewall from the command line.

Good luck

zog

---------- Post added at 05:04 PM ---------- Previous post was at 04:46 PM ----------

btw:

I forgot to mention, if you want to keep this port open for future use, do the following to make the changes permanent:

iptables-save > /etc/sysconfig/iptables

systemctl restart iptables.service

Just remember, always start your security at "Paranoid" and RAISE your security as needed. I am not trying to be funny. Leaving ports open that do not need to be open is a bad security practice to get into.