ssh-connect is very slow

[Heidl Robert]

Hello all,

I have installed ssh 3.0.2p1 on my HP-UX (11.00) N-Class-Server.
When I connect from this Server to an other ssh-Server it takes a long time to connect (> 50 sec.).
When I use the -v option I can see that the delay is in this step: debug1: Reading configuration data /opt/openssh2/etc/ssh_config.
The connect from an other Client to my HP-UX N-Class-Server is fast.

Thanks for help

Robert

[Steve Steel]

Hi


Sounds like

http://forums1-qa2.mayfield.hp.com/cm/QuestionAnswer/1,,0x5ac879bffde7d4118fef0090279cd0f9,00.html

Please read it


Steve Steel

[Steven Sim Kok Leong]

Hi,

It is probably due to reverse dns resolution. Check your reverse name resolution on the destination server. Perform an nslookup test:

# nslookup ip_address_of_ssh_client

Hope this helps. Regards.

Steven Sim Kok Leong

[Heidl Robert]

Hi Steve,
the link is not achievable.
Robert

[Heidl Robert]

Hi Steven,
the nslookup works fine.
Robert

[Steven Sim Kok Leong]

Hi,

From your client that you ssh from, what are the permissions on /opt/openssh2/etc/ssh_config ie.

# ll /opt/openssh2/etc/ssh_config

Can you show us your ssh_config?

# cat /opt/openssh2/etc/ssh_config

Hope this helps. Regards.

Steven Sim Kok Leong

[Heidl Robert]

Hi Steven,

ll ssh_config
-rw-r--r-- 1 root sys 1051 Feb 7 08:50 ssh_config
[db:root:/dev/pts/tc] /opt/openssh2/etc #
more ssh_config
# $OpenBSD: ssh_config,v 1.10 2001/04/03 21:19:38 todd Exp $

# This is ssh client systemwide configuration file. See ssh(1) for more
# information. This file provides defaults for users, and the values can
# be changed in per-user configuration files or on the command line.

# Configuration data is parsed as follows:
# 1. command line options
# 2. user-specific file
# 3. system-wide file
# Any configuration value is only changed the first time it is set.
# Thus, host-specific definitions should be at the beginning of the
# configuration file, and defaults at the end.

# Site-wide defaults for various options

# Host *
# ForwardAgent no
# ForwardX11 no
# RhostsAuthentication no
# RhostsRSAAuthentication yes
# RSAAuthentication yes
# PasswordAuthentication yes
# FallBackToRsh no
# UseRsh no
# BatchMode no
# CheckHostIP yes
# StrictHostKeyChecking yes
# IdentityFile ~/.ssh/identity
# IdentityFile ~/.ssh/id_dsa
# IdentityFile ~/.ssh/id_rsa
# Port 22
# Protocol 2,1
# Cipher blowfish
# EscapeChar ~

Robert

[Michael Tully]

Hi,

Is this server in a 'DMZ'?

If so you will experience some delays depending on the bandiwidth.

Michael

[Steven Sim Kok Leong]

Hi,

Can you nslookup your server from your client?

Try setting CheckHostIP to no in your ssh_config.

# CheckHostIP yes
CheckHostIP no

Hope this helps. Regards.

Steven Sim Kok Leong

[Heidl Robert]

Hi Michael,
no, the server is not in a DMZ.
Robert

[Heidl Robert]

Hi,
the nslookup works fine.
It also does not work withe the optin "CheckHostIP no" in my ssh_config.
Robert

[Antonio Trevino]

Robert,

We currently have Secure Shell A.03.10.002 and we had the same problem. We pounded out the "df" and #df -i" in the /opt/ssh/etc/ssh_prng_cmds file. We noticed there were alot of df processes when we ran ssh.

Hope this helps,

Tony T.

[Antonio Trevino]

Robert,

We currently have Secure Shell A.03.10.002 and we had the same problem. We pounded out the "df" and "df -i" in the /opt/ssh/etc/ssh_prng_cmds file. We noticed there were alot of df processes when we ran ssh.

Hope this helps,

Tony T.