trodke

Thanks for the quick response and fix!

Thank you for the quick response and fix!

Thanks!

Remote Desktop Manager Enterprise Edition

Version 12.5.4.0

I have the File, Options, Types, SSH/Telnet (Rebex) Auto register SSH fingerprint option enabled. However, when making a connection, I still get prompted to register the fingerprint.

I added this session via Edit, New Entry, Entry --> Session --> SSH Shell. Note that it's not the "Putty --> Putty" session type, or the "Putty --> SSH Shell (Rebex)" session type.

I know there is an "Always accept fingerprint" available in this session type (General --> Advanced; that option does suppress the prompt), but due to the current quantity of connections that we are building, plus future maintenance, not having to select this option each time is ideal.

Thanks!

Thank you for the crazy fast response!

this screen shot shows the resulting connection names where the ampersand in the parent folder name is rendered as $amp in the connection name

this screen shot shows a connection that is named with a "Group variable" referencing the parent folder name: $COMPUTER_NAME$

this screen shot shows a "Device" parent folder named with an ampersand ( & ) in the name.

If a parent folder is named with an ampersand, such as "A&B" (without the quotes), then the Group NAME$ variable (such as $COMPUTER_NAME$) is used in the name of a connection in that folder, the resulting variable entry is named "A&ampB".

It looks like the "&" in a group name is being converted to the HTML character reference for an ampersand, which is "&amp".

It would look like this in the Navigation Pane:

Example 1:

A&B <--parent folder

A&ampB <--connection named "COMPUTER_NAME$" (without the quotes)

Example 2:

Dun&Bradstreet <--parent folder

Dun&ampBradstreet <--connection named "COMPUTER_NAME$" (without the quotes)

I am running 1.5.50 and my coworker is running 1.5.64. Mine hangs and his does the prompt for credentials thing.

We have updated all of our managed firewalls to ASDM 9.1(3).

I would say that it's definitely hung. It will sit there as long as I let it sit.

edited by trodke on 7/22/2013

I believe that I have exhaustively tested those two options, but will certainly test again with specifics if you like.

For further testing, I have installed the local ASDM client on my PC, and everything appears to function fine, but the Cisco ASDM-IDM Launcher window hangs indefinitely after RDM hits the OK button. There is also no data being moved by the javaws.exe process in Task Manager.

Thanks!

Thank you for the quick reply!

I just tested some more and it works fine on ASDM version 7.1(3).

It does not work on ASDM 6.4(5) or 6.4(7). So I upgraded one of those two firewalls to ASDM 7.1(3) and it works fine now.

I am assuming that this is motivation to get it together, and get all of my firewalls updated!

Thank you for your time and consideration!

Howdy!

I stumbled across the new Cisco ASA add-on this morning. Considering that my team manages about five dozen firewalls, this will be a huge time saver! Another great bit of software from Devolutions.

I was able to configure the add-on quickly, and am in the process of converting over all of my Cisco ASA connections from a web page link to this new add-on.

Everything is working perfectly, except when the add-on presses OK the first time, it contacts the ASA, which rejects the credentials, then prompts again for the credentials. I can this cancel the credential reprompt, then get an error dialog box that says Unable to lunch device manager.

So I figure that I've entered the credentials wrong. I went back and retyped them and it worked fine. But it kept failing when using RDM. I then discovered that if I just cancel the credential reprompt and the error dialog box, I can just hit OK again using the same credentials that RDM entered, and it works fine.

To test further, I changed the login title, so that RDM never enters the credentials, and also leave the credentials blank, I then fill them in manually, and it still will not work the first time.

I can launch the same web page by going to the web URL: http://ipaddress and click the link to run the Java Web Start ASDM, and the credentials will take the first time.

I don't know how to describe it, but it appears somehow that opening the ASDM Java Web Start via RDM or via a web page is somehow slightly different. I'm totally thrown for a loop that I can just tell the same ASDM-IDM window to submit thsame credentials the seconds time and it works like a champ.

Help!

Thanh