• Support
  • Articles
  • Resources
  • Products

WSAAsyncselect1:10093 error

Moderator: boris

13 postsPage 1 of 1

boris
Moderator, LogMeTT and TTLEditor developer

Posts:
1590
Joined: Sat Jan 08, 2005 2:52 pm
by boris » Wed Jun 17, 2015 10:33 pm
I am getting permanent error while trying to connect to our two Catalyst 4500 switches via SSH2.

In interactive mode, after filling up SSH dialog box with username and password, dialog window disappears and Tera Term shows blank screen and appears to be hanging. When I click "X" at the upper right corner to close Tera Term, the error message pops up showing the same message 2 times (see below).

If I try to connect using Macro and provide credentials via Macro dialog boxes, SSH dialog box stays on the screen and Tera Term hangs again.

Here is the error Message:
Teratermbug.png
Teratermbug.png (24.28 KiB) Viewed 1887 times


And here is SSH Log.
---------------------------------------------------------------------
Wed Jun 17 15:11:26.362 2015 [8368] Initiating SSH session
Wed Jun 17 15:11:26.533 2015 [8368] Received server identification string: SSH-2.0-Cisco-1.25
Wed Jun 17 15:11:26.533 2015 [8368] Sent client identification string: SSH-2.0-TTSSH/2.73 Win32
Wed Jun 17 15:11:27.235 2015 [8368] client proposal: KEX algorithm: ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1
Wed Jun 17 15:11:27.235 2015 [8368] client proposal: server host key algorithm: ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519,ssh-rsa,ssh-dss
Wed Jun 17 15:11:27.235 2015 [8368] client proposal: encryption algorithm client to server: camellia256-ctr,aes256-ctr,camellia256-cbc,aes256-cbc,camellia192-ctr,aes192-ctr,camellia192-cbc,aes192-cbc,camellia128-ctr,aes128-ctr,camellia128-cbc,aes128-cbc,3des-ctr,3des-cbc,blowfish-ctr,blowfish-cbc,arcfour256,arcfour128,arcfour,cast128-ctr,cast128-cbc
Wed Jun 17 15:11:27.235 2015 [8368] client proposal: encryption algorithm server to client: camellia256-ctr,aes256-ctr,camellia256-cbc,aes256-cbc,camellia192-ctr,aes192-ctr,camellia192-cbc,aes192-cbc,camellia128-ctr,aes128-ctr,camellia128-cbc,aes128-cbc,3des-ctr,3des-cbc,blowfish-ctr,blowfish-cbc,arcfour256,arcfour128,arcfour,cast128-ctr,cast128-cbc
Wed Jun 17 15:11:27.235 2015 [8368] client proposal: MAC algorithm client to server: hmac-sha2-512,hmac-sha2-256,hmac-sha1,hmac-ripemd160@openssh.com,hmac-md5,hmac-sha1-96,hmac-md5-96
Wed Jun 17 15:11:27.235 2015 [8368] client proposal: MAC algorithm server to client: hmac-sha2-512,hmac-sha2-256,hmac-sha1,hmac-ripemd160@openssh.com,hmac-md5,hmac-sha1-96,hmac-md5-96
Wed Jun 17 15:11:27.235 2015 [8368] client proposal: compression algorithm client to server: none
Wed Jun 17 15:11:27.235 2015 [8368] client proposal: compression algorithm server to client: none
Wed Jun 17 15:11:27.235 2015 [8368] SSH2_MSG_KEXINIT was sent at SSH2_send_kexinit().
Wed Jun 17 15:11:27.235 2015 [8368] SSH2_MSG_KEXINIT was received.
Wed Jun 17 15:11:27.235 2015 [8368] server proposal: KEX algorithm: diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1
Wed Jun 17 15:11:27.235 2015 [8368] server proposal: server host key algorithm: ssh-rsa
Wed Jun 17 15:11:27.235 2015 [8368] server proposal: encryption algorithm client to server: aes128-cbc,3des-cbc,aes192-cbc,aes256-cbc
Wed Jun 17 15:11:27.235 2015 [8368] server proposal: encryption algorithm server to client: aes128-cbc,3des-cbc,aes192-cbc,aes256-cbc
Wed Jun 17 15:11:27.235 2015 [8368] server proposal: MAC algorithm client to server: hmac-sha1,hmac-sha1-96,hmac-md5,hmac-md5-96
Wed Jun 17 15:11:27.235 2015 [8368] server proposal: MAC algorithm server to client: hmac-sha1,hmac-sha1-96,hmac-md5,hmac-md5-96
Wed Jun 17 15:11:27.235 2015 [8368] server proposal: compression algorithm client to server: none
Wed Jun 17 15:11:27.235 2015 [8368] server proposal: compression algorithm server to client: none
Wed Jun 17 15:11:27.235 2015 [8368] KEX algorithm: diffie-hellman-group-exchange-sha1
Wed Jun 17 15:11:27.235 2015 [8368] server host key algorithm: ssh-rsa
Wed Jun 17 15:11:27.235 2015 [8368] encryption algorithm client to server: aes256-cbc
Wed Jun 17 15:11:27.235 2015 [8368] encryption algorithm server to client: aes256-cbc
Wed Jun 17 15:11:27.235 2015 [8368] MAC algorithm client to server: hmac-sha1
Wed Jun 17 15:11:27.235 2015 [8368] MAC algorithm server to client: hmac-sha1
Wed Jun 17 15:11:27.251 2015 [8368] compression algorithm client to server: none
Wed Jun 17 15:11:27.251 2015 [8368] compression algorithm server to client: none
Wed Jun 17 15:11:27.251 2015 [8368] SSH2_MSG_KEX_DH_GEX_REQUEST was sent at SSH2_dh_gex_kex_init().
Wed Jun 17 15:11:27.719 2015 [8368] Terminating SSH session...
Wed Jun 17 15:11:34.801 2015 [8368] A communications error occurred while sending an SSH packet.
The connection will close. (WSAAsyncSelect1:10093)
Wed Jun 17 15:11:34.801 2015 [8368] A communications error occurred while sending an SSH packet.
The connection will close. (WSAAsyncSelect1:10093)
Wed Jun 17 15:11:34.801 2015 [8368] SSH2_MSG_DISCONNECT was sent at SSH_notify_disconnecting().
Wed Jun 17 15:11:34.801 2015 [8368] SSH2_MSG_DISCONNECT was sent at SSH_notify_disconnecting().


SecureCRT 7.0.2 has no problem connecting to these switches and shows ssh2: AES-256 in the status bar.

I have all options enabled under TTSSH setup.

Please consider this post as report of 3 problems:
- failure to connect using ssh2: AES-256
- failure to show error message as soon as connection failed (log file is updated, but Tera Term keeps hanging)
- duplicate error message in Error Popup window.
Thanks.
Best regards,
Boris
boris
Moderator, LogMeTT and TTLEditor developer

Posts:
1590
Joined: Sat Jan 08, 2005 2:52 pm
by boris » Fri Jul 03, 2015 4:12 pm
Connection attempt to 2 other Cisco routers at my work started causing above error. Not sure if OS of those routers was recently upgraded or there is any other reason, but I was able to successfully SSH to them using Tera Term in the past.

Had to use SecureCRT to do my job :(
Thanks.
Best regards,
Boris
Yutaka Hirata
TeraTerm Developer

Posts:
598
Joined: Wed Jan 12, 2005 2:35 pm
by Yutaka Hirata » Wed Jul 22, 2015 4:31 pm
Hi Boris,

I apologize for my delay.
It seems that the Cisco IOS will have a bug regarding SSH connection.
I found below site.

https://supportforums.cisco.com/discuss ... openssh-64

Can you retrieve the Cisco router's SSH log?
Best regards, Yutaka Hirata
(yutakakn at gmail.com)
http://hp.vector.co.jp/authors/VA013320/
boris
Moderator, LogMeTT and TTLEditor developer

Posts:
1590
Joined: Sat Jan 08, 2005 2:52 pm
by boris » Thu Jul 23, 2015 6:07 pm
Hi Yutaka,

No worries about the late reply. We are all busy professionals and spend our free time on these projects, so no one here should expect immediate replies to the posts.

I understand that the problem may be on Cisco side, however other SSH Client applications are capable of handling this somehow. Would be good to have in Tera Term such backward compatibility as well.

Unfortunately I do not have sufficient access rights to the routers to get SSH logs from them.

Apart from above I just want to remind that original post was reporting 3 issues and hopefully addressing the last 2 is not that difficult.
Please consider this post as report of 3 problems:
- failure to connect using ssh2: AES-256
- failure to show error message as soon as connection failed (log file is updated, but Tera Term keeps hanging)
- duplicate error message in Error Popup window.
Thanks.
Best regards,
Boris
MihaiMM
Newbie

Posts:
8
Joined: Tue Nov 05, 2013 2:04 pm
by MihaiMM » Mon Jul 27, 2015 2:54 pm
Hi Yutaka, Boris,

If you want I can help with logs for Cisco devices. Just please tell me what should I give, and where I should transfer this logs.

One of the cisco devices which shows this error is:
Switch Ports Model SW Version SW Image
------ ----- ----- ---------- ----------
* 1 28 WS-C2960XR-24TS-I 15.0(2)EX5 C2960X-UNIVERSALK9-M


As a first info I have the following output from cisco debug:

Jul 27 14:40:32.447: SSH1: starting SSH control process
Jul 27 14:40:32.447: SSH1: sent protocol version id SSH-1.99-Cisco-1.25
Jul 27 14:40:32.531: SSH1: protocol version id is - SSH-2.0-TTSSH/2.73 Win32
Jul 27 14:40:32.531: SSH2 1: send:packet of length 344 (length also includes padlen of 5)
Jul 27 14:40:32.531: SSH2 1: SSH2_MSG_KEXINIT sent
Jul 27 14:40:32.985: SSH2 1: ssh_receive: 1008 bytes received
Jul 27 14:40:32.985: SSH2 1: input: total packet length of 1008 bytes
Jul 27 14:40:32.985: SSH2 1: partial packet length(block size)8 bytes,needed 1000 bytes,
maclen 0
Jul 27 14:40:32.985: SSH2 1: input: padlength 11 bytes
Jul 27 14:40:32.985: SSH2 1: SSH2_MSG_KEXINIT received
Jul 27 14:40:32.985: SSH2:kex: client->server enc:aes256-cbc mac:hmac-sha1
Jul 27 14:40:32.985: SSH2:kex: server->client enc:aes256-cbc mac:hmac-sha1
Jul 27 14:40:33.188: SSH2 1: ssh_receive: 24 bytes received
Jul 27 14:40:33.188: SSH2 1: input: total packet length of 24 bytes
Jul 27 14:40:33.188: SSH2 1: partial packet length(block size)8 bytes,needed 16 bytes,
maclen 0
Jul 27 14:40:33.188: SSH2 1: input: padlength 6 bytes
Jul 27 14:40:33.188: SSH2 1: SSH2_MSG_KEX_DH_GEX_REQUEST received
Jul 27 14:40:33.188: SSH2 1: Range sent by client is - 1024 < 8192 < 8192
Jul 27 14:40:33.188: %SSH-3-DH_RANGE_FAIL: Client DH key range mismatch with maximum configured DH key on server
Jul 27 14:40:33.289: SSH1: Session disconnected - error 0x00


I hope it helps, but if you need more data please tell me.

Best regards,
Mihai
MihaiMM
Newbie

Posts:
8
Joined: Tue Nov 05, 2013 2:04 pm
by MihaiMM » Mon Jul 27, 2015 8:07 pm
Hello again,

I have upgraded the L3 Switch to latest official (recommended -> Feb 2015) IOS, without success.
Switch Ports Model SW Version SW Image
------ ----- ----- ---------- ----------
* 1 28 WS-C2960XR-24TS-I 15.0(2a)EX5 C2960X-UNIVERSALK9-M


I'm able to connect only if I use sha1 instead of sha2 or if i use an older (I think 4.86) ttxssh.dll.

From what i see this error "DH_RANGE_FAIL: Client DH key range mismatch" it is very popular.
The bug was addressed to CISCO please follow below link:
https://tools.cisco.com/bugsearch/bug/CSCuo76464

I have also tried few of the ideas regarding "KexAlgorithms", without success, at least until now.

Therefore is the error on which Yutaka was referring in the first place.


Best regards,
Mihai
boris
Moderator, LogMeTT and TTLEditor developer

Posts:
1590
Joined: Sat Jan 08, 2005 2:52 pm
by boris » Wed Jul 29, 2015 5:54 pm
Got the same error while connecting to 2 other devices. Downgraded to Tera Term 4.86 to solve this issue.
Thanks.
Best regards,
Boris
Yutaka Hirata
TeraTerm Developer

Posts:
598
Joined: Wed Jan 12, 2005 2:35 pm
by Yutaka Hirata » Sat Aug 01, 2015 5:30 pm
Hi Boris,

Tera Term project team thinks that your problem will be a bug of the Cisco router's firmware
not Tera Term bug because the below site has information.

https://bugzilla.mindrot.org/show_bug.cgi?id=2209

However, we will support for the Cisco router bug in next release.

Thanks.
Best regards, Yutaka Hirata
(yutakakn at gmail.com)
http://hp.vector.co.jp/authors/VA013320/
boris
Moderator, LogMeTT and TTLEditor developer

Posts:
1590
Joined: Sat Jan 08, 2005 2:52 pm
by boris » Mon Aug 03, 2015 8:43 pm
Hi Yutaka,

I understand that this is Cisco problem and I appreciate your readiness to add workaround to Tera Term code.

In fact, not that many users are aware about the origin of this fault. They will just see that Tera Term cannot connect to certain node while other terminal emulators can. That's why making Tera Term more robust and able to handle this faulty scenario is important.


Meanwhile, if someone is experiencing this issue, you can downgrade to previous version 4.86 which works just fine.
Thanks.
Best regards,
Boris
Yutaka Hirata
TeraTerm Developer

Posts:
598
Joined: Wed Jan 12, 2005 2:35 pm
by Yutaka Hirata » Tue Aug 04, 2015 3:52 pm
Hi Boris,

We have added workaround regarding Cisco router in the following archive:

http://ttssh2.osdn.jp/snapshot/snapshot-20150805.zip

Please test this archive to resolve your problem.

Thanks.
Best regards, Yutaka Hirata
(yutakakn at gmail.com)
http://hp.vector.co.jp/authors/VA013320/
boris
Moderator, LogMeTT and TTLEditor developer

Posts:
1590
Joined: Sat Jan 08, 2005 2:52 pm
by boris » Tue Aug 04, 2015 11:36 pm
Yes, it is working !!! :D

Thank you!

Best regards,
Boris
AmyLou
Newbie

Posts:
1
Joined: Sat Sep 10, 2016 2:23 pm
by AmyLou » Sat Sep 10, 2016 2:29 pm
Can you provide that workaround again please? The link is no longer found.
Yutaka Hirata
TeraTerm Developer

Posts:
598
Joined: Wed Jan 12, 2005 2:35 pm
by Yutaka Hirata » Sun Sep 11, 2016 7:37 am
Hi AmyLou,

AmyLou wrote:Can you provide that workaround again please? The link is no longer found.


The workaround has been implemented in Tera Term 4.88(TTSSH 2.74) or later.
Please find below history.

http://ttssh2.osdn.jp/manual/en/about/h ... ttssh_2.74

Thanks.
Best regards, Yutaka Hirata
(yutakakn at gmail.com)
http://hp.vector.co.jp/authors/VA013320/
Display posts from previous:
Sort by:

13 postsPage 1 of 1

Users browsing this forum: No registered users