Allow use of SecureCRT as handler for telnet, ssh
Ok, I got it to work.
Thanks
What I found out was that the Other parameters already sends /ssh2 and /l and /password, all I needed was %PARENT_HOST%.
Allow use of SecureCRT as handler for telnet, ssh
Thats the problem, we have over 500 devices. Does this still require the sessions to exist on the clients PC? Rather than pushing the information to SecureCRT (Like Putty)?
Allow use of SecureCRT as handler for telnet, ssh
Is there a walk-through. I get it to launch, but that's about it.
I'm using it with Sub-connections.
edited by schavez@cvtc.org on 6/12/2015
Allow use of SecureCRT as handler for telnet, ssh
Does this work now? I'm having the same issue with my team also. We have a few guys who will not use RDM unless it works with SecureCRT.
Launches SecureCRT with the SSH or Telnet.
Also does this support command inputs, like credentials?