When I use SSH connection to switch，prompt:UnKnown Error

[nchair]

No description provided.

[nchair]

When I use SSH connection to switch，prompt:UnKnown Error

[kingToolbox]

I will analyze what situations will report UnKnown Error, and if there are any results, I will update here. Thank you,

[kingToolbox]

Hello, I analyzed the related code, and there may be two reasons, one is an unknown network error, and the other is a host lookup error. More detailed information may be needed for the first one. But for the second one, I wonder if the target of your connection uses a domain name, or an IPv6 address? And can other SSH clients connect normally at the same time?

[kingToolbox]

This issue will be closed because no further activity occurs during this month. Please reopen this issue if it is still valid. Thank you.

[nchair]

Hello, I analyzed the related code, and there may be two reasons, one is an unknown network error, and the other is a host lookup error. More detailed information may be needed for the first one. But for the second one, I wonder if the target of your connection uses a domain name, or an IPv6 address? And can other SSH clients connect normally at the same time?

i using iPV4 to connection，network is normal，use electerm, MobaXterm, terminus to connect successfully

[kingToolbox]

Thank you very much for the additional information.

If it is convenient for you, please help to collect the running log for analysis. The steps are as follows:

• Open the Session Property dialog box of the session.
• Select Terminal - Logging - Log Types - Log All Session Output.
• Connect the host and close the tab when the error occurs.
• Find the latest log under the folder WindTerm_Install_Path/profiles/default.v10/erminal/Session_Name/ and paste it here as attachment after compression.

Please dont worry, the log only contains protocol data and does not contain private data such as usernames and passwords. You can use any text editor to open the log and check it.

It doesn’t matter if it’s inconvenient to collect logs, please tell me, I will continue to do static analysis, but frankly speaking, static analysis is more difficult to solve this issue.

[nchair]

Thank you very much for the additional information.

If it is convenient for you, please help to collect the running log for analysis. The steps are as follows:

• Open the Session Property dialog box of the session.
• Select Terminal - Logging - Log Types - Log All Session Output.
• Connect the host and close the tab when the error occurs.
• Find the latest log under the folder WindTerm_Install_Path/profiles/default.v10/erminal/Session_Name/ and paste it here as attachment after compression.

Please dont worry, the log only contains protocol data and does not contain private data such as usernames and passwords. You can use any text editor to open the log and check it.

It doesn’t matter if it’s inconvenient to collect logs, please tell me, I will continue to do static analysis, but frankly speaking, static analysis is more difficult to solve this issue.

hi:
This is the log of the connected switch.
核心交换机_2021-08-06_19-15-17.log

[kingToolbox]

Sorry for the late reply. I just finished a long trip, and because there is no Internet, I can't deal with the issue in time.

Thank you for your log, I will analyze and see if the problem can be solved. In addition, the new version WindTerm_2.2.0_Prerelease_1 adds a feature that allows you to view all error messages when an error occurs. If possible, please download and use. Once the Unknown Error appears, click the expand button next to the close button to expand the message bar, so that you can see more specific error messages, and please tell me, that is the real cause of the error. Thank you.

[ghost]

Having the same problem "Unknown Error" when trying to SSH to a Cat4500 switch or ISR4331 router.

Log ends with:

ssh_packet_disconnect_callback: Received SSH_MSG_DISCONNECT 2:Protocol error: expected packet type 61, got 50
ssh_packet_disconnect_callback: Received SSH_MSG_DISCONNECT: 2:Protocol error: expected packet type 61, got 50

No issue connecting to a Nexus9K switch.

Feels vaguely similar to this asyncssh issue

This is on 2.2.0_Prerelease_1. Sorry but I do not see where the "expand" button next to the "close" button is.

[kingToolbox]

@akmiscer
Thank you for providing such detailed and similar issue. I will study this and try to solve the problem. If there is any progress, I will update here.

BTW, Don't mind that button, it will only appear when multiple messages are reported.