PowerShell / PowerShell/Win32-OpenSSH
Unable to connect to an OpenSSH server via a corp domain user
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
OpenSSH_for_Windows_7.7p1
Server OperatingSystem
Windows Server 2019 Datacenter
Client OperatingSystem
Windows Server 2019 Datacenter
What is failing
OpenSSH won't connect using a corporate AD user
Expected output
prompt on remote server
Actual output
Connection reset by 10.8.7.55 port 22
Local user, everything works fine:
ssh -l localwinuser vwazurevm.server.local
Are you sure you want to continue connecting (yes/no)? yes
localwinuser@vwazurevm.server.local C:\Users\localwinuser>
Only AD users can't connect:
ssh -l CORPDOMAIN\corpaduser vwazurevm.server.local
Connection reset by 10.8.7.55 port 22
ssh -l corpaduser@corporate.com vwazurevm.server.local
Connection reset by 10.8.7.55 port 22
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 two corporate AD login commands against the Windows Server 2019 host and compare them with the working local-user command. Check the OpenSSH server configuration and relevant authentication logs to narrow down why AD sessions are reset. Done means an AD user reaches the expected remote prompt without breaking local-user access.
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
- Mostly clear
- Newbie friendliness
- 25/100