-
Notifications
You must be signed in to change notification settings - Fork 767
Troubleshooting Steps
manojampalam edited this page May 16, 2016
·
17 revisions
If sshd cannot start
- Check that sshd_config is in place
- Check that host keys are generated
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
- MSI Install Instructions
- Script Install Instructions
- Alternative installation using the universal installer
- Retrieving download links for the latest packages