Welcome to the VanDyke Software Forums

Join the discussion today!


Go Back   VanDyke Software Forums > Secure Shell

Reply
 
Thread Tools Display Modes
  #1  
Old 04-29-2019, 05:00 AM
Dhawi Dhawi is offline
Registered User
 
Join Date: Apr 2019
Posts: 1
The semaphore timeout period has expired !

Hi,

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 7.3.0.1034
[LOCAL] : Connecting to x.x.x.x:22 ...
[LOCAL] : Changing state from STATE_NOT_CONNECTED to STATE_EXPECT_KEX_INIT
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 zlib@openssh.com
[LOCAL] : SEND : KEXINIT
[LOCAL] : Changing state from STATE_EXPECT_KEX_INIT to STATE_CLOSED
[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.
Reply With Quote
  #2  
Old 04-29-2019, 11:30 AM
berdmann berdmann is offline
VanDyke Technical Support
 
Join Date: Aug 2017
Posts: 207
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.
__________________
Thanks,
--Brittney

VanDyke Software
Technical Support
support@vandyke.com
(505) 332-5730
Reply With Quote
Reply

Tags
semaphore , timeout


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


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