...at me, the same problem occured in a freshly installed linux. The solution was to configure the /etc/hosts.deny because it had by default an
ALL: PARANOID
line in it which prevented me to log in from my notebook (which actually was not having a reverse lookup-enabled domain name - ip address pair).

Anyway, this was the simple problem with it.

For a workaround, when you can't get into your system from a previous DHCP enabled machine try logging onto another server having a fixed IP-DNS pair and try logging onto your server from there possible with much higher success ratio and you can fine tune your /etc/hosts.deny file from there...

BBK

I solved this problem. This occured because of changing permissions in /var/ folder.This may be one reseason for you.

so now change permissions to
chmod -R 755 /var/

Now i got resolved this problem.
-Thanks

sorry wrong posting.

Be careful the /var can has /var/www or other folders that probably will have other permissions.
For get ssh working in my case I just did:
chmod 775 /var/run/sshd
chown root:root /var/run/sshd
/etc/init.d/ssh restart

In my Debian Etch.

Some of my RHEL servers tends to respond very slow as we connect through ssh and take longer time to give login prompt. When I get authenticated and log in, it works as usual. Is there any reason for this ?

Hi!

I had the same problem, then I foun that my /etc/inetd.conf had the following line:

ssh stream tcp nowait root /usr/sbin/tcpd /usr/bin/ssh

I commented the the line, restarted inetd and then it got ok.

Are you able to login to the server locally using ssh.?

look and see if ALL: PARANOID in /etc/hosts.deny is uncommented.

My configuration had
ALL : PARANOID : deny
in hosts.allow . Removing this line fixed the problem

1)chek the firewall on the client machine

chek this link

http://lists.debian.org/debian-user/.../msg02345.html

If you can log into the server via console. Try editing the /etc/hosts.allow file and adding:

ALL: 10.

or try adding:

ALL: <your subnet>

as the last line in the file.

Hi all:

I am trying to set up an ssh tunnel from my machine (in India) to a server (in US). How do I do it? The problem is: I have to first create a tunnel to Server-1 and then another from Server-1 to Server-2. The point here is: I have to establish a tunnel from my machine to Server-2. Can you please help me establish one?

Hi avijitp.

The reason it takes a long time to get the login prompt is usually that the host cannot resolve the DNS name of the client, so it waits until to reslove attempt times out and then proceeds. Solve this by making sure the client is resolvable by the DNS that the server connects to, or just manually add the client to the /etc/hosts file - it usually fixes things.

Guess the sshd tryes to resolve the name of the clients for logging purposes or something...

- Karsten

I too had that idea and to test that I have also added the corresponding entry in the /etc/hosts file and it did not help. I tried and verbose option and it waits unusually long at the authorization phase.

THANK YOU. Switching subnets and networks in the office and for days couldn't figure out why certain servers were pingable but just dropping ssh packets.