Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

copSSH not working on windows 7 32-bit


  • Please log in to reply
3 replies to this topic

#1 vinsor

vinsor

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:08:54 PM

Posted 04 August 2010 - 02:25 AM

I have three systems with the IP's:
XX.188: Windows 7 32-bit System with copSSH installed
XX.125: Windows 7 64-bit SYstem with copSSH Installed
XX.220: Winodws XP proffessional with cygwin installed
When I try to SSH from 188 to 125/220 it works like butter no problem at all.
But, when i try to ssh to 188 from 125/220 it logins succesfully for the first time, but after the 1st attempt it fails randomly.
Consider you attempt 5 times after first login:
Then there are 2/5 chances u can login or 3/5 or if your luck is good 5/5.
But 5/5 rarely happens.
Here is the script file of XX.220:
Script started on Tue Aug 3 19:20:12 2010
[Administrator@xpvm4dev

$ ssh Administrator@9.120.96.188
Last login: Fri Sep 3 03:20:06 2010 from dtmoutbound20.in.ibm.com


Administrator@windows-PC
$ logout

Connection to 9.120.96.188 closed.



Administrator@xpvm4dev

$ ssh Administrator@9.120.96.188
Last login: Fri Sep 3 03:24:30 2010 from dtmoutbound20.in.ibm.com


Administrator@windows-PC
$ logout

Connection to 9.120.96.188 closed.



Administrator@xpvm4dev

$ ssh Administrator@9.120.96.188
Last login: Fri Sep 3 03:24:40 2010 from dtmoutbound20.in.ibm.com


Administrator@windows-PC
$ logout

Connection to 9.120.96.188 closed.



Administrator@xpvm4dev

$ ssh Administrator@9.120.96.188
Last login: Fri Sep 3 03:24:47 2010 from dtmoutbound20.in.ibm.com


Administrator@windows-PC
$ logout

Connection to 9.120.96.188 closed.



Administrator@xpvm4dev

$ ssh Administrator@9.120.96.188
Last login: Fri Sep 3 03:24:54 2010 from dtmoutbound20.in.ibm.com


Administrator@windows-PC
$ logout

Connection to 9.120.96.188 closed.



Administrator@xpvm4dev

$ ssh Administrator@9.120.96.188
Last login: Fri Sep 3 03:25:02 2010 from dtmoutbound20.in.ibm.com


Administrator@windows-PC
$ logout

Connection to 9.120.96.188 closed.



Administrator@xpvm4dev

$ ssh Administrator@9.120.96.188
Last login: Fri Sep 3 03:25:14 2010 from dtmoutbound20.in.ibm.com


Administrator@windows-PC
$ logout

Connection to 9.120.96.188 closed.



Administrator@xpvm4dev

$ ssh Administrator@9.120.96.188
shell request failed on channel 0



Administrator@xpvm4dev

$ ssh Administrator@9.120.96.188
ssh_exchange_identification: read: Connection reset by peer



Administrator@xpvm4dev

$ ssh Administrator@9.120.96.188
Last login: Fri Sep 3 03:25:20 2010 from dtmoutbound20.in.ibm.com


Administrator@windows-PC
$ logout

Connection to 9.120.96.188 closed.



Administrator@xpvm4dev

$ ssh sh Administrator@9.120.96.125
sh: sssh: command not found


Administrator@xpvm4dev

$ shsssh Administrator@9.120.96.125
Last login: Fri Sep 3 03:23:25 2010 from dtmoutbound20.in.ibm.com


Administrator@manish-PC
$ logout

Connection to 9.120.96.125 closed.



Administrator@xpvm4dev

$ ssh Administrator@9.120.96.125
Last login: Fri Sep 3 03:26:18 2010 from dtmoutbound20.in.ibm.com


Administrator@manish-PC
$ logout

Connection to 9.120.96.125 closed.



Administrator@xpvm4dev

$ ssh Administrator@9.120.96.125
Last login: Fri Sep 3 03:26:24 2010 from dtmoutbound20.in.ibm.com


Administrator@manish-PC
$ logout

Connection to 9.120.96.125 closed.



Administrator@xpvm4dev

$ ssh Administrator@9.120.96.125
Last login: Fri Sep 3 03:26:30 2010 from dtmoutbound20.in.ibm.com


Administrator@manish-PC
$ logout

Connection to 9.120.96.125 closed.



Administrator@xpvm4dev

$ logoussh Administrator@9.120.96.125
Last login: Fri Sep 3 03:26:42 2010 from dtmoutbound20.in.ibm.com


Administrator@manish-PC
$ logout

Connection to 9.120.96.125 closed.



Administrator@xpvm4dev

$ sciptexit
exit

Script done on Tue Aug 3 19:24:14 2010
Posted Image
Posted Image

I would appreciate any help regarding this problem.

BC AdBot (Login to Remove)

 


#2 vinsor

vinsor
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:08:54 PM

Posted 05 August 2010 - 07:38 AM

In verbose mode:
This is what i found.
Unsuccessful Attempt script file:
Script started on Wed Aug 4 21:07:33 2010
]0;~

Administrator@xpvm4dev ~

$ exit
ssh -vvv Administrator@9.120.96.188
OpenSSH_5.4p1, OpenSSL 0.9.8m 25 Feb 2010
debug1: Reading configuration data /etc/ssh_config

debug2: ssh_connect: needpriv 0

debug1: Connecting to 9.120.96.188 [9.120.96.188] port 22.

debug1: Connection established.

debug1: identity file /home/Administrator/.ssh/id_rsa type -1

debug1: identity file /home/Administrator/.ssh/id_rsa-cert type -1

debug1: identity file /home/Administrator/.ssh/id_dsa type -1

debug1: identity file /home/Administrator/.ssh/id_dsa-cert type -1

debug1: Remote protocol version 2.0, remote software version OpenSSH_5.4

debug1: match: OpenSSH_5.4 pat OpenSSH*

debug1: Enabling compatibility mode for protocol 2.0

debug1: Local version string SSH-2.0-OpenSSH_5.4

debug2: fd 3 setting O_NONBLOCK

debug1: SSH2_MSG_KEXINIT sent

Read from socket failed: Connection reset by peer

]0;~

Administrator@xpvm4dev ~

$ exit
exit

Script done on Wed Aug 4 21:07:45 2010
------------------------------------------------------------------------------------
Successful script file:
Script started on Wed Aug 4 21:07:52 2010
]0;~

Administrator@xpvm4dev ~

$ exit
ssh -vvv Administrator@9.120.96.188
OpenSSH_5.4p1, OpenSSL 0.9.8m 25 Feb 2010
debug1: Reading configuration data /etc/ssh_config

debug2: ssh_connect: needpriv 0

debug1: Connecting to 9.120.96.188 [9.120.96.188] port 22.

debug1: Connection established.

debug1: identity file /home/Administrator/.ssh/id_rsa type -1

debug1: identity file /home/Administrator/.ssh/id_rsa-cert type -1

debug1: identity file /home/Administrator/.ssh/id_dsa type -1

debug1: identity file /home/Administrator/.ssh/id_dsa-cert type -1

debug1: Remote protocol version 2.0, remote software version OpenSSH_5.4

debug1: match: OpenSSH_5.4 pat OpenSSH*

debug1: Enabling compatibility mode for protocol 2.0

debug1: Local version string SSH-2.0-OpenSSH_5.4

debug2: fd 3 setting O_NONBLOCK

debug1: SSH2_MSG_KEXINIT sent

debug1: SSH2_MSG_KEXINIT received

debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1

debug2: kex_parse_kexinit: ssh-rsa-cert-v00@openssh.com,ssh-dss-cert-v00@openssh.com,ssh-rsa,ssh-dss

debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se

debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se

debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96

debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96

debug2: kex_parse_kexinit: none,zlib@openssh.com,zlib

debug2: kex_parse_kexinit: none,zlib@openssh.com,zlib

debug2: kex_parse_kexinit:

debug2: kex_parse_kexinit:

debug2: kex_parse_kexinit: first_kex_follows 0

debug2: kex_parse_kexinit: reserved 0

debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1

debug2: kex_parse_kexinit: ssh-rsa,ssh-dss

debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se

debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se

debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96

debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96

debug2: kex_parse_kexinit: none,zlib@openssh.com

debug2: kex_parse_kexinit: none,zlib@openssh.com

debug2: kex_parse_kexinit:

debug2: kex_parse_kexinit:

debug2: kex_parse_kexinit: first_kex_follows 0

debug2: kex_parse_kexinit: reserved 0

debug2: mac_setup: found hmac-md5

debug1: kex: server->client aes128-ctr hmac-md5 none

debug2: mac_setup: found hmac-md5

debug1: kex: client->server aes128-ctr hmac-md5 none

debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent

debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP

debug2: dh_gen_key: priv key bits set: 130/256

debug2: bits set: 497/1024

debug1: SSH2_MSG_KEX_DH_GEX_INIT sent

debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY

debug3: check_host_in_hostfile: host 9.120.96.188 filename /home/Administrator/.ssh/known_hosts

debug3: check_host_in_hostfile: host 9.120.96.188 filename /home/Administrator/.ssh/known_hosts

debug3: check_host_in_hostfile: match line 1

debug1: Host '9.120.96.188' is known and matches the RSA host key.

debug1: Found key in /home/Administrator/.ssh/known_hosts:1

debug2: bits set: 497/1024

debug1: ssh_rsa_verify: signature correct

debug2: kex_derive_keys

debug2: set_newkeys: mode 1

debug1: SSH2_MSG_NEWKEYS sent

debug1: expecting SSH2_MSG_NEWKEYS

debug2: set_newkeys: mode 0

debug1: SSH2_MSG_NEWKEYS received

debug1: Roaming not allowed by server

debug1: SSH2_MSG_SERVICE_REQUEST sent

debug2: service_accept: ssh-userauth

debug1: SSH2_MSG_SERVICE_ACCEPT received

debug2: key: /home/Administrator/.ssh/id_rsa (0x0)

debug2: key: /home/Administrator/.ssh/id_dsa (0x0)

debug1: Authentications that can continue: publickey,password,keyboard-interactive

debug3: start over, passed a different list publickey,password,keyboard-interactive

debug3: preferred publickey,keyboard-interactive,password

debug3: authmethod_lookup publickey

debug3: remaining preferred: keyboard-interactive,password

debug3: authmethod_is_enabled publickey

debug1: Next authentication method: publickey

debug1: Trying private key: /home/Administrator/.ssh/id_rsa

debug3: no such identity: /home/Administrator/.ssh/id_rsa

debug1: Trying private key: /home/Administrator/.ssh/id_dsa

debug3: no such identity: /home/Administrator/.ssh/id_dsa

debug2: we did not send a packet, disable method

debug3: authmethod_lookup keyboard-interactive

debug3: remaining preferred: password

debug3: authmethod_is_enabled keyboard-interactive

debug1: Next authentication method: keyboard-interactive

debug2: userauth_kbdint

debug2: we sent a keyboard-interactive packet, wait for reply

debug1: Authentications that can continue: publickey,password,keyboard-interactive

debug3: userauth_kbdint: disable: no info_req_seen

debug2: we did not send a packet, disable method

debug3: authmethod_lookup password

debug3: remaining preferred:

debug3: authmethod_is_enabled password

debug1: Next authentication method: password

Administrator@9.120.96.188's password:
debug3: packet_send2: adding 48 (len 66 padlen 14 extra_pad 64)
debug2: we sent a password packet, wait for reply
debug1: Authentication succeeded (password).
debug1: channel 0: new [client-session]
debug3: ssh_session2_open: channel_new: 0
debug2: channel 0: send open
debug1: Requesting no-more-sessions@openssh.com
debug1: Entering interactive session.
debug2: callback start
debug2: client_session2_setup: id 0
debug2: channel 0: request pty-req confirm 1
debug2: channel 0: request shell confirm 1
debug2: fd 3 setting TCP_NODELAY
debug2: callback done
debug2: channel 0: open confirm rwindow 0 rmax 32768
debug2: channel_input_status_confirm: type 99 id 0
debug2: PTY allocation request accepted on channel 0
debug2: channel 0: rcvd adjust 2097152
debug2: channel_input_status_confirm: type 99 id 0
debug2: shell request accepted on channel 0
Last login: Sat Sep 4 05:11:19 2010 from dtmoutbound20.in.ibm.com

]0;~
Administrator@windows-PC ~
$ logoutdebug1: client_input_channel_req: channel 0 rtype exit-status reply 0

debug1: client_input_channel_req: channel 0 rtype eow@openssh.com reply 0

debug2: channel 0: rcvd eow

debug2: channel 0: close_read

debug2: channel 0: input open -> closed

debug2: channel 0: rcvd eof

debug2: channel 0: output open -> drain

debug2: channel 0: rcvd close

debug3: channel 0: will not send data after close



debug3: channel 0: will not send data after close

debug2: channel 0: obuf empty

debug2: channel 0: close_write

debug2: channel 0: output drain -> closed

debug2: channel 0: almost dead

debug2: channel 0: gc: notify user

debug2: channel 0: gc: user detached

debug2: channel 0: send close

debug2: channel 0: is dead

debug2: channel 0: garbage collecting

debug1: channel 0: free: client-session, nchannels 1

debug3: channel 0: status: The following connections are open:

#0 client-session (t4 r0 i3/0 o3/0 fd -1/-1 cc -1)



debug3: channel 0: close_fds r -1 w -1 e 6

Connection to 9.120.96.188 closed.

Transferred: sent 2056, received 2456 bytes, in 3.7 seconds

Bytes per second: sent 557.6, received 666.1

debug1: Exit status 0

]0;~

Administrator@xpvm4dev ~

$ exit
exit

Script done on Wed Aug 4 21:08:06 2010

#3 vinsor

vinsor
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:08:54 PM

Posted 17 August 2010 - 05:15 AM

What are the other alternatives for SSH.

#4 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:01:54 AM

Posted 19 August 2010 - 02:26 PM

I have always had good luck with PuTTy I highly recommend it.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users