VanDyke Software Forums

VanDyke Software Forums (
-   Secure Shell (
-   -   The semaphore timeout period has expired ! (

Dhawi 04-29-2019 05:00 AM

The semaphore timeout period has expired !

I have an issue where i am not able to connect using SSH to a remote device

I can telnet port 22 and it is open and i can connect to device GUI console on different port and it is working

i check previous posts on this forum but non of them helped me

[LOCAL] : SSH2Core version
[LOCAL] : Connecting to x.x.x.x:22 ...
SecureCRT - Version 7.3.7 (x64 build 1034)
[LOCAL] : Using protocol SSH2
[LOCAL] : RECV : Remote Identifier = 'SSH-2.0-OpenSSH_5.3'
[LOCAL] : CAP : Remote can re-key
[LOCAL] : CAP : Remote sends language in password change requests
[LOCAL] : CAP : Remote sends algorithm name in PK_OK packets
[LOCAL] : CAP : Remote sends algorithm name in public key packets
[LOCAL] : CAP : Remote sends algorithm name in signatures
[LOCAL] : CAP : Remote sends error text in open failure packets
[LOCAL] : CAP : Remote sends name in service accept packets
[LOCAL] : CAP : Remote includes port number in x11 open packets
[LOCAL] : CAP : Remote uses 160 bit keys for SHA1 MAC
[LOCAL] : CAP : Remote supports new diffie-hellman group exchange messages
[LOCAL] : CAP : Remote correctly handles unknown SFTP extensions
[LOCAL] : CAP : Remote correctly encodes OID for gssapi
[LOCAL] : CAP : Remote correctly uses connected addresses in forwarded-tcpip requests
[LOCAL] : CAP : Remote can do SFTP version 4
[LOCAL] : CAP : Remote x.509v3 uses ASN.1 encoding for DSA signatures
[LOCAL] : CAP : Remote correctly handles
[LOCAL] : Connected for 18 seconds, 0 bytes sent, 21 bytes received

[LOCAL] : Stream has closed [CLOSE_TYPE_NONSPECIFIC] : The semaphore timeout period has expired.

The semaphore timeout period has expired.

berdmann 04-29-2019 11:30 AM

Hi Dhawi,

The "semaphore timeout period has expired" error is a generic network error, and usually indicates a problem with the machine that SecureCRT is running on or a problem with the machine's network configuration.

Individuals seeing this problem indicated that the problems were related to one or more of the following issues:
- DHCP assigning network addresses (some resolved by going static).
- Slow networks.
- Sometimes disc problems, or file retrieval problems.
- Reports of port scanners or other network security tools probing the network.
- Difficulty connecting to specific ports on a non-loopback network interface.
- Wireless networks.
This issue cannot be resolved in SecureCRT. I recommend reaching out to your network administrators to troubleshoot this behavior further.

All times are GMT -6. The time now is 07:02 AM.