![]() Have you tried to use a different SSH client? Have you tried Putty? Possibly it will be simpler, if you use Putty on Windows workstation and server, so you can directly compare.Īlso running ssh with -vvv parameter can give you a bit more insight and possibly hint what went wrong. If you just copied the keypair files from a Windows computer, it could be placed in the wrong location or wrong filename. What kind of SSH are you using? Different incarnations save things at different locations. ![]() A test against a Linux system could help testing. If you transferred the keypair, it could be possible, that the transfer was not done correctly. On the Windows server - is the public key generated separately for this user/server? Or did you transfer the keypair from a Windows workstation? I'd rather guess, that it is sending the wrong key!ĭo you have a Linux system at hand? That should allow you to check if the same key works from both windows platforms, or if it fails. So I don't really believe, that under 2016 a 'different type of private key' would be sent to the remote host. A public key is a public key, no matter what OS is connecting to a remote server.
0 Comments
Leave a Reply. |