Extremelly annoying problem, ssh connections fail with this error: Received disconnect from 140.xxx.xxx.xxx: 2: bind: Permission denied I get this error connecting to a dozen machines or so. SSH connections from other machines (including Win XP, Solaris 9, and RH) all work fine to the same hosts. here is verbose: user@host:~> ssh -v adcbkp15 OpenSSH_3.9p1, OpenSSL 0.9.7e 25 Oct 2004 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to adcbkp15 [140.87.248.144] port 22. debug1: Connection established. debug1: identity file /home/ccarson/.ssh/id_rsa type 1 debug1: identity file /home/ccarson/.ssh/id_dsa type 2 debug1: Remote protocol version 2.0, remote software version OpenSSH_3.8.1p1 debug1: match: OpenSSH_3.8.1p1 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_3.9p1 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client aes128-cbc hmac-md5 none debug1: kex: client->server aes128-cbc hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: Host 'adcbkp15' is known and matches the RSA host key. debug1: Found key in /home/ccarson/.ssh/known_hosts:2 debug1: ssh_rsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,password,keyboard-interactive debug1: Next authentication method: publickey debug1: Offering public key: /home/ccarson/.ssh/id_rsa debug1: Server accepts key: pkalg ssh-rsa blen 149 debug1: read PEM private key done: type RSA debug1: Authentication succeeded (publickey). debug1: channel 0: new [client-session] debug1: Entering interactive session. debug1: Requesting X11 forwarding with authentication spoofing. debug1: Requesting authentication agent forwarding. debug1: Sending environment. debug1: Sending env LANG = en_US.UTF-8 You can seeit accepts my key, but something pukes after that. I tied removing the pub key and using password auth and same thing. Ugh. I dont wanna have to revert back to FC, but this problem is a major show stopper for me. Thanks for any help, CC
Chuck Carson wrote:
Extremelly annoying problem, ssh connections fail with this error: Received disconnect from 140.xxx.xxx.xxx: 2: bind: Permission denied
I get this error connecting to a dozen machines or so.
SSH connections from other machines (including Win XP, Solaris 9, and RH) all work fine to the same hosts.
I use SSH with 9.3 all the time and it works fine. What happens if you reinstall it?
Quoting Chuck Carson <chuck.carson@gmail.com>:
Extremelly annoying problem, ssh connections fail with this error: Received disconnect from 140.xxx.xxx.xxx: 2: bind: Permission denied
Are you running BIND (DNS server)? I am running SSH successfully from 9.3 to SuSE 9.2 and Debian sarge and an unknown distribution Linux systems with no problems. Jeffrey
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Thursday 2005-07-21 at 11:14 -0500, Chuck Carson wrote:
debug1: Entering interactive session. debug1: Requesting X11 forwarding with authentication spoofing. debug1: Requesting authentication agent forwarding. debug1: Sending environment. debug1: Sending env LANG = en_US.UTF-8
You can seeit accepts my key, but something pukes after that. I tied removing the pub key and using password auth and same thing.
But the error doesn't show there.
Ugh. I dont wanna have to revert back to FC, but this problem is a major show stopper for me.
You could try sshing to your own computer (local loop) enabling debugging in the server, and see what shows. Better still, if the server is in another machine. Another idea; you said:
Extremelly annoying problem, ssh connections fail with this error: Received disconnect from 140.xxx.xxx.xxx: 2: bind: Permission denied
"Bind" might be refering to this: | Use the `bind' function to assign an address to a socket. The prototype | for `bind' is in the header file `sys/socket.h'. For examples of use, | see *Note Local Socket Example::, or see *Note Inet Your ssh client may be failing to get a local socket for some reason. More I can not guess. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFC4CYTtTMYHG2NR9URArsaAJwMdzknaoZ59ChPHTdMNvrQ12JqUgCfYdzR KpILRUavHGbdiNb3K2/nisU= =gdRQ -----END PGP SIGNATURE-----
participants (4)
-
Carlos E. R. -
Chuck Carson -
James Knott -
Jeffrey L. Taylor