Telnet bug

avatar
jeroen01
Disabled

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.

All Comments (27)

avatar

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,

Jeff Dagenais

avatar
jeroen01
Disabled

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.

avatar

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,

Hubert Mireault

avatar

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,

Hubert Mireault

avatar
jeroen01
Disabled

Hi Hubert,

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

avatar

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,

Denis Vincent

avatar

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,

Denis Vincent

avatar
jeroen01
Disabled

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