Telnet sessions cause application crash

Hi,
I will assign this to our dev and he will get back to you quickly

Regards

Hi,
I'm working on this bug, but I'm unable to reproduce it for now. Could it be that you get crashes for anonymous connections? e.g. without user name and password? Also, what kind of device do you have this problem with?

Regards

Trying to access two Cisco switches (3750s in one case, and 2960 in another). Both switches are accessable on a private IP address (192.168 in one case, and 172.16 in the other). I can access them fine using Putty, but using RDM crashes the program. Just for troubleshooting I tried to connect to one of our routers (also Cisco), which resulted in the same crash of RDM.
Putty opens the expected 'Access is prohibited' welcome screen and the prompt asking for the username, like RDM used to do. RDM now however briefly shows the docked black background, never tosses up the 'Access is prohinited' notice, and just reports that RDM is no longer responding (hence killing the program off).
All I've done with regards to settings for the connection is add the IP address it should connect to under the machine, with the standard port. Password and username are grayed out, but that's not an issue. I prefer to fill out the username and password manually once it's connected. So yes, it crashes on anonymous connections, but with the Free version I have you don't get the option of saving username and password in any case, so I can't test that.

Thank you for the info. I finally got to reproduce the bug connecting without user name. I made a correction and here is the DLL. You just need to copy the unzipped DLL over: C:\Program Files (x86)\Devolutions\Remote Desktop Manager Free\x86\DevolutionsTerminalNative.dll
Let us know if it fixed your problem. If so, it will be part of our next release.

Thank you.


DLL is where? No link in your post :)

Sorry, it seems drag and drop does not work to attach a file... Here is the DLL.

And that one gives me this on download (just send you a private mail with my e-mail which may help here :)):
404 - File or directory not found.The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable.

Got it through e-mail. Closed the program. Renamed the old DevolutionsTerminalNative.dll to DevolutionsTerminalNative.old
Copied the new one next to it.
Started the program and tried this.
Pleased to report that it looks like your change solved the issue :) Tks :)

Excellent! Thank you for your feedback and your help.

Hi Denis,

I am not getting anything in the zip file. Are you able to send me a copy to my email.

Thanks

New version is out (3.0.15.0).
Minor mishap creeped in on Telnet sessions... My free version is now asking for a username upon starting a Telnet session, despite there not being a username filled in (or a requirement for) on the session.
No matter what I fill in here, or if I cancel the prompt... I still get the basic login prompt of the device, so I can login there. It's just an extra screen that pops up when it's not needed. Filling in the username on that screen also does nothing for the provided screen by the device. If I fill my username in there, the device is not asking for the password, but will once again ask for the username.

http://i68.photobucket.com/albums/i7/Neko1308/Tijdelijk/RDMTelnet_zpsakspinqm.png

Hello,

Thank you for the feedback. We were able to reproduce the issue in our environment and will work on a fix. It should be an easy one, we'll update this topic once the change has been made internally.

Regards,

The fix has been made and it will be available in the next version of RDM.

Regards,

Awesome :)

I am still getting the SSH error. I have upgraded to 3.0.16.0 and this did not correct the problem.

@mchange, what error do you get exactly? Could you verify if you have the prerequisite installed?

Regards

"An unknown SSH error was encountered.

No error"

What do you mean prerequisite? I have been using RDM for about 2 years now. I just did the upgrade when the program opened up.

I will ask Hubert and Denis to check with you.

Regards

3.0.16.0 installed here. No issues anymore with telnet sessions that I can see. No password prompt popping up, and just showing the CLI. Just as wanted :)
If I try to connect to an SSH session a password prompt is shown (GUI prompt), but anything I fill in there (or nothing) results in the SSH screen to be closed. No connection is made, no error is shown.
Not sure if this is a separate bug (if it is one) or not.

@mchance: We're currently investigating this issue, we'll keep you updated.

@Jurriaan: The password prompt opens when the terminal is unable to connect with the specified settings and might require a password. What authentication method are you using, password or private key?

I'd expect the connection to just show a logon prompt allowing me the username and password combo on the CLI.
It's worked before when I made the connection, but on a test today (as a result of the SSH comment above) I found it didn't anymore.
SSH Shell connection - Username and password are set as empty (grayed out, so can't fill those in either). All other settings are default.
There is no personal key, nor any location provided for one.
If I grab Putty, just fill in the IP address of the device, and use SSH (port 22), I get a CLI asking me for 'Login as: '. RDM gives me a GUI question for the password with NO request for the username. RDM does so on multiple devices on the network that are reachable with Putty under SSH. Cancelling this password GUI prompt closes the entire window for that session.

@Jurriann: If the username and password field are greyed out, are you using a credential entry with the entry? The fields shouldn't be greyed out unless that's the case.


@mchance: I talked with Denis and we would need more logs to figure the issue out. You can enable them in that part of the SSH Shell entry:



You can then send it to me through private message.

Regards,

Hello,

Thanks to mchance's logs we have identified the "no error" issue and we've fixed it internally. The change will be available in the next version of RDM. If you want to try the change out right away I attached to this post a zip containing the DLLs with the fix. You need to replace the DevolutionsTerminalNative.dll files in your RDM installation folder (in the x86 and x64 folders) by the ones attached to this post.

Regards,

This worked great. Thanks.

I've made some screenshots regarding the session-setup of the SSH that I've got here that pops up tis screen when connecting:



I'd expect something akin to this:



The connection has worked in the past, with the following setup:








No real setting regarding credentials that I can see... Unless I'm missing something?


I've also changed out the provided DevolutionsTerminalNative.dll you gave out last, but the problem remains as-is.

I think I understand what happens. Since you set the credentials to "none", the terminal is unable to login and will ask for credentials. This is why you see the "password" prompt. The issue here is that it doesn't also ask for a username even if it requires one. We'll fix this for the next version of RDM free and enterprise, it will prompt when the username is required too for SSH Shell, SSH Tunnel and Portforward entries.

Unfortunately though, it's not possible to have the prompt be inside the terminal like PuTTY. Both the username and password prompts will be separate, one after the other. If you want to enter both the username and password at the same time it has to be done before the connection by using the "Open (prompt for credentials)" button in the dashboard or the right click menu:


I hope this helps.

Regards,

That last one works. It logs in and provides me a prompt. It is a change from how RDM used to behave tho.

This is because in 12.0.8.0 we were still using our old implementation of the terminal, while in the latest beta versions we have migrated to our new implementation. This new implementation allows us more flexibility and an easier time adding new features and fixing bugs. Sorry for the inconvenience.

Regards,

Guess that explains it then. Good to know. While there is a 'Always request credentials' tick under the connection, I guess the free version grays that out. Oh well. Not that I have to connect to SSH connections that regularly.