Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
SSH Switch Connection
#1
We are in the process of testing the 2016 Remote-Desktop product.  My question is, how do you configure the app, or is it possible, to manage Cisco switch or VMware hosts from a terminal session?  I did a brief search on SSH and Cisco but it did not produce anything of value.   

Thanks ahead
Reply
#2
Hi...thanks for yur question !
If you need an ssh terminal session then you have the option to use putty or poderosa to manage the terminal session. You can configure putty settings right out of the "SSH connection". Furthermore you can save the local putty settings to registry or write them back local. For VMware you can use a special role on a connection node to conenct to a Vmware host directly.
Hope that helps !?

Best regards,
Michael
best regards,
Michael -- michael.scholz@asg.com --
Reply
#3
(22-08-2016, 11:21 AM)Michael Scholz Wrote: Hi...thanks for yur question !
If you need an ssh terminal session then you have the option to use putty or poderosa to manage the terminal session. You can configure putty settings right out of the "SSH connection". Furthermore you can save the local putty settings to registry or write them back local. For VMware you can use a special role on a connection node to conenct to a Vmware host directly.
Hope that helps !?

Best regards,
Michael

Michael,

Thanks for the reply.  We have tried several times to get an SSH connection working but have had no luck.  We've upgraded Putty and manually created the settings and tried pulling them in to the registry as well - no luck.  We get a prompt like it is trying to log us in to something but it errors with the following message - "Connection failed: The SSH Server Connection wa not found. The requested name is valid, but no data of the requested type was found".  Any idea what could be causing this?  Thanks ahead.
Reply
#4
Strange. But you cant upgrade the putty version that will be used by ASG-RD because it's a special version. I think its based on version 0.66. But if you use a slightly different local version it's settings should be usable by the integrated putty. Have you tried to create the session with putty alone ? Does that work ? Because researching the web your failure message sounds like a common error message with putty/winscp that points to DNS problems and the internal putty should work like the external one...the differnence is only that is handled by ASG-RD...
best regards,
Michael -- michael.scholz@asg.com --
Reply
#5
(22-08-2016, 03:54 PM)Michael Scholz Wrote: Strange. But you cant upgrade the putty version that will be used by ASG-RD because it's a special version. I think its based on version 0.66. But if you use a slightly different local version it's settings should be usable by the integrated putty. Have you tried to create the session with putty alone ? Does that work ? Because researching the web your failure message sounds like a common error message with putty/winscp that points to DNS problems and the internal putty should work like the external one...the differnence is only that is handled by ASG-RD...

Michael,

We figured out what it was.  The connection was not configured correctly inside the product.  It is working like a charm now.  Thank you for your quick response to my issue.

Bill
Reply
#6
Thanks for your feedback bill ! Glad it works now ;-)

(22-08-2016, 07:43 PM)wam6187 Wrote: ...

Michael,

We figured out what it was.  The connection was not configured correctly inside the product.  It is working like a charm now.  Thank you for your quick response to my issue.

Bill
best regards,
Michael -- michael.scholz@asg.com --
Reply




Users browsing this thread: 1 Guest(s)