PowerShell / PowerShell/Win32-OpenSSH
RPC_S_SERVER_UNAVAILABLE error when connection through Windows 2019 sshd
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 8.3k
- Forks
- 819
- PR merge metrics
- No merged PRs in 30d
Description
We are trying to use certreq.exe to issue SSL certificates. certreq.exe uses RPC against a Microsoft CA
Setup: Linux-Client -> Windows 2019 Server where we can execute certreq.exe (*)-> Microsoft CA Server
This works
- locally
- via RDP using cmd or powershell
- via scheduled task
This does not work if executed via sshd running on a Windows 2019 Server:
certreq -q -config "xyz" -attrib "xyz" -submit "xyz.csr"
Certificate Request Processor: The RPC server is unavailable. 0x800706ba (WIN32: 1722 RPC_S_SERVER_UNAVAILABLE)
There is no difference if this user has local admin privileges on (*) or not. The error message is always the same
Are there any documented limitations regarding RPC/EPM (Port 135) or is this a bug?
"OpenSSH for Windows" version
7.7.2.2
Server OperatingSystem
Windows Server 2019 Standard
Client OperatingSystem
SLES 12 SP5, OpenSSH 7.7p2
What is failing
RPC call is failing, see error message from certreq above
Expected output
No error output, succesful RPC
Actual output
The RPC server is unavailable. 0x800706ba (WIN32: 1722 RPC_S_SERVER_UNAVAILABLE)
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
The issue names no repository files or tests. Start by reproducing the certreq command through Windows OpenSSH and compare it with local, RDP, and scheduled-task execution; done means determining whether the RPC failure is a documented limitation or an actionable Win32-OpenSSH bug.
Written by the indexing model from the issue text.
Assessment
- Domain
- networking, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100