No SSH Response from Cisco SF350 - WeOnlyDo Discussion board

No SSH Response from Cisco SF350 (wodSSH / wodSSH.NET)

by Phill, Friday, May 29, 2020, 16:21 (45 days ago)

Hi,

We are using the wodSSH.NET Component (2.6.4) against Cisco SF350 and have been unable to make a connection. Reviewing a wireshark trace we can see that the communication does not progress past the offered server and client protocols.

We are able to putty to the SF350 from the same server and so wondered if anyone had any recommendations?

Below is a text version of a wireshark trace.
10. is the SF350
192. is the system running wodSSH

1 192.x.x.x 10.x.x.x TCP 70 57824 → 22 [SYN, ECN, CWR] Seq=0 Win=8192 Len=0 MSS=1460 WS=256 SACK_PERM=1
2 192.x.x.x 10.x.x.x TCP 70 [TCP Out-Of-Order] 57824 → 22 [SYN, ECN, CWR] Seq=0 Win=8192 Len=0 MSS=1460 WS=256 SACK_PERM=1
3 192.x.x.x 10.x.x.x TCP 70 [TCP Out-Of-Order] 57824 → 22 [SYN, ECN, CWR] Seq=0 Win=8192 Len=0 MSS=1460 WS=256 SACK_PERM=1
4 192.x.x.x 10.x.x.x TCP 70 [TCP Out-Of-Order] 57824 → 22 [SYN, ECN, CWR] Seq=0 Win=8192 Len=0 MSS=1460 WS=256 SACK_PERM=1
5 10.x.x.x 192.x.x.x TCP 62 22 → 57824 [SYN, ACK] Seq=0 Ack=1 Win=4096 Len=0 MSS=1440
6 192.x.x.x 10.x.x.x TCP 58 57824 → 22 [ACK] Seq=1 Ack=1 Win=64800 Len=0
7 192.x.x.x 10.x.x.x TCP 58 [TCP Dup ACK 6#1] 57824 → 22 [ACK] Seq=1 Ack=1 Win=64800 Len=0
8 10.x.x.x 192.x.x.x SSHv2 84 Server: Protocol (SSH-2.0-OpenSSH_7.3p1.RL)
9 192.x.x.x 10.x.x.x SSHv2 80 Client: Protocol (SSH-2.0-WeOnlyDo.Net)
10 192.x.x.x 10.x.x.x TCP 80 [TCP Retransmission] 57824 → 22 [PSH, ACK] Seq=1 Ack=27 Win=64774 Len=22
11 192.x.x.x 10.x.x.x TCP 80 [TCP Retransmission] 57824 → 22 [PSH, ACK] Seq=1 Ack=27 Win=64774 Len=22
12 192.x.x.x 10.x.x.x TCP 80 [TCP Retransmission] 57824 → 22 [PSH, ACK] Seq=1 Ack=27 Win=64774 Len=22
13 10.x.x.x 192.x.x.x TCP 58 22 → 57824 [ACK] Seq=27 Ack=23 Win=4074 Len=0
14 192.x.x.x 10.x.x.x TCP 58 57824 → 22 [RST, ACK] Seq=23 Ack=27 Win=0 Len=0
15 192.x.x.x 10.x.x.x TCP 58 57824 → 22 [RST, ACK] Seq=23 Ack=27 Win=0 Len=0

No SSH Response from Cisco SF350

by Jasmine, Friday, May 29, 2020, 18:03 (45 days ago) @ Phill

Hi Phill,

you seem to be using older version of wodSSH.NET, and I believe we did make fix for this 'waiting for other party' issue. Can you try with the latest if it works ok?

Regards,
Jasmine.