topic Re: sshd bind to port 22 fail in Operating System - Linux

sshd bind to port 22 fail

Tammy Liang — Fri, 15 Dec 2006 16:08:19 GMT

I have a VM running RedHat ES4. I can not start sshd daemon due to port 22 is already used. I checked port 22 is not used before I started sshd daemon. Below is the error message I saw at secure file.
sshd: bind to port 22 on 0.0.0.0 failed: Address already in use.

I can ssh from the VM to itself. But not from other system to this VM. I got error message:
ssh: connect to host 123.122.121.13 port 22: No route to host.

Thanks for any help.

Re: sshd bind to port 22 fail

George Liu_4 — Fri, 15 Dec 2006 16:25:35 GMT

post

netstat -antp|grep 22

Re: sshd bind to port 22 fail

Tammy Liang — Fri, 15 Dec 2006 16:30:45 GMT

tcp 0 0 :::22 ::: * LISTEN 9467/sshd

9467 is PID for sshd

Re: sshd bind to port 22 fail

Ivan Krastev — Fri, 15 Dec 2006 17:52:56 GMT

Actually you have error "No route to host". Check your connection to VM. Try ping, traceroute, arp.

Also check routing table on VM for errors.

regards,
ivan

Re: sshd bind to port 22 fail

Matti_Kurkela — Wed, 20 Dec 2006 15:26:20 GMT

The ":::22" in the netstat output is IPv6-style for "listening on port 22 on all interfaces."

You have an IPv6-capable sshd already running (process ID 9467). The single process may be able to handle both IPv4 and IPv6 connections, but it will probably display even the IPv4 addresses in IPv6 style. This may be slightly confusing, but harmless.

When you ssh from the VM to itself, you may be actually using IPv6 locally. This might explain why the localhost connection works.

There might be something wrong with your IPv4 settings, which would explain why you cannot connect to the VM from other systems.

From the information you've provided so far I cannot determine what the problem might be.