NT SERVICE\SSHD Logon Failure when starting SSHD service #964
Comments
|
If I start the process via command line it works. But in this case the process runs under my user. |
|
Even I have the same issue. Is there some config that we can set to accept network username/pwd login? |
|
when I run sshd.exe SSH connection works fine. But I could see a command prompt being opened on the server machine for each putty session. Is it expected? |
|
Please share the sshd.log (DEBUG3 enabled) when sshd failed to start as service. |
|
@chanducrr I assume you are using Basic authentication. If so it is expected. @leotxcosta @chanducrr can you try reinstalling sshd? (just run install-sshd.ps1 in installation folder). |
|
@leotxcosta windows 2008 is equivalent to vista SP1. Note that vista and below is out of scope for our project. |
|
@manojampalam I tried reinstalling but basic authentication doesn't work . Here is the DEBUG3 log Windows PowerShell PS C:\Windows\system32> cd 'C:\Program Files\OpenSSH' Mode LastWriteTime Length Name d----- 11/15/2017 10:22 PM logs PS C:\Program Files\OpenSSH> .\install-sshd.ps1 |
|
@bagajjal @manojampalam @bingbing8 We are trying this on Windows Server 2012 R2 |
|
@bagajjal @manojampalam @bingbing8 Here is the success case log when run sshd PS C:\Program Files\OpenSSH> .\sshd.exe -ddd debug2: input_userauth_request: setting up authctxt for XYZORG\adminuser debug2: channel 0: read<=0 rfd 8 len 0 Connection closed by 12.34.56.78 port 52184 |
|
In Win Server 2012 R2 I didn't have this problem. |
|
I don't think you can get this working, they specifically state Windows 7 (Windows Server 2008 R2) and above is supported and Windows Server 2008 is before this edition as per @bingbing8. I tried playing around with this very briefly to see if it was just a software limit but the |
|
@jborean93 @manojampalam @bagajjal @bingbing8 I couldn't make it work windows server 2012 R2. Do you have any updates from the logs I've shared?. May be it is related to this error? 88700 01:38:10:276 debug3: NetUserGetInfo() failed with error: 1722 for user: adminuser and domain: XYZORG \n |
|
Hi everyone! Sorry I haven't post this one sooner. This is happening in all versions of Windows (Windows 10) and Windows Servers too.
The workaround I've been using for some time is to change the log On to: Local System Account with "Allow service to interact with desktop". Then, the service will start without any issues.
I have blog about this and forgot to open an incident. :) |
|
By the way, for some reason, when executing the command: Is not giving any errors nor notification that the service didn't start. :) |
|
@MaximoTrinidad - Most likely its related to the host key file permissions.
|
|
Awesome! That did it. I'll be fixing my blog post. Greatly Appreciated, |
|
This issue is no longer applicable with the latest changes requiring SSHD to run as SYSTEM |
|
@mamojampalam while the service runs without any issues and is listening on the port, it seems like there are still issues with Server 2008. I know it isn’t supported but I didn’t want to give people false hope saying the latest release works on this version. |
|
Sure. this thread has too many conversations mixed in one. If someone has an issue on Server 2008, feel free to create a new issue with detailed symptoms. Happy to take a quick look and provide a work around if any. |
OpenSSH for Windows" version
0.0.23.0
Server OperatingSystem
Windows Server 2008 Standard
What is failing
When I try to start SSHD service I got a logon failure message. Checking event viewer, there is a log with the error "The sshd service was unable to log on as NT SERVICE\SSHD with the currently configured password due to the following error:
Logon failure: unknown user name or bad password."
Expected output
Service starting successfully.
Actual output
Service not starting.
The text was updated successfully, but these errors were encountered: