Welcome to the VanDyke Software Forums

Join the discussion today!


Go Back   VanDyke Software Forums > General

Reply
 
Thread Tools Display Modes
  #1  
Old 11-13-2012, 03:05 AM
jiangchx jiangchx is offline
Registered User
 
Join Date: Nov 2012
Posts: 1
Secure CRT cannot ssh linux server, but putty work fine.

Hello,

Recently, I tried to SecureCRT ssh2 EMC VPLEX manage server(an linux server), failed to login without any prompt, but putty worked fine.

Any idea on this?
Thanks

blow is the trace output while login:
SecureCRT - Version 6.5.3 (build 490)
[LOCAL] : SSH2Core version 6.5.0.490
[LOCAL] : 正在连接到 10.77.80.225:22 ...
[LOCAL] : 正在从状态 STATE_NOT_CONNECTED 更改为 STATE_EXPECT_KEX_INIT
[LOCAL] : Using protocol SSH2
[LOCAL] : RECV : Remote Identifier = 'SSH-2.0-OpenSSH_5.6'
[LOCAL] : CAP : Remote can re-key
[LOCAL] : CAP : Remote sends language in password change requests
[LOCAL] : CAP : Remote sends algorithm name in PK_OK packets
[LOCAL] : CAP : Remote sends algorithm name in public key packets
[LOCAL] : CAP : Remote sends algorithm name in signatures
[LOCAL] : CAP : Remote sends error text in open failure packets
[LOCAL] : CAP : Remote sends name in service accept packets
[LOCAL] : CAP : Remote includes port number in x11 open packets
[LOCAL] : CAP : Remote uses 160 bit keys for SHA1 MAC
[LOCAL] : CAP : Remote supports new diffie-hellman group exchange messages
[LOCAL] : CAP : Remote correctly handles unknown SFTP extensions
[LOCAL] : CAP : Remote correctly encodes OID for gssapi
[LOCAL] : CAP : Remote correctly uses connected addresses in forwarded-tcpip requests
[LOCAL] : CAP : Remote can do SFTP version 4
[LOCAL] : CAP : Remote x.509v3 uses ASN.1 encoding for DSA signatures
[LOCAL] : SSPI : Requesting full delegation
[LOCAL] : SSPI : [Kerberos] SPN : host@10.77.80.225
[LOCAL] : SSPI : [Kerberos] InitializeSecurityContext() failed.
[LOCAL] : SSPI : [Kerberos] The specified target is unknown or unreachable
[LOCAL] : SSPI : [Kerberos] Disabling gss mechanism
[LOCAL] : GSS : Requesting full delegation
[LOCAL] : GSS : [Kerberos] SPN : host@10.77.80.225
[LOCAL] : GSS : [Kerberos] InitializeSecurityContext() failed.
[LOCAL] : GSS : [Kerberos] Could not load library 'gssapi32.dll': The specified module could not be found.
[LOCAL] : GSS : [Kerberos] Disabling gss mechanism
[LOCAL] : GSS : [Kerberos] Disabling gss mechanism
[LOCAL] : The following key exchange method has been filtered from the key exchange method list because it is not supported: gss-group1-sha1-toWM5Slw5Ew8Mqkay+al2g==
[LOCAL] : SSPI : Requesting full delegation
[LOCAL] : SSPI : [Kerberos (Group Exchange)] SPN : host@10.77.80.225
[LOCAL] : SSPI : [Kerberos (Group Exchange)] InitializeSecurityContext() failed.
[LOCAL] : SSPI : [Kerberos (Group Exchange)] The specified target is unknown or unreachable
[LOCAL] : SSPI : [Kerberos (Group Exchange)] Disabling gss mechanism
[LOCAL] : GSS : Requesting full delegation
[LOCAL] : GSS : [Kerberos (Group Exchange)] SPN : host@10.77.80.225
[LOCAL] : GSS : [Kerberos (Group Exchange)] InitializeSecurityContext() failed.
[LOCAL] : GSS : [Kerberos (Group Exchange)] Could not load library 'gssapi32.dll': The specified module could not be found.
[LOCAL] : GSS : [Kerberos (Group Exchange)] Disabling gss mechanism
[LOCAL] : GSS : [Kerberos (Group Exchange)] Disabling gss mechanism
[LOCAL] : The following key exchange method has been filtered from the key exchange method list because it is not supported: gss-gex-sha1-toWM5Slw5Ew8Mqkay+al2g==
[LOCAL] : SEND : KEXINIT
[LOCAL] : RECV : Read kexinit
[LOCAL] : Available Remote Kex Methods = diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1
[LOCAL] : Selected Kex Method = diffie-hellman-group-exchange-sha1
[LOCAL] : Available Remote Host Key Algos = ssh-rsa,ssh-dss
[LOCAL] : Selected Host Key Algo = ssh-dss
[LOCAL] : Available Remote Send Ciphers = aes128-ctr,aes192-ctr,aes256-ctr,aes128-cbc,3des-cbc,aes192-cbc,aes256-cbc
[LOCAL] : Selected Send Cipher = aes256-ctr
[LOCAL] : Available Remote Recv Ciphers = aes128-ctr,aes192-ctr,aes256-ctr,aes128-cbc,3des-cbc,aes192-cbc,aes256-cbc
[LOCAL] : Selected Recv Cipher = aes256-ctr
[LOCAL] : Available Remote Send Macs = hmac-sha1
[LOCAL] : Selected Send Mac = hmac-sha1
[LOCAL] : Available Remote Recv Macs = hmac-sha1
[LOCAL] : Selected Recv Mac = hmac-sha1
[LOCAL] : Available Remote Compressors = none,zlib@openssh.com
[LOCAL] : Selected Compressor = none
[LOCAL] : Available Remote Decompressors = none,zlib@openssh.com
[LOCAL] : Selected Decompressor = none
[LOCAL] : 正在从状态 STATE_EXPECT_KEX_INIT 更改为 STATE_KEY_EXCHANGE
[LOCAL] : SEND : KEXDH_GEX_REQUEST
[LOCAL] : RECV : KEXDH_GEX_GROUP
[LOCAL] : SEND : KEXDH_INIT
[LOCAL] : Stream has closed [CLOSE_TYPE_NONSPECIFIC] : The operation completed successfully.
[LOCAL] : RECV: TCP/IP close
[LOCAL] : 正在从状态 STATE_KEY_EXCHANGE 更改为 STATE_CLOSED
[LOCAL] : 已连接 0 秒, 815 字节发送出, 725 字节接收到
Reply With Quote
  #2  
Old 11-13-2012, 10:36 AM
rtb rtb is offline
VanDyke Technical Support
 
Join Date: Aug 2008
Posts: 4,306
Hi jiangchx,

If you move diffie-hellman to the top of the Key exchange list located in the Connection / SSH2 category of the Session Options dialog, is this issue resolved?

If not, would you be able to post a successful connection log from putty?
__________________
--Todd

VanDyke Software
Technical Support
support@vandyke.com
505-332-5730

Last edited by rtb; 10-02-2014 at 09:20 AM.
Reply With Quote
  #3  
Old 10-02-2014, 08:35 AM
damos1972 damos1972 is offline
Registered User
 
Join Date: Oct 2014
Posts: 1
Having same issue with CRT Version 7.2.6 (x64 build 606)

Here is the Putty which works when connecting to the VPLEX



=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2014.10.02 14:31:27 =~=~=~=~=~=~=~=~=~=~=~=
Event Log: Writing new session log (SSH packets mode) to file: putty.log
Event Log: Looking up host "10.137.12.68"
Event Log: Connecting to 10.137.12.68 port 22
Event Log: We claim version: SSH-2.0-PuTTY_Release_0.63
Event Log: Server version: SSH-2.0-OpenSSH_5.6
Event Log: Using SSH protocol version 2
Outgoing packet #0x0, type 20 / 0x14 (SSH2_MSG_KEXINIT)

Incoming packet #0x0, type 20 / 0x14 (SSH2_MSG_KEXINIT)
..........
Event Log: Doing Diffie-Hellman group exchange
Outgoing packet #0x1, type 30 / 0x1e (SSH2_MSG_KEX_DH_GEX_REQUEST)
00000000 00 00 10 00 ....
Incoming packet #0x1, type 31 / 0x1f (SSH2_MSG_KEX_DH_GEX_GROUP)
.
Event Log: Host key fingerprint is:
Event Log: ssh-rsa 1024 97:15:9d:1f:d6:a6:7d:8c:59:4f:01:18:4d:c3:8c:0d
Outgoing packet #0x3, type 21 / 0x15 (SSH2_MSG_NEWKEYS)
Event Log: Initialised AES-256 SDCTR client->server encryption
Event Log: Initialised HMAC-SHA1 client->server MAC algorithm
Incoming packet #0x3, type 21 / 0x15 (SSH2_MSG_NEWKEYS)
Event Log: Initialised AES-256 SDCTR server->client encryption
Event Log: Initialised HMAC-SHA1 server->client MAC algorithm
Outgoing packet #0x4, type 5 / 0x05 (SSH2_MSG_SERVICE_REQUEST)
00000000 00 00 00 0c 73 73 68 2d 75 73 65 72 61 75 74 68 ....ssh-userauth
Incoming packet #0x4, type 6 / 0x06 (SSH2_MSG_SERVICE_ACCEPT)
00000000 00 00 00 0c 73 73 68 2d 75 73 65 72 61 75 74 68 ....ssh-userauth
Reply With Quote
  #4  
Old 10-02-2014, 09:26 AM
rtb rtb is offline
VanDyke Technical Support
 
Join Date: Aug 2008
Posts: 4,306
Hi damos1972,

Thanks for the post. Since logs can have sensitive information, please send an email to support@vandyke.com. Please attach a complete SecureCRT trace, and a complete Putty log, but make sure that the Putty log doesn't have your password in it.
__________________
--Todd

VanDyke Software
Technical Support
support@vandyke.com
505-332-5730
Reply With Quote
  #5  
Old 10-14-2014, 06:02 PM
GoSWH GoSWH is offline
Registered User
 
Join Date: Oct 2014
Location: DC
Posts: 2
Cool SSHv2 with Putty works, but not with SecureCRT

Any help with this would be appreciated as I am having this exact same issue using SecureCRT to connect to an ESXi host via SSH. I can connect just fine to this ESXi server via Putty but not with SecureCRT.

Looking at the VMware release notes, it states that only SSH v2 is supported using 256-bit and 128-bit AES ciphers.

Note: My wrinkle to the issue is that I use a password manager and have variables in the command lines of each program to launch the session.

Sample Command line entries:
Putty: c:\PuTTY\putty.exe -ssh <dummyuser>@<Local IP> <First Port> -pw <Password>

SecureCRT: C:\PROGRA~1\VANDYK~1\SecureCRT\SecureCRT.exe /T /SSH2 /AUTH password /L <dummyuser> /PASSWORD %PASS% <Local IP>:<First Port>
Also, I have no issue with Putty or SecureCRT with standard Linux/UNIX servers like Ubuntu, Debian, Red Hat, AIX, Solaris, etc. I can use this same command line (minus the <dummyuser> field) on several other linux and unix hosts with no issues.

Here are the Putty connection logs:
2014-10-14 18:15:45 Looking up host "127.22.22.5"
2014-10-14 18:15:45 Connecting to 127.22.22.5 port 2230
2014-10-14 18:15:46 Server version: SSH-2.0-OpenSSH_3.9p1
2014-10-14 18:15:46 Using SSH protocol version 2
2014-10-14 18:15:46 We claim version: SSH-2.0-PuTTY_Release_0.63
2014-10-14 18:15:46 Doing Diffie-Hellman group exchange
2014-10-14 18:15:46 Doing Diffie-Hellman key exchange with hash SHA-1
2014-10-14 18:15:46 Host key fingerprint is:
2014-10-14 18:15:46 ssh-rsa 2048 02:53:1e:81:68:7b:63:d4:77:8b:b4:34:cb:3b:08:43
2014-10-14 18:15:46 Initialised AES-256 SDCTR client->server encryption
2014-10-14 18:15:46 Initialised HMAC-SHA1 client->server MAC algorithm
2014-10-14 18:15:46 Initialised AES-256 SDCTR server->client encryption
2014-10-14 18:15:46 Initialised HMAC-SHA1 server->client MAC algorithm
2014-10-14 18:15:46 Writing new session log (raw mode) to file: C:\Users\Shawn Hank\Desktop\putty.log
2014-10-14 18:15:46 Attempting keyboard-interactive authentication
2014-10-14 18:15:47 Access granted
2014-10-14 18:15:47 Opening session as main channel
2014-10-14 18:15:47 Opened main channel
2014-10-14 18:15:47 Allocated pty (ospeed 38400bps, ispeed 38400bps)
2014-10-14 18:15:47 Started a shell/command
Here are the SecureCRT logs:
[LOCAL] : SSH2Core version 7.2.0.524
[LOCAL] : Connecting to 127.22.22.5:2231 ...
[LOCAL] : Changing state from STATE_NOT_CONNECTED to STATE_EXPECT_KEX_INIT
SecureCRT - Version 7.2.4 (x64 build 524)
[LOCAL] : Using protocol SSH2
[LOCAL] : RECV : Remote Identifier = 'SSH-2.0-OpenSSH_3.9p1'
[LOCAL] : CAP : Remote can re-key
[LOCAL] : CAP : Remote sends language in password change requests
[LOCAL] : CAP : Remote sends algorithm name in PK_OK packets
[LOCAL] : CAP : Remote sends algorithm name in public key packets
[LOCAL] : CAP : Remote sends algorithm name in signatures
[LOCAL] : CAP : Remote sends error text in open failure packets
[LOCAL] : CAP : Remote sends name in service accept packets
[LOCAL] : CAP : Remote includes port number in x11 open packets
[LOCAL] : CAP : Remote uses 160 bit keys for SHA1 MAC
[LOCAL] : CAP : Remote supports new diffie-hellman group exchange messages
[LOCAL] : CAP : Remote correctly handles unknown SFTP extensions
[LOCAL] : CAP : Remote correctly encodes OID for gssapi
[LOCAL] : CAP : Remote correctly uses connected addresses in forwarded-tcpip requests
[LOCAL] : CAP : Remote can do SFTP version 4
[LOCAL] : CAP : Remote x.509v3 uses ASN.1 encoding for DSA signatures
[LOCAL] : CAP : Remote correctly handles zlib@openssh.com
[LOCAL] : SSPI : Requesting full delegation
[LOCAL] : SSPI : [Kerberos] SPN : host@127.22.22.5
[LOCAL] : SSPI : [Kerberos] InitializeSecurityContext() failed.
[LOCAL] : SSPI : [Kerberos] The specified target is unknown or unreachable
[LOCAL] : SSPI : [Kerberos] Disabling gss mechanism
[LOCAL] : GSS : Requesting full delegation
[LOCAL] : GSS : [Kerberos] SPN : host@127.22.22.5
[LOCAL] : GSS : [Kerberos] InitializeSecurityContext() failed.
[LOCAL] : GSS : [Kerberos] Could not load library 'gssapi64.dll': The specified module could not be found.
[LOCAL] : GSS : [Kerberos] Disabling gss mechanism
[LOCAL] : GSS : [Kerberos] Disabling gss mechanism
[LOCAL] : The following key exchange method has been filtered from the key exchange method list because it is not supported: gss-group1-sha1-toWM5Slw5Ew8Mqkay+al2g==
[LOCAL] : SSPI : Requesting full delegation
[LOCAL] : SSPI : [Kerberos (Group Exchange)] SPN : host@127.22.22.5
[LOCAL] : SSPI : [Kerberos (Group Exchange)] InitializeSecurityContext() failed.
[LOCAL] : SSPI : [Kerberos (Group Exchange)] The specified target is unknown or unreachable
[LOCAL] : SSPI : [Kerberos (Group Exchange)] Disabling gss mechanism
[LOCAL] : GSS : Requesting full delegation
[LOCAL] : GSS : [Kerberos (Group Exchange)] SPN : host@127.22.22.5
[LOCAL] : GSS : [Kerberos (Group Exchange)] InitializeSecurityContext() failed.
[LOCAL] : GSS : [Kerberos (Group Exchange)] Could not load library 'gssapi64.dll': The specified module could not be found.
[LOCAL] : GSS : [Kerberos (Group Exchange)] Disabling gss mechanism
[LOCAL] : GSS : [Kerberos (Group Exchange)] Disabling gss mechanism
[LOCAL] : The following key exchange method has been filtered from the key exchange method list because it is not supported: gss-gex-sha1-toWM5Slw5Ew8Mqkay+al2g==
[LOCAL] : SEND : KEXINIT
[LOCAL] : RECV : Read kexinit
[LOCAL] : Available Remote Kex Methods = diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1
[LOCAL] : Selected Kex Method = diffie-hellman-group14-sha1
[LOCAL] : Available Remote Host Key Algos = ssh-rsa,ssh-dss
[LOCAL] : Selected Host Key Algo = ssh-dss
[LOCAL] : Available Remote Send Ciphers = aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-cbc,rijndael-cbc@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-ctr
[LOCAL] : Selected Send Cipher = aes256-ctr
[LOCAL] : Available Remote Recv Ciphers = aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-cbc,rijndael-cbc@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-ctr
[LOCAL] : Selected Recv Cipher = aes256-ctr
[LOCAL] : Available Remote Send Macs = hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
[LOCAL] : Selected Send Mac = hmac-sha1
[LOCAL] : Available Remote Recv Macs = hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
[LOCAL] : Selected Recv Mac = hmac-sha1
[LOCAL] : Available Remote Compressors = none,zlib
[LOCAL] : Selected Compressor = none
[LOCAL] : Available Remote Decompressors = none,zlib
[LOCAL] : Selected Decompressor = none
[LOCAL] : Changing state from STATE_EXPECT_KEX_INIT to STATE_KEY_EXCHANGE
[LOCAL] : SEND : KEXDH_INIT
[LOCAL] : RECV : KEXDH_REPLY
[LOCAL] : Changing state from STATE_KEY_EXCHANGE to STATE_READY_FOR_NEW_KEYS
[LOCAL] : RECV: Remote Hostkey: 65:b7:98:95:ad:7a:c7:52:e8:cc:65:85:b2:1e:13:0b
[LOCAL] : SEND : NEWKEYS
[LOCAL] : Changing state from STATE_READY_FOR_NEW_KEYS to STATE_EXPECT_NEWKEYS
[LOCAL] : RECV : NEWKEYS
[LOCAL] : Changing state from STATE_EXPECT_NEWKEYS to STATE_CONNECTION
[LOCAL] : SEND: SERVICE_REQUEST[ssh-userauth]
[LOCAL] : RECV: SERVICE_ACCEPT[ssh-userauth] -- OK
[LOCAL] : SENT : USERAUTH_REQUEST [none]
[LOCAL] : RECV : SSH_MSG_USERAUTH_BANNER
[LOCAL] : RECV : USERAUTH_FAILURE, continuations [publickey,keyboard-interactive]
[LOCAL] : SEND: Disconnect packet: Unable to authenticate using any of the configured authentication methods.
[LOCAL] : Changing state from STATE_CONNECTION to STATE_SEND_DISCONNECT
[LOCAL] : Changing state from STATE_SEND_DISCONNECT to STATE_CLOSED
[LOCAL] : Connected for 0 seconds, 1197 bytes sent, 1618 bytes received
[LOCAL] : Stream has closed [CLOSE_TYPE_NONSPECIFIC] : The client has disconnected from the server. Reason: Unable to authenticate using any of the configured authentication methods.

The client has disconnected from the server. Reason:
Unable to authenticate using any of the configured authentication methods.
Reply With Quote
  #6  
Old 10-14-2014, 06:16 PM
rtb rtb is offline
VanDyke Technical Support
 
Join Date: Aug 2008
Posts: 4,306
Hi GoSWH,

This looks like a known issue with some SSH2 servers. They advertise supporting ssh-dss, and that is what SecureCRT choses by default since it is the one algorithm that is required by the SSH2 protocol.

My guess is that the server doesn't support it or is misconfigured.

If you edit the Default.ini file such that SecureCRT uses ssh-rsa, do you see better results?
To edit the Default.ini file:
  1. Close all instances of SecureCRT. If changes are made to the Default.ini file while SecureCRT is running, the changes made will be undone when SecureCRT is closed.
  2. Edit Default.ini file (located in the Sessions subfolder of SecureCRT's configuration folder location indicated by the Configuration folder field in the General / Configuration Paths category of the Global Options dialog. Add/modify lines as instructed.
  3. Save the Default.ini file and start SecureCRT.

    Note: If you have a /f in the target of the shortcut used to launch SecureCRT, then the path to the Config folder will be different than the path in step 2 above.
Here are the lines to edit:
From:
D:"Use Global Host Key Algorithms"=00000001
To:
D:"Use Global Host Key Algorithms"=00000000
From:
S:"Host Key Algorithms"=ssh-dss,ssh-rsa,null,x509v3-sign-rsa,x509v3-sign-dss
To:
S:"Host Key Algorithms"=ssh-rsa,ssh-dss,null,x509v3-sign-rsa,x509v3-sign-dss
__________________
--Todd

VanDyke Software
Technical Support
support@vandyke.com
505-332-5730
Reply With Quote
  #7  
Old 10-14-2014, 06:42 PM
GoSWH GoSWH is offline
Registered User
 
Join Date: Oct 2014
Location: DC
Posts: 2
re:rtb

Hi, Todd.

I made the changes as you suggested and still end up at the same place. (i.e., Error Message -
The client has disconnected from the server. Reason:
Unable to authenticate using any of the configured authentication methods.
I was playing around and found out the below. Please let me know your thoughts:

If I manually setup a connection to the same server using the Quick Connect feature and I select Password as the auth method, I get the same error as described above.

When I change from Password to Keyboard Interactive, and I manually paste the password, the connection is successful.

I've got the traces in a separate file to send over to you. I wasn't able to paste them here due to the 10,000 character limit on the forum.


And it doesn't matter if DSS or RSA is first in either of the locations where I made the change. This behavior is consistent regardless of the suggested changes.

-S
Reply With Quote
  #8  
Old 10-15-2014, 09:17 AM
rtb rtb is offline
VanDyke Technical Support
 
Join Date: Aug 2008
Posts: 4,306
Hi GoSWH,

Thanks for the update. It doesn't sound like this is the same issue jiangchx experienced.

You are welcome to send the data to support@vandyke.com with a subject of Attn: Todd - forum thread #10755.

It makes sense that keyboard interactive is working because that is what the server supports. The server doesn't support password authentication, so if that is what you have configured SecureCRT to use, then the disconnect is expected.

I will wait to get your email so we can continue to work on this issue.
__________________
--Todd

VanDyke Software
Technical Support
support@vandyke.com
505-332-5730
Reply With Quote
  #9  
Old 02-11-2015, 05:11 PM
helloguys helloguys is offline
Registered User
 
Join Date: Feb 2015
Posts: 1
I got the exact same symptom and the workaround works for me as well.

OS: Windows 7 x64 SP1 Enterprise Edition
SecureCRT: Version 7.3.1 (x64 build 685)
SSH Server: Cisco Nexus C7010, NX-OS version 6.1(1)

Symptom:
I tried to SSH to the Nexus switch with SecureCRT. But Nexus kept rejecting the password. I knew the password was correct because I Putty works just fine.

Workaround:
From SecureCRT, disable all authentication methods except for "Keyboard Interactive". Now I'm able to authenticate.

What logs do I collect to troubleshoot this? Thanks!
Reply With Quote
  #10  
Old 02-11-2015, 05:17 PM
rtb rtb is offline
VanDyke Technical Support
 
Join Date: Aug 2008
Posts: 4,306
Hi helloguys,

Thanks for the post.

By way of explanation, Putty supports keyboard-interactive authentication, but not password authentication. Since keyboard-interactive authentication is successful in both SecureCRT and Putty, and password authentication is not successful in SecureCRT, the workaround is to use keyboard-interactive authentication in SecureCRT.

This issue is not specific to SecureCRT. It sounds like the SSH2 server advertises password authentication as an option, but doesn't support password authentication. If you would like to troubleshoot this further, you may consider contacting Cisco to work with them regarding the SSH2 server that advertises an authentication method that doesn't work.

Does this help to answer your question?
__________________
--Todd

VanDyke Software
Technical Support
support@vandyke.com
505-332-5730

Last edited by rtb; 02-11-2015 at 05:46 PM.
Reply With Quote
  #11  
Old 01-25-2019, 02:08 PM
teggenberger teggenberger is offline
Registered User
 
Join Date: May 2014
Posts: 15
Secure CRT cannot SSH, Putty works fine.

Was this issue ever resolved or did this thread just die?
I'm having the same issue as the aforementioned.
I didn't see a fix anywhere in the thread
...and none of the 'workarounds' that were posted worked.

Last edited by teggenberger; 01-25-2019 at 02:31 PM.
Reply With Quote
  #12  
Old 01-25-2019, 02:28 PM
ekoranyi ekoranyi is offline
VanDyke Technical Support
 
Join Date: Jan 2017
Posts: 654
Hi teggenberger,

What trouble are you having? In reviewing this thread it seems a couple of issues were discussed, host key algorithms and authentication methods.

The most recent post was a case of the remote server only supporting keyboard interactive authentication, not password, the solution is to simply configure SecureCRT to use keyboard interactive before trying password.

Perhaps reviewing a log of your connection attempt would give me a better idea of the changes needed.

PLEASE DO NOT POST YOUR LOG TO THE FORUMS.

Can you take these steps and send me the resulting log file for analysis?
Video Link: Trace Options Debug Logging in SecureCRT
- Launch SecureCRT and open SecureCRT's main "File" menu and select the "Trace Options" menu item.

- Open the "File" menu again and choose "Log Session..."
--> Specify a path to your Desktop folder and a name of the log file, such as SCRT_Log.txt.

- Now attempt your connection again.

- When the connection fails, open SecureCRT's "File" menu and look at the "Log Session" menu item. If it has a check-mark next to it, click on it to turn off logging.

- Go to your Desktop folder and locate the SCRT_Log.txt.
Please email the log as an attachment to Support@VanDyke.com with "Attn: Eric Forum Post 10755" in the subject line. In the email please include the version of SecureCRT you are running, serial number associated with your license data, and the Operating System you are running on. The version and license data can be found by choosing About SecureCRT... from the main Help drop down menu.
__________________
Thanks,
--Eric

VanDyke Software
Technical Support
support@vandyke.com
(505) 332-5730
Reply With Quote
Reply


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -6. The time now is 04:44 PM.