OpenSSH Server (Windows 11) : client_loop: send disconnect: Connection reset

Well, Based on the reply i found here, here i won't be able to connect to microsoft account linked windows host with ease. But since my device is in AD setting, i was able to ssh login to windows host with password authentication. But when i try to login with key (added the public key to the .ssh\authorized_keys and enabled PubKeyAuthentication in sshd_config, and also added the firewall inbound rule for ssh in the host), I get this message client_loop: send disconnect: Connection reset and i also got the debug log with ssh -i private_key username@ip -vvv and the output was debug1: Server accepts key: .\\id_conn RSA SHA256:tkeAQw+mF5mye3IKVQkMF190Rkqe/HQ9K1pPkUO4ang explicit debug3: sign_and_send_pubkey: using publickey-hostbound-v00@openssh.com with RSA SHA256:tkeAQw+mF5mye3IKVQkMF190Rkqe/HQ9K1pPkUO4ang debug3: sign_and_send_pubkey: signing using rsa-sha2-512 SHA256:tkeAQw+mF5mye3IKVQkMF190Rkqe/HQ9K1pPkUO4ang debug3: send packet: type 50 debug3: receive packet: type 52 Authenticated to 192.168.1.184 ([192.168.1.184]:22) using "publickey". debug1: channel 0: new session [client-session] (inactive timeout: 0) debug3: ssh_session2_open: channel_new: 0 debug2: channel 0: send open debug3: send packet: type 90 debug1: Requesting no-more-sessions@openssh.com debug3: send packet: type 80 debug1: Entering interactive session. debug1: pledge: filesystem debug3: client_repledge: enter debug1: ENABLE_VIRTUAL_TERMINAL_INPUT is supported. Reading the VTSequence from console debug3: This windows OS supports conpty debug1: ENABLE_VIRTUAL_TERMINAL_PROCESSING is supported. Console supports the ansi parsing debug3: Successfully set console output code page from:65001 to 65001 debug3: Successfully set console input code page from:437 to 65001 debug3: recv - from CB ERROR:10054, io:000002519BD65E30 debug3: send packet: type 1 debug3: send - WSASend() ERROR:10054, io:000002519BD65E30 client_loop: send disconnect: Connection reset So, I can't login with the key. (but the catch is when i ran the sshd in debug mode with sshd -d in the host, i was able to login with key as well). Yelp....

Feb 20, 2025 - 13:22

OpenSSH Server (Windows 11) : client_loop: send disconnect: Connection reset

Well, Based on the reply i found here,

i won't be able to connect to microsoft account linked windows host with ease. But since my device is in AD setting, i was able to ssh login to windows host with password authentication.

But when i try to login with key (added the public key to the .ssh\authorized_keys and enabled PubKeyAuthentication in sshd_config, and also added the firewall inbound rule for ssh in the host), I get this message
client_loop: send disconnect: Connection reset

and i also got the debug log with
ssh -i private_key username@ip -vvv

and the output was
debug1: Server accepts key: .\\id_conn RSA SHA256:tkeAQw+mF5mye3IKVQkMF190Rkqe/HQ9K1pPkUO4ang explicit debug3: sign_and_send_pubkey: using publickey-hostbound-v00@openssh.com with RSA SHA256:tkeAQw+mF5mye3IKVQkMF190Rkqe/HQ9K1pPkUO4ang debug3: sign_and_send_pubkey: signing using rsa-sha2-512 SHA256:tkeAQw+mF5mye3IKVQkMF190Rkqe/HQ9K1pPkUO4ang debug3: send packet: type 50 debug3: receive packet: type 52 Authenticated to 192.168.1.184 ([192.168.1.184]:22) using "publickey". debug1: channel 0: new session [client-session] (inactive timeout: 0) debug3: ssh_session2_open: channel_new: 0 debug2: channel 0: send open debug3: send packet: type 90 debug1: Requesting no-more-sessions@openssh.com debug3: send packet: type 80 debug1: Entering interactive session. debug1: pledge: filesystem debug3: client_repledge: enter debug1: ENABLE_VIRTUAL_TERMINAL_INPUT is supported. Reading the VTSequence from console debug3: This windows OS supports conpty debug1: ENABLE_VIRTUAL_TERMINAL_PROCESSING is supported. Console supports the ansi parsing debug3: Successfully set console output code page from:65001 to 65001 debug3: Successfully set console input code page from:437 to 65001 debug3: recv - from CB ERROR:10054, io:000002519BD65E30 debug3: send packet: type 1 debug3: send - WSASend() ERROR:10054, io:000002519BD65E30 client_loop: send disconnect: Connection reset

So, I can't login with the key. (but the catch is when i ran the sshd in debug mode with sshd -d in the host, i was able to login with key as well).

Yelp....