12-22-2008
There are a few things which can cause this, all of which have the same initial response delay when connecting.
1. DNS (on the system you are connecting to) as already mentioned, use of the ipaddress does not preclude this possibility, because if UseDns is set the server will attempt to lookup the client before allowing the connection.
2. Netmasks. If the netmask is incorrect on the server or client it will take some time to figure out the correct routing.
3. Network autonegotiation issue, if one or other party ends up half-duplex you will see similar problems.
10 More Discussions You Might Find Interesting
1. BSD
just as the title says.
thanks.
#General Rule Sets
/sbin/ipfw add 0300 check-state
/sbin/ipfw add 0301 deny tcp from any to any in established
/sbin/ipfw add 0302 pass tcp from any to any out setup keep-state
/sbin/ipfw add 0303 pass udp from any to any out
#SSH FTP
/sbin/ipfw add 0400... (11 Replies)
Discussion started by: dwildgoose
11 Replies
2. Solaris
When I ssh to my box, an Ultra 5. I get prompted for password immediately. I enter it and have to wait sometimes a full minute for it to prompt for a password.
The same thing happens when i try to ftp to the box, it will say connected, but it takes forever to prompt for password, and... (2 Replies)
Discussion started by: BG_JrAdmin
2 Replies
3. UNIX for Dummies Questions & Answers
Hi again guys,
Earlier today, just all of a sudden, all SSH and FTP connections to my internal Linux box just slowed down to a crawl. After the connection/authentication though, everything was back to normal speed. Until you have to connect again. A box reboot didnt work either.
Now, from... (1 Reply)
Discussion started by: Aeros
1 Replies
4. Solaris
Hi Guys and Girls, I know this is a common question but I've searched and we've tried the suggestions without luck. When I log into the box via SSH from a windows machine I get a 1 min 20 sec delay. If we add my IP address and machine name to /etc/hosts then I get an instant login. I would be happy... (12 Replies)
Discussion started by: MikeKulls
12 Replies
5. Shell Programming and Scripting
I have some sample code that's supposed to ssh to another machine using Net::SSH::Perl, execute a command, and print
the output of that command. It's very basic, and it works. However, I noticed that upon logging in:
$ssh->login('username','password');
It takes roughly 10-13 seconds to... (2 Replies)
Discussion started by: mrwatkin
2 Replies
6. Solaris
I have Solaris-10 server which was patched by patch cluster last weekend. After patching, it connects slow with other server. Meaning, when I do -
ssh server2
OR
ssh wluser2@server2
OR
ssh root@server2
It waits for 9-10 seconds and then prompt for password, while it used to be instant... (2 Replies)
Discussion started by: solaris_1977
2 Replies
7. Solaris
Hi, I have the following issue, when I tried to login to an Openindiana remote server through ssh It takes to long to ask me for the password. So i tried -v and I realize that sshd hangs here " debug1: SSH2_MSG_SERVICE_ACCEPT received " for at least 2 minutes. Then I can log in and everything is... (2 Replies)
Discussion started by: piukeman
2 Replies
8. HP-UX
Hi experts,
We are getting slow ssh session connections at HP-UX 11.31 servers.
We have set the parameters that maybe will affect , and commented at other theads at config file sshd_config :
UseDNS no
X11Forwarding yes
X11DisplayOffset 10
X11UseLocalhost no
GSSAPIAuthentication no.
... (7 Replies)
Discussion started by: SapBasisSystem
7 Replies
9. SuSE
We are having an issue with slow password prompts via SSH login on all of our SLES 11.2 boxes. The output from a ssh -v login attempt shows a delay here:
debug1: SSH2_MSG_SERVICE_ACCEPT receivedThis issue only happens on the first logon of the day; subsequent logons are normal. Adding the client's... (8 Replies)
Discussion started by: j_aix
8 Replies
10. Solaris
ssh is slow on solaris zone , and is getting stuck at the following place.
debug2: callback done
debug2: channel 0: open confirm rwindow 0 rmax 32768
debug3: Wrote 664 bytes for a total of 3325
Below is the ssh version being used: Sun_SSH_1.1.6, SSH protocols 1.5/2.0, OpenSSL 0x0090704f
... (10 Replies)
Discussion started by: skamal4u
10 Replies
rshd(8c) rshd(8c)
Name
rshd - remote shell server
Syntax
/etc/rshd
Description
The command is the server for the routine and, consequently, for the program. The server provides remote execution facilities with authen-
tication based on privileged port numbers.
The is invoked by when it receives a connection on the port indicated in the cmd service specification. When a service request is
received, the following protocol is initiated:
1) The server checks the client's source port. If the port is not in the range 0-1023, the server aborts the connection.
2) The server reads characters from the socket up to a null (` ') byte. The resultant string is interpreted as an ASCII number, base
10.
3) If the number received in step 1 is non-zero, it is interpreted as the port number of a secondary stream to be used for the stderr.
A second connection is then created to the specified port on the client's machine. The source port of this second connection is
also in the range 0-1023.
4) The server checks the client's source address. If the address is associated with a host for which no corresponding entry exists in
the host name data base the server aborts the connection. For further information, see
5) A null terminated user name of at most 16 characters is retrieved on the initial socket. This user name is interpreted as a user
identity to use on the server's machine.
6) A null terminated user name of at most 16 characters is retrieved on the initial socket. This user name is interpreted as the user
identity on the client's machine.
7) A null terminated command passed to a shell is retrieved on the initial socket. The length of the command is limited by the upper
bound on the size of the system's argument list.
8) The command validates the user according to the following steps. The remote user name is looked up in the password file and a is
performed to the user's home directory. If either the lookup or fail, the connection is terminated. If the user is not the supe-
ruser, (user id 0), the file or is consulted for a list of hosts considered equivalent. If the client's host name is in this file,
the authentication is considered successful. If the lookup fails, or the user is the superuser, the file in the home directory of
the remote user, is checked for the machine name and identity of the user on the client's machine. If the lookup fails, the connec-
tion is terminated.
9) A null byte is returned on the connection associated with the stderr and the command line is passed to the normal login shell of the
user. The shell inherits the network connections established by
Diagnostics
All diagnostic messages are returned on the connection associated with the stderr, after which any network connections are closed. An
error is indicated by a leading byte with a value of 1 (0 is returned in step 9 above upon successful completion of all the steps prior to
the command execution).
locuser too long
The name of the user on the client's machine is longer than 16 characters.
remuser too long
The name of the user on the remote machine is longer than 16 characters.
command too long
The command line passed exceeds the size of the argument list (as configured into the system).
Hostname for your address unknown.
No entry in the host name database existed for the client's machine.
Login incorrect.
No password file entry for the user name existed.
No remote directory.
The command to the home directory failed.
Permission denied.
The authentication procedure described above failed.
Can't make pipe.
The pipe needed for the stderr was not created.
Try again.
A fork by the server failed.
/bin/sh: ...
The user's login shell could not be started.
Restrictions
The authentication procedure used here assumes the integrity of each client machine and the connecting medium. This is insecure, but is
useful in an open environment.
See Also
rsh(1c), rcmd(3x), services(5), inetd(8c)
rshd(8c)