From 134c5947aef2b6191b159ab3288802075f24bf97 Mon Sep 17 00:00:00 2001 From: manojampalam Date: Sun, 15 May 2016 23:48:54 -0700 Subject: [PATCH] Created Troubleshooting Steps (markdown) --- Troubleshooting-Steps.md | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 Troubleshooting-Steps.md diff --git a/Troubleshooting-Steps.md b/Troubleshooting-Steps.md new file mode 100644 index 0000000..99775b0 --- /dev/null +++ b/Troubleshooting-Steps.md @@ -0,0 +1,18 @@ +Trouble shooting steps for typical connection issues: +- Server side - run sshd in debug mode + * `net stop sshd` + * In an elevated admin console - `sshd.exe -d` + * This will dump debug logs real time on console +- Client side - start ssh.exe in verbose mode + * `ssh.exe -v ...` + * This will dump verbose logs on console + +Trouble shooting more complex issues: +- Server side + * stop sshd and ssh-agent services + * delete sshd.log and ssh-agent.log (can be found in the sshd.exe directory) + * set LogLevel to DEBUG (or DEBUG2/DEBUG3 for higher levels of logging) in sshd_config + * run the scenario. sshd.log and ssh-agent.log will contain sshd and ssh-agent related traces respectively +- Client side + * set LogLevel to DEBUG (or DEBUG2/DEBUG3 for higher levels of logging) in ssh_config + * Run ssh.exe in verbose mode as detailed above