PowerShell / PowerShell/Win32-OpenSSH
Domain login doesn't work on Windows 11
Open
Nobody has claimed this yet.
Waiting on Author
- Dominant language
- No language data
- Stars
- 8.3k
- Forks
- 819
- PR merge metrics
- No merged PRs in 30d
Description
Prerequisites
- Write a descriptive title.
- Make sure you are able to repro it on the latest version
- Search the existing issues.
Steps to reproduce
- Enable OpenSSH server on a Windows 11 machine (
$COMPUTER) jointed to an Active Directory domain ($DOMAIN). - Give
$COMPUTERall permissions on the$DOMAIN\$USERuser. - On a client,
ssh $DOMAIN\$USER@$COMPUTER. This happens with both$DOMAIN\$USERand$USER@$DOMAIN.COM. - Type
$USER's password.
Expected behavior
I get a shell on `$COMPUTER` as `$USER` because the password was correct.
Actual behavior
The client shows `Permission denied (publickey,password,keyboard-interactive).`
Error details
The client shows: `$USER@$DOMAIN@$COMPUTER: Permission denied (publickey,password,keyboard-interactive).`
`$COMPUTER`'s event viewer shows the following event:
An account failed to log on.
Subject:
Security ID: SYSTEM
Account Name: $COMPUTER$
Account Domain: $DOMAIN
Logon ID: 0x3E7
Logon Type: 8
Account For Which Logon Failed:
Security ID: NULL SID
Account Name: NOUSER
Account Domain: $COMPUTER
Failure Information:
Failure Reason: Unknown user name or bad password.
Status: 0xC000006D
Sub Status: 0xC0000064
Process Information:
Caller Process ID: 0x6f70
Caller Process Name: C:\Windows\System32\OpenSSH\sshd.exe
Network Information:
Workstation Name: $COMPUTER
Source Network Address: -
Source Port: -
Detailed Authentication Information:
Logon Process: Advapi
Authentication Package: Negotiate
Transited Services: -
Package Name (NTLM only): -
Key Length: 0
### Environment data
```PowerShell
Name Value
---- -----
PSVersion 7.3.8
PSEdition Core
GitCommitId 7.3.8
OS Microsoft Windows 10.0.22621
Platform Win32NT
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
WSManStackVersion 3.0
Version
OpenSSH_for_Windows_8.6p1
Visuals
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure with OpenSSH_for_Windows 8.6p1 on a Windows 11 machine joined to Active Directory, using both documented username formats. Compare the client error with the OpenSSH server event showing the failed Negotiate authentication. Done means a domain user's password login establishes a shell on the target computer.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, networking, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100