Enable SSH Putty on Orion Node page
Apologies for the delay i was on holidays .:D .I have tested this with 2008 / windows 7 / Vista / 2003 and its working fine.
You mean there is not a "C:\System\PuTTY\putty.exe"? Then create one. or modify the path in the .reg file or to reflect the path to your copy of his putty .exe
Nice. Got it working on our server. Thanks Malik Haider for the information. Very helpful!
So, what does this do? Will it make the telnet links in orion into SSH links? or will it just handle SSH and Telnet with putty?
1. Setup the standard release of Putty
2. if you have a proxyhost configure your putty/pageant/puttygen for login using authorized_keys
3. create a new profile, e.g. 'telnet' with you proxyhost settings in it using this as the starting point: ssh ProxyCommand and PuTTY | Monkeys with Buttons
(if you can ssh from your desktop, then don't bother with the proxy configuration in this profile. A profile is useful for configuring things like keeping a logfile and other session properties)
4. use ftype to redirect the telnet URL:
ftype telnet="C:\Program Files (x86)\PuTTY\putty.exe" -load "telnet" -ssh %1
the -ssh forces the use of ssh even if the URL is telnet://
Thank you Richard!!
Now, i am able to implement the same but the issue is two of them (highlighted in yellow color) is not wokring.
1- ping tool and another is trace route
They will work when you will have SolarWinds Engineer's Toolset installed .
Network Engineer Tools - Engineer's Toolset | SolarWinds
ok Thankyou Malik for your response
Is reg edit file to be ran on Orion server or on end user machines? GoldTipu
end-user machines
You can also now use the web-based SSH feature we ship with in the newer versions.
Care to expand? What does that mean, there'll be no reg edits necessary on user machines to enable them to ssh straight to a box from a node details page? Cheers!
Is there any record (logs) in the Orion of these connections?
NO putty is outside Solarwinds
We are using the SolarWinds built in syslog server and we are sending all login success and login failures to the syslog server. Then on each node we are using the last XX syslog messages widget, limiting it to the last 15 messages from the past 12 months and filtering based on
Message Like '*login*' AND Message NOT Like '*user: OURSWADMINACCOUNT*'
That way we are only seeing the login messages and we are excluding the messages that are the Solarwinds environment logging into the switches to upload config templates (which are tracked by NCM) or downloading the latest config (NCM Jobs). But, allows us to focus on the success and failures of actual users logging into the switch. We are also doing command logging so that we can see what each putty session is doing.
