Thank you for the suggestion. I've tried all I can to remove existing keys. Do Putty, WinSCP and OpenSSH (Win 10) all keep the local key info in the same place (I'm doubtful)? I'm having the same problem despite my efforts (mostly with a fair bit of Google help).

Any further guidance would be most appreciated. I'm no expert on SSH, however I'm a quick learner.

Rgds, Steve.

@oyyodams - I did have the 2018.12.24 Christmas.Beta release on that Pi3 (and remains available on another SD card). There is indeed an external (32Gb USB) storage device that is connected to the Pi containing ROMs.

Hi folks,

I've deployed the current (6.0-DragonBlaze Build 193955549) image onto a Pi3. I'm unable to connect to it via ssh for some reason. When I ssh -v I get this.....

C:>ssh -v root@192.168.2.172
OpenSSH_for_Windows_7.6p1, LibreSSL 2.6.4
debug1: Connecting to 192.168.2.172 [192.168.2.172] port 22.
debug1: Connection established.
debug1: key_load_public: No such file or directory
debug1: identity file C:\Users\steve/.ssh/id_rsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file C:\Users\steve/.ssh/id_rsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file C:\Users\steve/.ssh/id_dsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file C:\Users\steve/.ssh/id_dsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file C:\Users\steve/.ssh/id_ecdsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file C:\Users\steve/.ssh/id_ecdsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file C:\Users\steve/.ssh/id_ed25519 type -1
debug1: key_load_public: No such file or directory
debug1: identity file C:\Users\steve/.ssh/id_ed25519-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_for_Windows_7.6
debug1: Remote protocol version 2.0, remote software version dropbear_2017.75
debug1: no match: dropbear_2017.75
debug1: Authenticating to 192.168.2.172:22 as 'root'
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: curve25519-sha256@libssh.org
debug1: kex: host key algorithm: ecdsa-sha2-nistp521
debug1: kex: server->client cipher: aes128-ctr MAC: hmac-sha2-256 compression: none
debug1: kex: client->server cipher: aes128-ctr MAC: hmac-sha2-256 compression: none
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
Connection closed by 192.168.2.172 port 22

I'm keen to connect using Putty to work out why I can't get the Amiga emulator to work

Any help more gratefully received.
Steve C.