SSH via Putty not working after ip change

[divided]

Running Fedora 5

We changed ip's the other day and now ssh is not working. SSH/Putty was working fine before the ip change. Everything else is working fine on the machine. The sshd_config file has not been touched at all since I've been working on the machine.

var/log/messages shows this:

bind to port 22 on 0.0.0.0 failed address already in use

netstat -an shows that tcp is listening on 0.0.0.0:22 with no port conflicts.

I google searched the error and I couldn't find anything helpful.

We haven't changed anything except ip's on the box. What is the issue? Thanks in advance.

[scathefire]

Are you using the ListenAddress option in your ssh config? If so, try commenting it out and restarting the service.

[divided]

Are you using the ListenAddress option in your ssh config? If so, try commenting it out and restarting the service.

Thanks for the reply. Two ListenAddress lines in sshd_config are commented-out. Sshd_config shows this:

#ListenAddress 0.0.0.0
#ListenAddress ::

[scathefire]

so if you stop ssh service and do a netstat -pantu, does it show anything still running on port 22? if it does, then take the PID from there and use kill. then try starting the ssh service.

[divided]

so if you stop ssh service and do a netstat -pantu, does it show anything still running on port 22? if it does, then take the PID from there and use kill. then try starting the ssh service.

Nothing is running on port 22 after stopping ssh.

[divided]

I have since tried other programs to remote into the box (mysql query browser, ftp, webmin) and none of them work. Looks like it's an issue with the box accepting connections.

[scathefire]

is this a internal to internal connection? or an external to internal connection? it sounds weird that the whole connection interface would just be hosed like that. Are all services reporting binding issues?

[divided]

is this a internal to internal connection? or an external to internal connection? it sounds weird that the whole connection interface would just be hosed like that. Are all services reporting binding issues?

This would be an internal connection to an external connection. Only sshd is reporting binding issues, but we still can't get to mysql on port 3306 for example.

[scathefire]

any chance there would be a NAT table not properly updated on a border router?

[divided]

any chance there would be a NAT table not properly updated on a border router?

Thanks for all your help scathefire. We found the problem. Apparently the box was running a firewall that we didn't know about (shorewall) and in the shorewall config, it defined all of our old ip's. We switched them to the new ones and now everything works fine (and it's faster). We inherited the box and had no clue that it was even running its own firewall (i'm a linux newb).

Thanks for all of your help!