Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Wednesday, April 11, 2018 2:43 AM
Hi Forum,
I am currently running on Windows 10 Professional. I came to know that Telnet Server is not included in Windows 10. As a supplement, they have provided beta versions of OpenSSH Client and Server respectively.
However, after installing both these beta versions and rebooting the PC I was unable to run SSH using teraterm client. When I checked the SSHD logs, below is what I found.
11928 12:58:00:929 Unable to negotiate with 127.0.0.1 port 51140: no matching key exchange method found. Their offer: ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1
The SSH client is using the exchange method curve25519-sha256, but the SSH server only supports the exchange methods listed above and hence I was unable to use the SSH.
So, I tried to add one of the exchange methods used by SSH Server in SSH Client by the running the below command from the command prompt (ran as administrator).
C:\Windows\system32\OpenSSH>ssh - oKexAlgorithms=+diffie-hellman-group-exchange-sha256 127.0.0.1
But the system gave the below error message.
ssh: Could not resolve hostname -: No such host is known.
Please note, I also tried changing the hostname from 127.0.0.1 to the one displayed under ipconfig command, but the same error was encountered.
Can you please advise, how this error can be resolved in order to successfully use SSH in windows 10 ?
Thanks in advance.
All replies (7)
Wednesday, April 11, 2018 7:18 AM
Hi Naveen_UM,
Did you have a look at this guide?
Regards
Simon
If you find that my post has answered your question, please mark it as the answer. If you find my post to be helpful in anyway, please click vote as helpful. Regards Simon Disclaimer: This posting is provided AS IS with no warranties or guarantees, and confers no rights.
Friday, April 13, 2018 4:02 AM
Hi Simon,
Thank you for the response. Yes, I have seen this guide, but unfortunately it doesn't say anything about the problem I encountered !!
Regards,
Naveen
Friday, April 20, 2018 6:41 AM
Hi,
We haven’t heard from you for a couple of days, have you solved the problem?
Please remember to mark the replies as answers if they help. If you have feedback for TechNet Subscriber Support, contact [email protected].
Saturday, May 12, 2018 4:31 PM
Hello Naveen,
I was having the same error. However, trying to ssh to my computer through the Ubuntu Linux Subsystem made the connection work. At this point, my computer asked for the password, but it wouldn't connect at all.
I've seen in another forum people telling to disable the SSH Server Broker and SSH Server Proxy, that are being installed with the OpenSSH since a couple months ago. I disabled the two services and it all suddenly started to work.
I don't know what are these services actually for, but one thing I've noticed is that all my ssh clients complained about the changed server key, so I had to remove the entry on .ssh/known_hosts file.
Hope this helps,
Carlos
Tuesday, March 26, 2019 1:51 PM | 1 vote
I know this is old but you never know when someone will stumble upon it.
The reason you get the error is, as you said, the exchange methods are incompatible.
The following error dealing with the hostname is due to syntax. I'm not sure if you are trying to connect to localhost or not but that command is used to define the exchange method while initiation a connection and should look like the below.
E.g. My client > remote host server.domain.com with username admin
ssh -oKexAlgorithms=+diffie-hellman-group1-sha1 [email protected]
Wednesday, June 19, 2019 12:01 PM
You will see this if the host you are trying to connect to is configured to be fips compliant.
Wednesday, July 22, 2020 2:20 PM
I was able to get connected to my switch by combining two ciphers with "ssh -oKexAlgorithms=+diffie-hellman-group1-sha1 -c aes256-cbc [email protected]"