Telnet bug
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
Telnet bug
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
Telnet bug
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 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
Telnet bug
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,
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
Telnet bug
Hi Erica,
thank you for your answer. I've sent you a PM with the requested information.
Kind regards,
Jeroen
Telnet bug
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.
Telnet bug
Hi Support, Best Wishes to all of you,
are there any updates regarding the Telnet issue we're experiencing?
Telnet bug
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
Telnet bug
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.
Telnet bug
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
Network Scan Remote Sites not / partially working
So far I seem to be able to find everything with the ping set to 1000 but it's good to know that if I'll still miss out on a site with even higher response times that it can be upped to 4000.
Thank you very much for your help!
Network Scan Remote Sites not / partially working
I just upped to ping value to a 1000ms just to test it out and at the moment this is reporting back all the devices in the subnet.
I am however still somewhat surprised that the value needs to be this high while the ping responses are all under 300ms even with a continuous ping for an extended period of time.
Network Scan Remote Sites not / partially working
Hi Hubert,
thank you for your response. I've increased the ping to both 300ms and 500ms and checked the response times from the switches which are in between 100-150ms. While I'm getting more objects with the network scan I'm still not seeing every device which is in this subnet.
Network Scan Remote Sites not / partially working
I'm currently testing the Trial version of Remote Desktop Manager and generating a complete overview of our Network Infrastructure. Using the Network Scan tool to import switches and routers has been working great however we have several sites over the world which don't have the fastest connection.
I noticed that the Network Scan is having problems with picking up everything on these sites. It feels as if the 'Ping before scan' discards the scanned IP address if it didn't reply within a really fast response.
Is there to increase the delay of the ping before the Network Scan starts with the next IP address in the scope? I'd preferably not disable the Ping before scan because scanning an entire /24 takes a lot of time then.
Please see the attached screenshot for what the Network Scan found and some ping results of devices in that subnet which should have been picked up.
I've been able to retrieve the information I need by installing the Trial Version on a local machine on the subnet I wanted to scan but installing the entire software for a simply network scan is quite a cumbersome task if it's needed on a lot of remote sites.
Telnet bug
Hi Hubert,
thank you for the update. The username and password field for the entry are empty.
Telnet bug
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.
Telnet bug
Hi,
I've started using the Trial version of the Enterprise edition and so far I've been really impressed in everything this tool has to offer and how well the support forums are.
Unfortunately I haven't been able to resolve the next issue yet or find any related thread on the forums about this.
I've imported all the switches (mainly HP, some Juniper) from one of our locations using the Network scan option. However if I try to connect to any switch HP using Telnet (some don't support SSH) I first get the prompt to press 'Space' to continue and afterwards get prompted the username field. This is where it gets weird because without pressing anything after the space a 'q' gets filled in behind the "username:" prompt. If I try to delete it using backspace it will automatically reappear and if I add more characters they automatically get changed to a 'q' as well.
This way we obviously cannot log on to our switches since the credentials won't match.
If I use a regular Putty session the problem doesn't exist.
I'm really loving this tool so far so I hope there's a way to resolve this because networking is super important for our department.