Telnet bug

Hello,

What type of Telnet session have you created? Is it Telnet or Telnet (Rebex)?

Could you also post some screenshots of the issue or a small video. This should help with the troubleshooting.

Best regards,

Hi Jeff,

I assume it's a regular Telnet session. It has been created using the network scan import. I can't find an option anywhere to create a Telnet (Rebex) session.

Please find the video attached to see the problem being recreated.

Thank you for all of the information, we'll take a look at the issue. If PuTTY is able to properly do this, we should be able to too :)

If we need more information we'll post on this thread.

Regards,

Could you tell us if your entry's username and password are filled out or are they empty so that you can type them in yourself?

We've assigned Denis to work on this issue by the way.

Regards,

Hi Hubert,
thank you for the update. The username and password field for the entry are empty.

Hello,

I ran some tests and normally, when the user name is empty, the telnet terminal should proceed with interactive login just like putty. Just to be safe, you could check that the user name field is indeed empty, without invisible characters like spaces or tabs.

If you're familiar with WireShark, you could send me the exchange up until the user name prompt is displayed, that would be of great help to me. Otherwise, I can add some diagnosis logging to help pinpoint the problem.

Regards,

Hi,

I looked to add diagnosis logging to telnet. As it turns out, the telnet terminal already supports a pretty good set of verbose logging (it's a surprise to me, I never noticed it was there in the code I integrated).

So you can just turn on "verbose" in the telnet entry and send me the resulting logs. That would be very helpful.

Regards,

Hi Denis,
here is the log for the Telnet session (IP address commented out for obvious reasons) :


[21-12-2017 9:55:35] Looking up host "x.x.x.x"
[21-12-2017 9:55:35] Connecting to x.x.x.x port 23
[21-12-2017 9:55:35] client: WILL NAWS
[21-12-2017 9:55:35] client: WILL TSPEED
[21-12-2017 9:55:35] client: WILL TTYPE
[21-12-2017 9:55:35] client: WILL NEW_ENVIRON
[21-12-2017 9:55:35] client: DO ECHO
[21-12-2017 9:55:35] client: WILL SGA
[21-12-2017 9:55:35] client: DO SGA
[21-12-2017 9:55:35] server: DO TTYPE
[21-12-2017 9:55:35] server: WILL ECHO
[21-12-2017 9:55:35] server: DO NAWS
[21-12-2017 9:55:35] client: SB NAWS 126,40
[21-12-2017 9:55:35] server: DONT TSPEED
[21-12-2017 9:55:35] server: DONT NEW_ENVIRON
[21-12-2017 9:55:35] client: WILL OLD_ENVIRON
[21-12-2017 9:55:35] server: DO SGA
[21-12-2017 9:55:35] server: WILL SGA
[21-12-2017 9:55:35] server: DONT OLD_ENVIRON

Hi,

I made some changes, here is a DLL for you to try. Just replace the DLL with the same name with this one. The path should be something like:

C:\Program Files (x86)\Devolutions\Remote Desktop Manager\x86
and
C:\Program Files (x86)\Devolutions\Remote Desktop Manager\x64

I provided you with both 32 and 64 bits versions. But you can replace only one DLL depending on the version you use.

Regards,

Hi Denis,


do the DLL files need to be registered or is replacing the files and restarting the application sufficient? Because thus far the problem remains the same. I've also tried recreating the session but to no avail.

No registration needed, just replacing and restarting. It looks like the fix I made didn't work for you. Could you send me the logs so I can see if anything changed? I guess I will have to search a little more to fix this problem.

Regards,

Hi Denis,


hereby the log as requested:
[23-12-2017 12:24:11] Looking up host "x.x.x.x"
[23-12-2017 12:24:11] Connecting to x.x.x.x port 23
[23-12-2017 12:24:11] client: WILL NAWS
[23-12-2017 12:24:11] client: WILL TSPEED
[23-12-2017 12:24:11] client: DO ECHO
[23-12-2017 12:24:11] client: WILL SGA
[23-12-2017 12:24:11] client: DO SGA
[23-12-2017 12:24:11] server: DO TTYPE
[23-12-2017 12:24:11] client: WILL TTYPE
[23-12-2017 12:24:11] server: WILL ECHO
[23-12-2017 12:24:11] server: DO NAWS
[23-12-2017 12:24:11] client: SB NAWS 126,35
[23-12-2017 12:24:11] server: DONT TSPEED
[23-12-2017 12:24:11] server: DO SGA
[23-12-2017 12:24:11] server: WILL SGA

Hi Support, Best Wishes to all of you,


are there any updates regarding the Telnet issue we're experiencing?

Hi,

I am currently working on this. I started yesterday, but debugging a problem I can not reproduce in my environment is always trickier. I should come up with a solution to try in a few days. Or at least a test you could perform to give me more clues.

Best wishes to you.

Hi,

Here is another DLL for you to try. I made a small change and I doubt it will make any difference. But I also included a special detailed logging to help me diagnose the problem. Make sure to send me logs up to that mystery "q".

Thanks for your help.

Hi Denis,
thank you for the update. Here is the new output from the log.
[4-1-2018 17:26:47] Looking up host "x.x.x.x"
[4-1-2018 17:26:47] Connecting to x.x.x.x port 23
[4-1-2018 17:26:47] FF,FD,18,
[4-1-2018 17:26:47] server: DO TTYPE
[4-1-2018 17:26:47] client: WILL TTYPE
[4-1-2018 17:26:47] client: DO ECHO
[4-1-2018 17:26:47] client: WILL SGA
[4-1-2018 17:26:47] client: DO SGA
[4-1-2018 17:26:47] FF,FB,01,1B,5B,32,4A,1B,5B,3F,37,6C,1B,5B,33,3B,32,33,72,1B,5B,3F,36,6C,1B,5B,31,3B,31,48,1B,5B,3F,32,35,6C,1B,5B,31,3B,31,48,50,72,6F,43,75,72,76,65,20,4A,39,30,38,38,41,20,53,77,69,74,63,68,20,32,36,31,30,2D,34,38,0D,0A,0D,53,6F,66,74,77,61,72,65,20,72,65,76,69,73,69,6F,6E,20,52,2E,31,31,2E,31,30,37,0D,0A,0D,0D,0A,0D,43,6F,70,79,72,69,67,68,74,20,28,43,29,20,31,39,39,31,2D,32,30,31,33,20,48,65,77,6C,65,74,74,2D,50,61,63,6B,61,72,64,20,43,6F,2E,20,20,41,6C,6C,20,52,69,67,68,74,73,20,52,65,73,65,72,76,65,64,2E,0A,0D,0A,0D,20,20,20,20,20,20,20,20,20,20,20,20,20,20,20,20,20,20,20,20,20,20,20,20,20,20,20,52,45,53,54,52,49,43,54,45,44,20,52,49,47,48,54,53,20,4C,45,47,45,4E,44,0A,0D,0A,0D,20,55,73,65,2C,20,64,75,70,6C,69,63,61,74,69,6F,6E,2C,20,6F,72,20,64,69,73,63,6C,6F,73,75,72,65,20,62,79,20,74,68,65,20,47,6F,76,65,72,6E,6D,65,6E,74,20,69,73,20,73,75,62,6A,65,63,74,20,74,6F,20,72,65,73,74,72,69,63,74,69,6F,6E,73,0A,0D,20,61,73,20,73,65,74,20,66,6F,72,74,68,20,69,6E,20,73,75,62,64,69,76,69,73,69,6F,6E,20,28,62,29,20,28,33,29,20,28,69,69,29,20,6F,66,20,74,68,65,20,52,69,67,68,74,73,20,69,6E,20,54,65,63,68,6E,69,63,61,6C,20,44,61,74,61,20,61,6E,64,0A,0D,20,43,6F,6D,70,75,74,65,72,20,53,6F,66,74,77,61,72,65,20,63,6C,61,75,73,65,20,61,74,20,35,32,2E,32,32,37,2D,37,30,31,33,2E,0A,0D,0A,0D,20,20,20,20,20,20,20,20,20,48,45,57,4C,45,54,54,2D,50,41,43,4B,41,52,44,20,43,4F,4D,50,41,4E,59,2C,20,33,30,30,30,20,48,61,6E,6F,76,65,72,20,53,74,2E,2C,20,50,61,6C,6F,20,41,6C,74,6F,2C,20,43,41,20,39,34,33,30,33,0A,0D,0A,0D,57,65,27,64,20,6C,69,6B,65,20,74,6F,20,6B,65,65,70,20,79,6F,75,20,75,70,20,74,6F,20,64,61,74,65,20,61,62,6F,75,74,3A,0A,0D,20,20,2A,20,53,6F,66,74,77,61,72,65,20,66,65,61,74,75,72,65,20,75,70,64,61,74,65,73,0A,0D,20,20,2A,20,4E,65,77,20,70,72,6F,64,75,63,74,20,61,6E,6E,6F,75,6E,63,65,6D,65,6E,74,73,0A,0D,20,20,2A,20,53,70,65,63,69,61,6C,20,65,76,65,6E,74,73,0A,0D,0A,0D,50,6C,65,61,73,65,20,72,65,67,69,73,74,65,72,20,79,6F,75,72,20,70,72,6F,64,75,63,74,73,20,6E,6F,77,20,61,74,3A,20,20,77,77,77,2E,50,72,6F,43,75,72,76,65,2E,63,6F,6D,0A,0D,0A,0D,0A,0D,1B,5B,32,34,3B,31,48,50,72,65,73,73,20,61,6E,79,20,6B,65,79,20,74,6F,20,63,6F,6E,74,69,6E,75,65,1B,5B,31,3B,31,48,1B,5B,3F,32,35,68,1B,5B,32,34,3B,32,37,48,FF,FD,03,
[4-1-2018 17:26:47] server: WILL ECHO
[4-1-2018 17:26:47] server: DO SGA
[4-1-2018 17:26:48] FF,FB,03,
[4-1-2018 17:26:48] server: WILL SGA
[4-1-2018 17:26:49] 1B,5B,32,4A,1B,5B,3F,37,6C,1B,5B,33,3B,32,33,72,1B,5B,3F,36,6C,1B,5B,32,34,3B,32,37,48,1B,5B,3F,32,35,68,1B,5B,32,34,3B,32,37,48,1B,5B,3F,36,6C,1B,5B,31,3B,32,34,72,1B,5B,3F,37,6C,1B,5B,32,4A,1B,5B,32,34,3B,32,37,48,1B,5B,31,3B,32,34,72,1B,5B,32,34,3B,32,37,48,
[4-1-2018 17:26:50] 1B,5B,32,34,3B,31,48,55,73,65,72,6E,61,6D,65,3A,20,1B,5B,3F,32,35,68,1B,5B,32,34,3B,31,48,1B,5B,3F,32,35,68,1B,5B,32,34,3B,31,31,48,1B,5B,32,34,3B,31,31,48,1B,5B,3F,32,35,68,1B,5B,32,34,3B,31,31,48,1B,5B,32,34,3B,31,31,48,71,1B,5B,3F,32,35,68,1B,5B,32,34,3B,31,32,48,
[4-1-2018 17:26:51] 1B,5B,32,34,3B,31,31,48,20,1B,5B,3F,32,35,68,1B,5B,32,34,3B,31,31,48,1B,5B,32,34,3B,31,31,48,71,1B,5B,3F,32,35,68,1B,5B,32,34,3B,31,32,48,
[4-1-2018 17:26:53] 1B,5B,32,34,3B,31,31,48,20,1B,5B,3F,32,35,68,1B,5B,32,34,3B,31,31,48,1B,5B,32,34,3B,31,31,48,71,1B,5B,3F,32,35,68,1B,5B,32,34,3B,31,32,48,
[4-1-2018 17:26:55] 1B,5B,32,34,3B,31,31,48,20,1B,5B,3F,32,35,68,1B,5B,32,34,3B,31,31,48,1B,5B,32,34,3B,31,31,48,71,1B,5B,3F,32,35,68,1B,5B,32,34,3B,31,32,48,
[4-1-2018 17:26:57] 1B,5B,32,34,3B,31,31,48,20,1B,5B,3F,32,35,68,1B,5B,32,34,3B,31,31,48,1B,5B,32,34,3B,31,31,48,71,1B,5B,3F,32,35,68,1B,5B,32,34,3B,31,32,48,


On a side note what strikes me as strange as well is the normally you need to a press a key before you can continue to the username and password prompt (it's a HP switch) however this quickly disappears without any keyboard input and afterwards you get prompted the Username: with the mystery 'q'.


Maybe there's another keystroke which we are missing.

Hello,

Sorry for jumping into this conversation.

I just have some question to try to help with this issue.

Have you tried to manually create a new Telnet entry to see if it is not a problem with the Network scan?

Is it possible to export an entry that has the issue and send it to me in a private message? Please remove all sensitive information before sending it.

Best regards,

Hi Erica,


thank you for your answer. I've sent you a PM with the requested information.


Kind regards,
Jeroen

Hello,

Thank you for the sessions and the information. The properties of both entries didn't includes any wrong configuration.

Have you this issue only with Remote Desktop Manager? Maybe a silly question, have you tried with another Telnet client software?

Best regards,

Hello,

I have the same issue with HP switch. We Use different model of HP switch.

By using putty client integration work without this "q" issue.

Hi,

I made a new DLL for you to try. It does not solve any issue but has more logging details. (I added logging of all client outputs, it's a little more invasive so that is why I did not include it in the previous DLL). Please, replace the DLLs and send me the logs (with the verbose option on). If I understood correctly, you do have some HP switch that does work, it would be nice to see those logs too!

Again, thanks for your help.

Denis Vincent

Hi Erica,
I've tried the creating the connection with a Putty client and if I use that on the same device it works without problems. So there has to be something in Remote Desktop Manager that's causing it.
Regards,
Jeroen

Hi Denis,
please find the logs below.
Switch that doesn't work:
[16-1-2018 9:08:44] Looking up host "x.x.x.x"
[16-1-2018 9:08:44] Connecting to x.x.x.x port 23
[16-1-2018 9:08:44] s:[FF][FD][18]
[16-1-2018 9:08:44] server: DO TTYPE
[16-1-2018 9:08:44] c:[FF][FB][18]
[16-1-2018 9:08:44] client: WILL TTYPE
[16-1-2018 9:08:44] c:[FF][FD][01]
[16-1-2018 9:08:44] client: DO ECHO
[16-1-2018 9:08:44] c:[FF][FB][03]
[16-1-2018 9:08:44] client: WILL SGA
[16-1-2018 9:08:44] c:[FF][FD][03]
[16-1-2018 9:08:44] client: DO SGA
[16-1-2018 9:08:44] s:[FF][FB][01][1B][2J[1B][?7l[1B][3;23r[1B][?6l[1B][1;1H[1B][?25l[1B][1;1HProCurve J9088A Switch 2610-48[0D][0A][0D]Software revision R.11.107[0D][0A][0D][0D][0A][0D]Copyright (C) 1991-2013 Hewlett-Packard Co. All Rights Reserved.[0A][0D][0A][0D] RESTRICTED RIGHTS LEGEND[0A][0D][0A][0D] Use, duplication, or disclosure by the Government is subject to restrictions[0A][0D] as set forth in subdivision (b) (3) (ii) of the Rights in Technical Data and[0A][0D] Computer Software clause at 52.227-7013.[0A][0D][0A][0D] HEWLETT-PACKARD COMPANY, 3000 Hanover St., Palo Alto, CA 94303[0A][0D][0A][0D]We'd like to keep you up to date about:[0A][0D] * Software feature updates[0A][0D] * New product announcements[0A][0D] * Special events[0A][0D][0A][0D]Please register your products now at: [url=http://www.ProCurve.com[0A][0D][0A][0D][0A][0D][1B][24;1HPress]www.ProCurve.com[0A][0D][0A][0D][0A][0D][1B][24;1HPress[/url] any key to continue[1B][1;1H[1B][?25h[1B][24;27H
[16-1-2018 9:08:44] server: WILL ECHO
[16-1-2018 9:08:44] s:[FF][FD][03]
[16-1-2018 9:08:44] server: DO SGA
[16-1-2018 9:08:44] s:[FF][FB][03]
[16-1-2018 9:08:44] server: WILL SGA
[16-1-2018 9:08:45] c:[FF][F1]
[16-1-2018 9:08:46] c:[FF][F1]
[16-1-2018 9:08:46] s:[1B][2J[1B][?7l[1B][3;23r[1B][?6l[1B][24;27H[1B][?25h[1B][24;27H[1B][?6l[1B][1;24r[1B][?7l[1B][2J[1B][24;27H[1B][1;24r[1B][24;27H
[16-1-2018 9:08:46] s:[1B][24;1HUsername: [1B][?25h[1B][24;1H[1B][?25h[1B][24;11H[1B][24;11H[1B][?25h[1B][24;11H[1B][24;11Hq[1B][?25h[1B][24;12H
[16-1-2018 9:08:47] c:[FF][F1]
[16-1-2018 9:08:48] c:[FF][F1]
[16-1-2018 9:08:48] s:[1B][24;11H [1B][?25h[1B][24;11H[1B][24;11Hq[1B][?25h[1B][24;12H
[16-1-2018 9:08:49] c:[FF][F1]
[16-1-2018 9:08:50] c:[FF][F1]
[16-1-2018 9:08:50] s:[1B][24;11H [1B][?25h[1B][24;11H[1B][24;11Hq[1B][?25h[1B][24;12H

And the log from the switch that does work fine:
[16-1-2018 9:28:31] Looking up host "x.x.x.x"
[16-1-2018 9:28:31] Connecting to x.x.x.x port 23
[16-1-2018 9:28:32] s:[FF][FD][18][FF][FB][01][1B][2J[1B][?7l[1B][3;23r[1B][?6l[1B][1;1H[1B][?25l[1B][1;1HProCurve J9021A Switch 2810-24G[0D][0A][0D]Software revision N.11.76[0D][0A][0D][0D][0A][0D]Copyright (C) 1991-2017 Hewlett-Packard Co. All Rights Reserved.[0A][0D][0A][0D] RESTRICTED RIGHTS LEGEND[0A][0D][0A][0D] Use, duplication, or disc
[16-1-2018 9:28:32] server: DO TTYPE
[16-1-2018 9:28:32] c:[FF][FB][18]
[16-1-2018 9:28:32] client: WILL TTYPE
[16-1-2018 9:28:32] c:[FF][FD][01]
[16-1-2018 9:28:32] client: DO ECHO
[16-1-2018 9:28:32] c:[FF][FB][03]
[16-1-2018 9:28:32] client: WILL SGA
[16-1-2018 9:28:32] c:[FF][FD][03]
[16-1-2018 9:28:32] client: DO SGA
[16-1-2018 9:28:32] server: WILL ECHO
[16-1-2018 9:28:32] s:losure by the Government is subject to restrictions[0A][0D] as set forth in subdivision (b) (3) (ii) of the Rights in Technical Data and[0A][0D] Computer Software clause at 52.227-7013.[0A][0D][0A][0D] HEWLETT-PACKARD COMPANY, 3000 Hanover St., Palo Alto, CA 94303[0A][0D][0A][0D]We'd like to keep you up to date about:[0A][0D] * Software feature updates[0A][0D] * New product announcements[0A][0D] * Special events[0A][0D][0A][0D]Please register your products now at: [url=http://www.ProCurve.com[0A][0D][0A][0D][0A][0D][1B][24;1HPress]www.ProCurve.com[0A][0D][0A][0D][0A][0D][1B][24;1HPress[/url] any key to continue[1B][1;1H[1B][?25h[1B][24;27H
[16-1-2018 9:28:32] s:[FF][FD][03]
[16-1-2018 9:28:32] server: DO SGA
[16-1-2018 9:28:32] s:[FF][FB][03]
[16-1-2018 9:28:32] server: WILL SGA
[16-1-2018 9:28:33] c:[FF][F1]
[16-1-2018 9:28:34] c:[FF][F1]
[16-1-2018 9:28:35] c:[FF][F1]
[16-1-2018 9:28:36] c:[FF][F1]
[16-1-2018 9:28:37] c:[FF][F1]
[16-1-2018 9:28:38] c:[FF][F1]
[16-1-2018 9:28:39] c:[FF][F1]
[16-1-2018 9:28:40] c:[FF][F1]
[16-1-2018 9:28:41] c:[FF][F1]
[16-1-2018 9:28:42] c:[FF][F1]
[16-1-2018 9:28:43] c:[FF][F1]
[16-1-2018 9:28:44] c:[FF][F1]
[16-1-2018 9:28:45] c:[FF][F1]
[16-1-2018 9:28:46] c:[FF][F1]
[16-1-2018 9:28:47] c:[FF][F1]

I've noticed though that with the new DLL files Remote Desktop Manager stops responding when I close a Telnet session so I'll be reverting back to the old ones now that you have the required information.


Kind regards,
Jeroen

I think this will resolve the login problem. For the closing freeze, I will check my latest changes on the SSH side, there is probably an unforeseen link. Keep in mind this is a quick fix, if it works, I will come up with an official solution which will be available in a future official version (we update frequently).

Regards,

Hi Denis,
thanks! This does indeed fix the login problem. These DLL files however still contain the issue that if you close an open Telnet Session using the tab (either Right-click -> Close or pressing the 'x') that the entire Remote Desktop Manager application locks up. If you log off from the switch properly by using the telnet session it works fine.
Kind regards,
Jeroen

Hi Denis,
I tried working with some SSH session yesterday and noticed that closing an SSH session the same way as described above with the Telnet session locks up the application as well.
Could you please look in to this?


Thank you in advance.
Jeroen

Hi,

We already encountered this problem and found a solution. The fix will be available with the next version of RDM. A beta version might be available today or tomorrow, which will include this fix.

Regards