From 2de7c9754677d0fbc8633cfe475d4c5412aebfe2 Mon Sep 17 00:00:00 2001 From: Manoj Ampalam Date: Wed, 12 Sep 2018 10:41:23 -0700 Subject: [PATCH] Updated Troubleshooting Steps (markdown) --- Troubleshooting-Steps.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Troubleshooting-Steps.md b/Troubleshooting-Steps.md index d8fa91d..0d7837a 100644 --- a/Troubleshooting-Steps.md +++ b/Troubleshooting-Steps.md @@ -6,7 +6,7 @@ Troubleshooting steps for typical service startup and connection issues: * Server side: run `sshd` in debug mode * `Stop-Service sshd` (if sshd service is running) - * `sshd.exe -d` This will run sshd in interactive mode under currently logon user (typically as admin) + * `sshd.exe -d` This will run sshd in interactive mode under currently logged on user (typically as admin). Note that, in this mode, you can only login as the "currently logged on user" and only using "key based auth". To overcome these restrictions, you should instead run `psexec -s sshd.exe -d` to run sshd as SYSTEM. * This will dump debug logs in real time to stdout on the console * You can also add additional `d`s for more detailed loggin: * `sshd.exe -dd` or `sshd.exe -ddd`