![putty ssh session putty ssh session](https://docs.bytemark.co.uk/wp-content/uploads/2018/04/putty-connection-details.png)
You will now end up with a bunch of unique log files for the various putty sessions and you’re building your own great putty-reference-database in the log directory specified. Already saved sessions will not be affected by this setting, you have to change these sessions separately. Will now log its output to a (new) logfile. The next step is save this new log settings to the Default Settings profile in putty the Default Settings profile contains your….uh…Default Settings :).
![putty ssh session putty ssh session](http://www.thetechfactors.com/wp-content/uploads/2016/02/Putty-session1.jpg)
It means every 60 seconds interval SSH client will send null packet to keep SSH session alive. Under Sending of null packets to keep session active, in the seconds between Keepalives, type 60. click on Category and click on connection as shown below. I am using some putty parameters which will make every session unique, in this case “&H-&Y&M&D-&T.log”, which means: Enter session details like Hostname or IP Address. Select all session output and specify a log file. This is pretty simple: open putty and go to Session->Logging. When you want putty to log all your session output, you have to change the default settings. In this way you always have a great reference/history available, which contains all previous commands and output of earlier telnet and SSH sessions. I think it’s a good idea to always log the telnet and SSH session output of every session to a file. Putty has the option to log telnet and SSH traffic session output to disk.
![putty ssh session putty ssh session](https://docs.digitalocean.com/screenshots/droplets/putty/auth-browse-highlighted.a30d15cce028591d8b3e6ebcc044fe4f4f9d0dcc3c4c9d7fd637761d03b127ad.png)
Putty is a simple but great tool for this purpose! But as I've previously said SSH works as I can connect from Nexus to 2960.Ĭonnectivity to 2960 from server is fine, as I can ping and the switch can also authenticate to TACACS server.I am using putty for telnet and SSH connections to ESXi hosts, switches and/or filers. I've Zeroized the RSA keys and generated new ones, I have tried different a modulus etc. While the blank screen is open I can see a connection to the switch SSH from Nexus 3k to Switch works fine, but when attempting SSH from the server to the 2960x Putty just hangs on a blank screen. I still have two switches that I am unable to connect to via SSH. This was solved (but not entirely clear why) by removing the unnecessary configuration of SVI's. I created a post recently with some issues with connected to switches via SSH.