Welcome to the VanDyke Software Forums

Join the discussion today!


Go Back   VanDyke Software Forums > General

Reply
 
Thread Tools Display Modes
  #1  
Old 07-29-2020, 04:00 PM
brae09 brae09 is offline
Registered User
 
Join Date: Jul 2020
Posts: 1
SecureCRT not working trying to connect to CentOS 8

SecureCRT is running on a Windows 10 computer. It cannot connect to a CentOS 8 server. It has no problem connecting to other Linux servers running CentOS 7. From the same Windows computer, I could connect to the CentOS 8 server using other programs, like Windows Terminal. Other users could connect to the server from other computers using Putty and other tools. Below is the tracing output from SecureCRT's failed connection attempt. Thank you very much for your help!

SecureCRT - Version 3.4
[SSH LOCAL ONLY] : SecureCRT(3.4) : Using SSH2Core v2.0
[SSH LOCAL ONLY] : State Change: SSH_STATE_UNINITIALIZED->SSH_STATE_CONNECTING
[SSH LOCAL ONLY] : State Change: SSH_STATE_CONNECTING->SSH_STATE_EXPECT_IDENTIFIER
[SSH LOCAL ONLY] : connected
[SSH LOCAL ONLY] : RECV : Remote Identifier = "SSH-2.0-OpenSSH_8.0"
[SSH LOCAL ONLY] : CAP : Remote can re-key
[SSH LOCAL ONLY] : CAP : Remote sends language in password change requests
[SSH LOCAL ONLY] : CAP : Remote sends algorithm name in PK_OK packets
[SSH LOCAL ONLY] : CAP : Remote sends algorithm name in public key packets
[SSH LOCAL ONLY] : CAP : Remote sends algorithm name in signatures
[SSH LOCAL ONLY] : CAP : Remote sends error text in open failure packets
[SSH LOCAL ONLY] : CAP : Remote sends name in service accept packets
[SSH LOCAL ONLY] : CAP : Remote includes port number in x11 open packets
[SSH LOCAL ONLY] : CAP : Remote uses 160 bit keys for SHA1 MAC
[SSH LOCAL ONLY] : CAP : Remote supports new diffie-hellman group exchange messages
[SSH LOCAL ONLY] : CAP : Remote is IETF-DRAFT compliant
[SSH LOCAL ONLY] : SEND : KEXINIT
[SSH LOCAL ONLY] : State Change: SSH_STATE_EXPECT_IDENTIFIER->SSH_STATE_INITIAL_KEYEXCHANGE
[SSH LOCAL ONLY] : RECV : Read kexinit
[SSH LOCAL ONLY] : Kex Method = diffie-hellman-group-exchange-sha1
[SSH LOCAL ONLY] : Host Key Algo = ssh-rsa
[SSH LOCAL ONLY] : Send Cipher = aes128-cbc
[SSH LOCAL ONLY] : Recv Cipher = aes128-cbc
[SSH LOCAL ONLY] : Send Mac = hmac-sha1
[SSH LOCAL ONLY] : Recv Mac = hmac-sha1
[SSH LOCAL ONLY] : Compressor = none
[SSH LOCAL ONLY] : Decompressor = none
[SSH LOCAL ONLY] : SEND : KEXDH_GEX_REQUEST
[SSH LOCAL ONLY] : RECV: TCP/IP close
[SSH LOCAL ONLY] : State Change: SSH_STATE_INITIAL_KEYEXCHANGE->SSH_STATE_CLOSED
[SSH LOCAL ONLY] : Connected for 0 seconds, 439 bytes sent, 1069 bytes received
Reply With Quote
  #2  
Old 07-30-2020, 07:13 AM
bgagnon bgagnon is offline
VanDyke Technical Support
 
Join Date: Oct 2008
Posts: 4,352
Hi brae09,

SecureCRT v3.4 is about 20 years old!

It's unlikely you have the necessary ciphers, MACs and key exchange algos even available that more modern SSH servers require.

The only other key exchange method available in your version of SecureCRT is one that should not be used due to a theoretical vulnerability related to the TLS Logjam vulnerability.

Please send serial number in the body of an email to support@vandyke.com and reference Forum Thread #14243 so we can check your eligibility for newer versions.

Please DO NOT post the serial number in the public forums.
__________________
Thanks,
--Brenda

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 02:18 PM.