PowerShell / PowerShell/Win32-OpenSSH

Connection error - "sshd: Failed password for user"

Open
#1,552 18 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
8.3k
Forks
819
PR merge metrics
No merged PRs in 30d

Description

"OpenSSH for Windows" version
8.1.0.0

Server OperatingSystem
Windows Server 2016 Standard

What is failing
SSH connection still fails everytime

Expected output
User is connected via ssh.

Actual output
All services are up and running. It is a domain joined server. I have a domain admin account and a local admin account outside the domain.
Server with SSHD process is answering for SSH remote requests to this server and i get a logon prompt. Typing valid username and password i´ll get the message "Access denied". Not matter if i use a local admin account or a domain admin account. In the logs I see the error message
sshd: Failed password for av** from 10.XXX.XXX.XXX port 57685 ssh2

I know the the user is working and password is correct i am typing.
The user also have access and all needed permissions to the needed files.

I also see this line when i use the debug mode.
debug1: get_passwd: LookupAccountName() failed: 1332.

But i don´t know where i have to configure or setup something like this.
I found that this error code looks like this system error code
ERROR_NONE_MAPPED
1332 (0x534)
No mapping between account names and security IDs was done.
https://docs.microsoft.com/en-us/windows/win32/debug/system-error-codes--1300-1699-

But all fixes for this code also won´t work for me.
I am searching now for several hours in different forums, but nothing helped for me.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file or test is identified. Start by reproducing the Windows Server 2016 authentication failure in debug mode and tracing the reported LookupAccountName() failure with ERROR_NONE_MAPPED; done means a valid local or domain account can complete SSH login.

Written by the indexing model from the issue text.

Assessment

Domain
authentication, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.