Packet Tracer Authentication Failed. Please Try Again.
Unable to access the win10 PC with OpenSSH installed through ssh command
I have installed the OpenSSH client and server in my win10 PC through this website (https://docs.microsoft.com/en-us/windows-server/administration/openssh/openssh_install_firstuse). However, when I tried to access the PC with ssh command through another PC, the ssh connection showed the error message with Permission denied, please effort again. fifty-fifty if I entered the right username and password. When I tried to access through administrator, the mistake bulletin was Connection reset by xxx.xxx.thirty.xxx.
In lodge to verify this problem, I tried ssh control on the same PC. And the error message kept showing. But when I use ssh command to access some other Linux PC, everything was working functionally.
Are at that place any other settings that need to be done with the OpenSSH server?
My OS is win10 Enterprise Edition LTSC ver. 1809 with 17763.1457
Here is the debug data on the server and client sides.
Administrator Fashion PowerShell
Server Side
shell PS C:\ProgramData\ssh> sshd.exe -d debug1: sshd version OpenSSH_for_Windows_7.7, LibreSSL two.6.v debug1: private host key #0: {} debug1: private host cardinal #one: {} debug1: individual host central #2: {} debug1: rexec_argv[0]='C:\\Windows\\System32\\OpenSSH\\sshd.exe' debug1: rexec_argv[1]='-d' debug1: Bind to port 23 on ::. Server listening on :: port 23. debug1: Bind to port 23 on 0.0.0.0. Server listening on 0.0.0.0 port 23. Client Side
beat PS C:\Windows\system32> ssh.exe -v -p 23 LiBai@127.0.0.one OpenSSH_for_Windows_7.7p1, LibreSSL 2.six.v debug1: Connecting to 127.0.0.one [127.0.0.1] port 23. debug1: Connectedness established. debug1: key_load_public: No such file or directory debug1: identity file C:\\Users\\LiBai/.ssh/id_rsa type -1 debug1: key_load_public: No such file or directory debug1: identity file C:\\Users\\LiBai/.ssh/id_rsa-cert blazon -1 debug1: key_load_public: No such file or directory debug1: identity file C:\\Users\\LiBai/.ssh/id_dsa type -one debug1: key_load_public: No such file or directory debug1: identity file C:\\Users\\LiBai/.ssh/id_dsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file C:\\Users\\LiBai/.ssh/id_ecdsa type -1 debug1: key_load_public: No such file or directory debug1: identity file C:\\Users\\LiBai/.ssh/id_ecdsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file C:\\Users\\LiBai/.ssh/id_ed25519 type -1 debug1: key_load_public: No such file or directory debug1: identity file C:\\Users\\LiBai/.ssh/id_ed25519-cert type -ane debug1: key_load_public: No such file or directory debug1: identity file C:\\Users\\LiBai/.ssh/id_xmss blazon -one debug1: key_load_public: No such file or directory debug1: identity file C:\\Users\\LiBai/.ssh/id_xmss-cert blazon -1 debug1: Local version string SSH-ii.0-OpenSSH_for_Windows_7.7 debug1: Remote protocol version 2.0, remote software version OpenSSH_for_Windows_7.7 debug1: match: OpenSSH_for_Windows_7.vii pat OpenSSH* compat 0x04000000 debug1: Authenticating to 127.0.0.1:23 as 'LiBai' debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: algorithm: curve25519-sha256 debug1: kex: host primal algorithm: ecdsa-sha2-nistp256 debug1: kex: server->client nada: chacha20-poly1305@openssh.com MAC: <implicit> compression: none debug1: kex: client->server cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none debug1: expecting SSH2_MSG_KEX_ECDH_REPLY debug1: Server host key: ecdsa-sha2-nistp256 SHA256:IYiYLWzCLvUfmuyrg9HZ3cVnAroABOBWX5vMbsU0o2Y debug1: checking without port identifier debug1: Host '127.0.0.1' is known and matches the ECDSA host cardinal. debug1: Found key in C:\\Users\\LiBai/.ssh/known_hosts:3 debug1: found matching fundamental due west/out port debug1: rekey subsequently 134217728 blocks debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: rekey after 134217728 blocks debug1: pubkey_prepare: ssh_get_authentication_socket: No such file or directory debug1: SSH2_MSG_EXT_INFO received debug1: kex_input_ext_info: server-sig-algs=<ssh-ed25519,ssh-rsa,rsa-sha2-256,rsa-sha2-512,ssh-dss,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521> debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that tin can go on: publickey,password,keyboard-interactive debug1: Next authentication method: publickey debug1: Trying private key: C:\\Users\\LiBai/.ssh/id_rsa debug1: Trying private key: C:\\Users\\LiBai/.ssh/id_dsa debug1: Trying private central: C:\\Users\\LiBai/.ssh/id_ecdsa debug1: Trying individual central: C:\\Users\\LiBai/.ssh/id_ed25519 debug1: Trying private key: C:\\Users\\LiBai/.ssh/id_xmss debug1: Next authentication method: keyboard-interactive debug1: Authentications that can continue: publickey,password,keyboard-interactive debug1: Next authentication method: password debug1: read_passphrase: tin't open up /dev/tty: No such file or directory LiBai@127.0.0.1's password: debug1: Authentications that can proceed: publickey,countersign,keyboard-interactive Permission denied, delight endeavour again. debug1: read_passphrase: tin't open up /dev/tty: No such file or directory LiBai@127.0.0.1's password: debug1: Authentications that tin can continue: publickey,countersign,keyboard-interactive Permission denied, please try again. debug1: read_passphrase: can't open up /dev/tty: No such file or directory LiBai@127.0.0.i'south password: debug1: Authentications that can continue: publickey,password,keyboard-interactive debug1: No more than authentication methods to try. LiBai@127.0.0.1: Permission denied (publickey,password,keyboard-interactive). PS C:\Windows\system32> Non-Administrator Mode PowerShell
Server Side:
trounce PS C:\Users\LiBai> sshd.exe -d debug1: sshd version OpenSSH_for_Windows_7.7, LibreSSL 2.vi.5 debug1: key_load_private: Permission denied debug1: key_load_public: Permission denied Could not load host key: __PROGRAMDATA__\\ssh/ssh_host_rsa_key debug1: key_load_private: Permission denied debug1: key_load_public: Permission denied Could not load host key: __PROGRAMDATA__\\ssh/ssh_host_ecdsa_key debug1: key_load_private: Permission denied debug1: key_load_public: Permission denied Could non load host fundamental: __PROGRAMDATA__\\ssh/ssh_host_ed25519_key sshd: no hostkeys bachelor -- exiting. PS C:\Users\LiBai> Customer Side
shell PS C:\Users\LiBai> ssh.exe -five -p 23 LiBai@127.0.0.ane OpenSSH_for_Windows_7.7p1, LibreSSL 2.vi.five debug1: Connecting to 127.0.0.one [127.0.0.1] port 23. debug1: Connection established. debug1: key_load_public: No such file or directory debug1: identity file C:\\Users\\LiBai/.ssh/id_rsa type -one debug1: key_load_public: No such file or directory debug1: identity file C:\\Users\\LiBai/.ssh/id_rsa-cert type -one debug1: key_load_public: No such file or directory debug1: identity file C:\\Users\\LiBai/.ssh/id_dsa type -1 debug1: key_load_public: No such file or directory debug1: identity file C:\\Users\\LiBai/.ssh/id_dsa-cert type -ane debug1: key_load_public: No such file or directory debug1: identity file C:\\Users\\LiBai/.ssh/id_ecdsa type -1 debug1: key_load_public: No such file or directory debug1: identity file C:\\Users\\LiBai/.ssh/id_ecdsa-cert blazon -i debug1: key_load_public: No such file or directory debug1: identity file C:\\Users\\LiBai/.ssh/id_ed25519 blazon -one debug1: key_load_public: No such file or directory debug1: identity file C:\\Users\\LiBai/.ssh/id_ed25519-cert blazon -1 debug1: key_load_public: No such file or directory debug1: identity file C:\\Users\\LiBai/.ssh/id_xmss blazon -1 debug1: key_load_public: No such file or directory debug1: identity file C:\\Users\\LiBai/.ssh/id_xmss-cert type -i debug1: Local version string SSH-two.0-OpenSSH_for_Windows_7.7 debug1: Remote protocol version two.0, remote software version OpenSSH_for_Windows_7.7 debug1: match: OpenSSH_for_Windows_7.7 pat OpenSSH* compat 0x04000000 debug1: Authenticating to 127.0.0.1:23 as 'LiBai' debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: algorithm: curve25519-sha256 debug1: kex: host key algorithm: ecdsa-sha2-nistp256 debug1: kex: server->client zilch: chacha20-poly1305@openssh.com MAC: <implicit> compression: none debug1: kex: client->server cipher: chacha20-poly1305@openssh.com MAC: <implicit> pinch: none debug1: expecting SSH2_MSG_KEX_ECDH_REPLY debug1: Server host key: ecdsa-sha2-nistp256 SHA256:IYiYLWzCLvUfmuyrg9HZ3cVnAroABOBWX5vMbsU0o2Y debug1: checking without port identifier debug1: Host '127.0.0.1' is known and matches the ECDSA host key. debug1: Found cardinal in C:\\Users\\LiBai/.ssh/known_hosts:3 debug1: found matching fundamental w/out port debug1: rekey afterwards 134217728 blocks debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: rekey later 134217728 blocks debug1: pubkey_prepare: ssh_get_authentication_socket: No such file or directory debug1: SSH2_MSG_EXT_INFO received debug1: kex_input_ext_info: server-sig-algs=<ssh-ed25519,ssh-rsa,rsa-sha2-256,rsa-sha2-512,ssh-dss,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521> debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,password,keyboard-interactive debug1: Adjacent authentication method: publickey debug1: Trying private key: C:\\Users\\LiBai/.ssh/id_rsa debug1: Trying private fundamental: C:\\Users\\LiBai/.ssh/id_dsa debug1: Trying individual key: C:\\Users\\LiBai/.ssh/id_ecdsa debug1: Trying private key: C:\\Users\\LiBai/.ssh/id_ed25519 debug1: Trying individual primal: C:\\Users\\LiBai/.ssh/id_xmss debug1: Next authentication method: keyboard-interactive debug1: Authentications that can continue: publickey,password,keyboard-interactive debug1: Next hallmark method: password debug1: read_passphrase: tin't open /dev/tty: No such file or directory LiBai@127.0.0.i's countersign: debug1: Authentications that can proceed: publickey,countersign,keyboard-interactive Permission denied, delight endeavour again. debug1: read_passphrase: tin't open /dev/tty: No such file or directory LiBai@127.0.0.1's password: debug1: Authentications that can proceed: publickey,password,keyboard-interactive Permission denied, please effort over again. debug1: read_passphrase: can't open /dev/tty: No such file or directory LiBai@127.0.0.one's countersign: debug1: Authentications that can continue: publickey,password,keyboard-interactive debug1: No more authentication methods to effort. LiBai@127.0.0.1: Permission denied (publickey,password,keyboard-interactive). PS C:\Users\LiBai> Hi @LiBai-8545,
Cheers for the detailed logs. So a few things to endeavour.
-
On the client try
ssh -five -p 23 LiBai@127.0.0.1
You lot don't need to exist in that directory nor do you need the ssh.exe. Secondly please ensure 127.0.0.1 is the valid IP address of the server automobile and is accessible from the customer.
-
If yous withal tin can't get it to work subsequently verifying above, it appears your having an issue with the authentication. This guide here shows how to setup a Windows SSH Server and connect to it with Linux. You should focus on the first half of the guide by ensuring you take the right firewall rules in windows firewall (step eleven) and read access. If yous get this far and are even so having issues, I'm confident it is a firewall or other authentication issue. Please let me know how this goes, I'd like to come across you resolve this. :)
0 Votes 0 ·
Hello @LiBai-8545 , just following upwards again as I haven't heard if this helped you resolve your event. Permit me know where your at.
0 Votes 0 ·
Cheers for your help. But I cannot notice the sshd service in the Services Window......
0 Votes 0 ·
Aforementioned problem. In my case I'm a college professor and I had my students fix sshd in society back up an upcoming assignment where they demand to examine the effect of setting file ACL permissions in one PowerShell window while setting them in another. About half of the students were successful. This is ane of the issues that occurred in the other one-half. The students are all at a level past the Windows x 1709 release running PowerShell seven and their NetworkCategory is set to Private.
I stopped the sshd server to that I could run sshd manually as the traffic was not going to the other daemon.
stop-service sshd
sshd -d
Also not sure where the config files would go in Windows. There'south the hidden .ssh directory under $Dwelling house in each user's account - it currently only has one file known_hosts. And so there'southward the \Windows\System32\Drivers\etc directory but this doesn't have (now) an ssh subdirectory.
0 Votes 0 ·
Ensure you lot ready static IP address and ensure /etc/ssh/sshd_config file:
To enable password hallmark, uncomment
PasswordAuthentication aye
To enable root login, uncomment
PermitRootLogin yes
To enable SSH cardinal login, uncomment
PubkeyAuthentication yep
AuthorizedKeysFile .ssh/authorized_keys
Thanks very much for your assistance. I have uncommented the PasswordAuthentication yes and PermitRootLogin yes. Because I don't use the key to log in, I didn't uncomment the key-related commands. Then I restart the PC, The mistake bulletin remained the same...
BTW, I also cannot find the sshd service in the Services Window......
Are at that place whatever other settings that need to be done after installing the OpenSSH Server and Client software?
0 Votes 0 ·
OpenSSH SSH Server
0 Votes 0 ·
I am too having this event at present where I cannot SSH into my win 10 automobile from my VM (virtual box) RHEL eight.5 server, but I can SSH from my win10 into the RHEL server...
[SH_Admin@Homme-Network-Security-Server bin]$ ssh -p 22 inspiropectus7@192.168.i.157 -vT
OpenSSH_8.0p1, OpenSSL one.1.1k FIPS 25 Mar 2021
debug1: Reading configuration information /etc/ssh/ssh_config
debug1: Reading configuration data /etc/ssh/ssh_config.d/05-redhat.conf
debug1: Reading configuration data /etc/crypto-policies/back-ends/openssh.config
debug1: configuration requests final Match pass
debug1: re-parsing configuration
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Reading configuration data /etc/ssh/ssh_config.d/05-redhat.conf
debug1: Reading configuration data /etc/crypto-policies/back-ends/openssh.config
debug1: Connecting to 192.168.i.157 [192.168.1.157] port 22.
debug1: Connection established.
debug1: identity file /home/SH_Admin/.ssh/id_rsa type 0
debug1: identity file /home/SH_Admin/.ssh/id_rsa-cert blazon -one
debug1: identity file /domicile/SH_Admin/.ssh/id_dsa type -1
debug1: identity file /home/SH_Admin/.ssh/id_dsa-cert type -1
debug1: identity file /home/SH_Admin/.ssh/id_ecdsa type 2
debug1: identity file /home/SH_Admin/.ssh/id_ecdsa-cert blazon -1
debug1: identity file /home/SH_Admin/.ssh/id_ed25519 blazon -1
debug1: identity file /dwelling/SH_Admin/.ssh/id_ed25519-cert type -i
debug1: identity file /habitation/SH_Admin/.ssh/id_xmss type -i
debug1: identity file /home/SH_Admin/.ssh/id_xmss-cert type -1
debug1: Local version cord SSH-two.0-OpenSSH_8.0
debug1: Remote protocol version ii.0, remote software version OpenSSH_for_Windows_8.1
debug1: match: OpenSSH_for_Windows_8.ane pat OpenSSH* compat 0x04000000
debug1: Authenticating to 192.168.1.157:22 equally 'inspiropectus7'
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: curve25519-sha256
debug1: kex: host key algorithm: ecdsa-sha2-nistp256
debug1: kex: server->client null: aes256-gcm@openssh.com MAC: <implicit> pinch: none
debug1: kex: client->server zilch: aes256-gcm@openssh.com MAC: <implicit> compression: none
debug1: kex: curve25519-sha256 need=32 dh_need=32
debug1: kex: curve25519-sha256 need=32 dh_need=32
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ecdsa-sha2-nistp256 SHA256:<Fundamental is nowadays>
debug1: Host '192.168.i.157' is known and matches the ECDSA host key.
debug1: Found cardinal in /home/SH_Admin/.ssh/known_hosts:1
debug1: rekey out after 4294967296 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: rekey in after 4294967296 blocks
debug1: Will attempt fundamental: /home/SH_Admin/.ssh/id_rsa RSA SHA256:<Key is present> agent
debug1: Will endeavor key: /home/SH_Admin/.ssh/id_ecdsa ECDSA SHA256:<Key is present> agent
debug1: Will effort central: /home/SH_Admin/.ssh/id_dsa
debug1: Will effort key: /abode/SH_Admin/.ssh/id_ed25519
debug1: Will attempt key: /dwelling/SH_Admin/.ssh/id_xmss
debug1: SSH2_MSG_EXT_INFO received
debug1: kex_input_ext_info: server-sig-algs=<ssh-ed25519,ssh-rsa,rsa-sha2-256,rsa-sha2-512,ssh-dss,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521>
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that tin can continue: publickey,countersign,keyboard-interactive
debug1: Adjacent authentication method: publickey
debug1: Offer public central: /home/SH_Admin/.ssh/id_rsa RSA SHA256:<Key is present> amanuensis
debug1: Authentications that tin proceed: publickey,countersign,keyboard-interactive
debug1: Offering public key: /dwelling/SH_Admin/.ssh/id_ecdsa ECDSA SHA256:<Central is nowadays> agent
debug1: Authentications that can keep: publickey,password,keyboard-interactive
debug1: Trying individual key: /home/SH_Admin/.ssh/id_dsa
debug1: Trying private key: /domicile/SH_Admin/.ssh/id_ed25519
debug1: Trying private primal: /abode/SH_Admin/.ssh/id_xmss
debug1: Side by side authentication method: keyboard-interactive
debug1: Authentications that tin continue: publickey,countersign,keyboard-interactive
debug1: Next authentication method: password
(Please notation I replaced the areas where there are key representation with "<Key is nowadays>"
Later on that I endeavor to cosign with my countersign from the Win10 machine and I go the error:
inspiropectus7@192.168.ane.157's countersign:
debug1: Authentications that can proceed: publickey,password,keyboard-interactive
Permission denied, please try again.
inspiropectus7@192.168.1.157's password:
debug1: Authentications that can continue: publickey,countersign,keyboard-interactive
Permission denied, please try again.
inspiropectus7@192.168.1.157's password:
Received disconnect from 192.168.1.157 port 22:2: As well many hallmark failures
Disconnected from 192.168.1.157 port 22
I have the same result. Spending a lot of time installing and configure the OpenSSH server on Windows ten and tried to access information technology via MacOs OpenSSH customer, merely cipher was resolved. All these problems with Windows 10, simply Linux and MacOs OpenSSH servers are running without any problems. Why this problem ?
Source: https://docs.microsoft.com/answers/questions/109609/unable-to-access-the-win10-pc-with-openssh-install.html
Hi @LiBai-8545 , thanks for the question.
Can y'all provide debug logs from the OpenSSH Server on the Windows 10 PC? For more on logging see hither.
0 Votes 0 ·
Hi @LiBai-8545 ,
I'thousand just following upwardly. Are you able to provide debug logs from your OpenSSH Server so nosotros tin drill downward further into the issue?
0 Votes 0 ·
Thank you very much for the quick respond. I accept tried the way you lot offered to me. There are two dissimilar outputs in the PowerShell: One is the non-administrator fashion and the other is the administrator style.
Ambassador Mode
Server Side:
0 Votes 0 ·
I am sorry the debug data is besides long. And the reply box is express past chiliad words. I volition post the complete debug data in the respond box.
0 Votes 0 ·
I was also having the same issue,
afterwards I blindly copied a control from a blog mail,
and executed information technology
New-ItemProperty -Path "HKLM:\SOFTWARE\OpenSSH" -Name DefaultShell -Value "C:\Program Files\PowerShell\7\pwsh.exe" -PropertyType String -Forcescratched my head for more than 10 hours,
then I did debug run of sshd with this control on Windows ten host:
sshd -dand tried to connect from my Linux machine as usual:
ssh james@192.168.1.123I saw this line in my Windows debug prompt:
User james non immune because beat c:\\program files\\powershell\\7\\pwsh.exe does not existso I executed this command again with modified path to Powershell 7 executable,
New-ItemProperty -Path "HKLM:\SOFTWARE\OpenSSH" -Name DefaultShell -Value "C:\Program Files\WindowsApps\Microsoft.PowerShell_7.2.1.0_x64__8wekyb3d8bbwe\pwsh.exe" -PropertyType String -Forcefulnessand it fixed my problem
0 Votes 0 ·