Timeout with wodsftp - WeOnlyDo Discussion board

Timeout with wodsftp (wodSFTP / wodSFTP.NET / wodSFTPdll)

by pjeffmcd, Tuesday, October 27, 2009, 23:04 (5293 days ago)

Hello all,

Looking for some assistance with a timeout issue connecting to an HPUX server...my app (VB based) is utilizing the wodsftp ActiveX component (version 3.2.1.62) and is passing the host, user/pass, and a timeout to the HPUX server. Timeout is set to 30 seconds...30 seconds after the authentication attempt an error 1460 is received.

I'm able to authenticate via putty's sftp and winscp. Using wireshark from Windows, I captured a trace with both wodsftp and winscp:

WODSFTP
TCP ndsp > ssh [SYN] Seq=0 Win=64240 Len=0 MSS=1460
TCP ssh > ndsp [SYN, ACK] Seq=0 Ack=1 Win=32768 Len=0 MSS=1460
TCP ndsp > ssh [ACK] Seq=1 Ack=1 Win=64240 Len=0
SSHv2 Server Protocol: SSH-2.0-OpenSSH_5.0p1+sftpfilecontrol-v1.2-hpn13v1
SSHv2 Client Protocol: SSH-2.0-WeOnlyDo

SSHv2 Server: Key Exchange Init
SSHv2 Client: Key Exchange Init
TCP ssh > ndsp [ACK] Seq=836 Ack=499 Win=32768 Len=0
SSHv2 Client: Diffie-Hellman Key Exchange Init
SSHv2 Server: New Keys
SSHv2 Client: New Keys
TCP ssh > ndsp [ACK] Seq=1556 Ack=659 Win=32768 Len=0
TCP [TCP segment of a reassembled PDU]
TCP [TCP segment of a reassembled PDU]
TCP [TCP segment of a reassembled PDU]
TCP [TCP segment of a reassembled PDU]
TCP [TCP segment of a reassembled PDU]
TCP ssh > ndsp [ACK] Seq=1692 Ack=863 Win=32768 Len=0
TCP ndsp > ssh [FIN, ACK] Seq=863 Ack=1692 Win=64104 Len=0
TCP ssh > ndsp [ACK] Seq=1692 Ack=864 Win=32768 Len=0

WINSCP
TCP ndnp > ssh [SYN] Seq=0 Win=64240 Len=0 MSS=1460
TCP ssh > ndnp [SYN, ACK] Seq=0 Ack=1 Win=32768 Len=0 MSS=1460
TCP ndnp > ssh [ACK] Seq=1 Ack=1 Win=64240 Len=0
SSHv2 Server Protocol: SSH-2.0-OpenSSH_5.0p1+sftpfilecontrol-v1.2-hpn13v1
SSHv2 Client Protocol: SSH-2.0-WinSCP_release_4.2.3

SSHv2 Server: Key Exchange Init
SSHv2 Client: Key Exchange Init
TCP ssh > ndnp [ACK] Seq=836 Ack=639 Win=32768 Len=0
SSHv2 Client: Diffie-Hellman Key Exchange Init
SSHv2 Server: Diffie-Hellman Key Exchange Reply
SSHv2 Client: Diffie-Hellman GEX Init
SSHv2 Server: Diffie-Hellman GEX Reply
TCP ndnp > ssh [ACK] Seq=927 Ack=1964 Win=64240 Len=0
SSHv2 Client: New Keys
TCP ssh > ndnp [ACK] Seq=1964 Ack=943 Win=32768 Len=0
SSHv2 Encrypted request packet len=52
SSHv2 Encrypted response packet len=52
SSHv2 Encrypted request packet len=68
SSHv2 Encrypted response packet len=84
SSHv2 Encrypted request packet len=100
TCP ssh > ndnp [ACK] Seq=2100 Ack=1163 Win=32768 Len=0
SSHv2 Encrypted response packet len=68
SSHv2 Encrypted request packet len=296
SSHv2 Encrypted response packet len=52
SSHv2 Encrypted request packet len=296
SSHv2 Encrypted response packet len=36
SSHv2 Encrypted request packet len=68
TCP ssh > ndnp [ACK] Seq=2256 Ack=1823 Win=32768 Len=0
SSHv2 Encrypted response packet len=52
SSHv2 Encrypted request packet len=84
TCP ssh > ndnp [ACK] Seq=2308 Ack=1907 Win=32768 Len=0
SSHv2 Encrypted request packet len=68
SSHv2 Encrypted response packet len=88
SSHv2 Encrypted request packet len=52
SSHv2 Encrypted response packet len=84
SSHv2 Encrypted request packet len=52
SSHv2 Encrypted response packet len=100
SSHv2 Encrypted request packet len=68
SSHv2 Encrypted response packet len=68
SSHv2 Encrypted request packet len=68
SSHv2 Encrypted response packet len=804
SSHv2 Encrypted request packet len=68
SSHv2 Encrypted response packet len=84
SSHv2 Encrypted request packet len=68
SSHv2 Encrypted response packet len=68
TCP ndnp > ssh [ACK] Seq=2351 Ack=3604 Win=64088 Len=0

The traces appear to be mostly identical until the Client: Diffie-Hellman Key Exchange Init ....at that point there is no reply from the server in wodsftp as there is with winscp (Server: Diffie-Hellman Key Exchange Reply).

I've researched outside of wodsftp (unrelated sftp forums, hpux config, etc.) but have come up empty handed.

Any information or ideas would be greatly appreciated!

-Pete


Complete thread: