Hi folks, I'm new to Windows servers have mostly used AIX, HP-UX, and Linux.  The server to which I'm trying to connect is controlled by the IT department of Nashville Metropolitan Government.  I have gotten into server management and can see that the SSH server is runnung but when I try to make the connection with AccuTerm, I get an AccuTerm error that "No supported SSH2 signature scheme exists".  When I click on the details it tells me that AccuTerm supports ssh-dss and ssh-rsa.  I know lots of you are using AccuTerm on Windows servers, can anybody suggest what I am lacking.  I suspect there is something on the server that I need to enable or set up.  As I said, I have limited knowledge on Windows servers; or is there something I need to enable on the AccuTerm?

Dale

Are you sure you're using AccuTerm 8?  AccuTerm 7 doesn't have the newer key exchange methods and newer versions of Linux (I don't know about Windows) don't support the older "insecure" methods.

Yes, it's AccuTerm 8.1, I think.  This is an upgrade to a new server and the customer (department) is finally moving up from Dynamic Connect.

Hi Dale,

We played around with the Bitvise SSH server recently and had no problems connecting to our Windows QM server. This was using AccuTerm 8.1.1.1135. Since then, there has been another point release (1136); and now 8.1.2 has been released.

Looking at the 'atsp' file, I can see that the sshVersion is set to 2, and sshAuth is set to KERBEROS. The file also contains the SSH fingerprint to validate connections. (We used Host validation of 'Trust on first use').

Looking at the release notes, version 8.1.1 added some extra ciphers and elliptic curve keys. See: https://docs.rocketsoftware.com/bundle/accuterm_release_8.1.2/page/ndn1693411429101.html

It may be worth checking your AccuTerm version - make sure you have at least 8.1.1 - and preferably 8.1.2.

Cheers,

Brian

Thanks Brian,

As I look more closely I see my version of AccuTerm is 8.0.  I'll upgrade it and try again.  Thanks to Joe also.

Hi Dale - 

Probably the new Windows server version of SSH does not support SHA1 hashing, and ssh-dss and ssh-rsa signatures use SHA1 hash. Newer versions of AccuTerm support SHA2-256 and SHA2-512 hash as well as several elliptic curve signature algorithms.

In my experience, Windows SSH does not play nicely with MV databases. I have not figured out how to configure it to leave the data alone, it always wants to interpret the data on the ssh connection as VT100/ANSI and mangles it as it moves from client to server and vice versa. As Brian mentioned, Bitvise SSH might work better. If you find that Windows SSH works, please post your results.

Thanks, Pete

Hi Dale,

We played around with the Bitvise SSH server recently and had no problems connecting to our Windows QM server. This was using AccuTerm 8.1.1.1135. Since then, there has been another point release (1136); and now 8.1.2 has been released.

Looking at the 'atsp' file, I can see that the sshVersion is set to 2, and sshAuth is set to KERBEROS. The file also contains the SSH fingerprint to validate connections. (We used Host validation of 'Trust on first use').

Looking at the release notes, version 8.1.1 added some extra ciphers and elliptic curve keys. See: https://docs.rocketsoftware.com/bundle/accuterm_release_8.1.2/page/ndn1693411429101.html

It may be worth checking your AccuTerm version - make sure you have at least 8.1.1 - and preferably 8.1.2.

Cheers,

Brian

I got BitVise working with Accuterm by using both the BitVise client and server. Just using port forwarding.  Can I eliminate the BitVise client?  I can connect to the server after setting up a user, but how do I connect the server to the D3 telnet server?