Hello, I am still having issues with Putty sessions not connecting. They connect fine using the Putty directly in the program folder, but when I connect within ASG Remote Desktop I get the error:
Connection Failed. The negotiation of encryption algorithm is failed.
I have checked and the enable compression is NOT checked. I put in this error on a previous post. The support person basically told me "I can't reproduce it on my server, so I can't help you.", which was not helpful at all. Please note that I DID have a previous version where these did work, and it was when the product was VisionApp. I have tried to remove all VisionApp settings from the registry, as well as all ASG settings, removed the program, removed Putty, and then re-installed everything. This did not work, either.
I would be happy to have someone work with me remotely, and I will even set up a WebEx to do so. I really need to get this working again, as remoting into the Linux servers is a part of my job, and it is frustrating me that I purchased this software and cannot use it as needed.
ASGRD is only calling Putty from application folder and set some parameters for the destination and the credentials - do you use the same session when trying with ASGRD and Putty standalone?
(17-06-2019, 02:24 PM)DevOma Wrote: ASGRD is only calling Putty from application folder and set some parameters for the destination and the credentials - do you use the same session when trying with ASGRD and Putty standalone?
Yes. It is the same session. Putty standalone works just fine, but within ASGRD it gives the error.
Perhaps any special characters? Is it working if you are using a Putty-Session without assigned credentials? I think there was a problem using space in password - but it is some years ago and I can't remember exactly...
No special characters, no spaces. Same error with or without assigned credentials. When I google this specific error, it has to do with compression protocols not matching what Putty is expecting. But, since Putty works fine by itself, I have to assume that ASGRD is starting the connection with a compression parameter set, perhaps within a .dll.
As I stated previously, I had a previous version from back when it was Visionapp installed on may machine, and they worked with that version. When I installed the ASG version, that is when they stopped working. So, this leads me to believe that it is either a setting in the registry, or a problem in a .dll.
Oh, and the Visionapp version will no longer work, either. I tried to uninstall all versions and go back to that one as well.
You are not calling Putty.exe from ASGRD-Installation-Folder - so perhaps you have an older Putty-Version on your computer installed? I don't know, perhaps that's the difference? We asked so many times if you are using Putty.exe from ASGRD-Installation-Folder...
(01-07-2019, 02:44 PM)DevOma Wrote: You are not calling Putty.exe from ASGRD-Installation-Folder - so perhaps you have an older Putty-Version on your computer installed? I don't know, perhaps that's the difference? We asked so many times if you are using Putty.exe from ASGRD-Installation-Folder...
I have attached screenshots of calling Putty from the ASG-RD installation folder, just to satisfy you that indeed the same thing happens when I use Putty from there.
Putty WORKS from the command line, NOT from within the application, therefore, the problem HAS to be in how the application is calling Putty. This could be a .DLL or Registry setting, I do not know what is causing this issue, but it is only happening WITHIN the app.
Ok last idea and perhaps difference - I can see that you are calling Putty "in cmd.exe executed as Administrator" - do you also start ASGRD "As Administrator"? Because ASGRD is starting the Putty process in the same way as it was started before…
And if you press in SSH-Configuration of a connection the Configure button - Putty will be started also - could you enter the same connection there again? Also not working? Or is that working?
It doesn't matter whether I start ASGRD as administrator or not, I get the same results.
If I press SSH-Configuration, set up a new connection or use an existing one, click configuration, which opens Putty session configuration, and then press connect from the Putty dialogue, it works.
The only time it does not work is clicking the session to start from the navigation screen for a saved session. I have also repeatedly removed ALL Putty ssh sessions and manually recreated them. At every step of the way, Putty works, up until launching from the navigator/saved/configured sessions.
IO would be more than happy to set up a webex and have you see exactly what my computer is doing, we can blow away everything and set things up from scratch, etc.
Hi,
all settings I have seen so far seems ok - only one thing is unclear and there could be a point of failure so just to make that clear: if you go to the ssh connection properties and choose "configure" then putty opens and you have to choose the desired session and then "load" that session. It's not choosen automatically by pressing "configure". ASG-RD will use all putty settings defined in a putty session except settings that have been made in the ASG-RD Gui like "Destination" - IP adress , Credentials and Port as the most important ones. If those settings in the GUI are made they will overwrite putty session settings ! So here is the point where a difference between the saved session definition from putty-only to those used with ASG-RD could occur. So if your putty session works then make sure a) to load the right session while configuring and b) don't overwrite settings throug ASG-RD GUI settings. In your case just use the "Destination" ip adress for the connection, use the Credentials if wanted and define the SSH "session" without anything else - no port. That should give the same results as standalone. That would be the things I would check. No need to blow things away.. if the putty session is working then everything else should work. If you are sure you did all that and want me take a look then I'm ok with that. Just send me a private mail and we have to find a time. Best regards,
Michael
best regards,
Michael -- michael.scholz@asg.com --
Yes, I would like to have you take a look. I have done everything that you have said in the last post. I agree with you that ' if the putty session is working then everything else should work". But, the Putty sessions work in everything except the ASG program interface.
