Article ID: 000094000 Content Type: Connectivity Last Reviewed: 05/31/2024

Unable to Secure Shell (SSH) into Intel® Developer Cloud Using Corporate’s Network

Environment

Ubuntu 20 Machine Corporate Lab network

BUILT IN - ARTICLE INTRO SECOND COMPONENT
Summary

Setup and configure proxy based on the documentation provided

Description

 

  1. While SSH into Bare Metal, received the following error message:
    "debug3: finish_connect - ERROR: async io completed with error: 10060, io:0000017125225020
    kex_exchange_identification: Connection closed by remote host
    nc: connection failed, socksv5 error : TTL expire
    "

     
  2. Initiated SSH connection into different Bare Metal instance using corporate network and encountered error:
    "nc: getaddrinfo: nodename nor servname provided, or not known
    kex_exchange_identification: Connection closed by remote host
    Connection closed by UNKNOWN port 65535
    kex_exchange_identification: Connection closed by remote host
    Connection closed by UNKNOWN port 65535
    "
Resolution
  • Set up proxy based on this Getting Started Guide.
  • PROXYSERVER and PROXYPORT can be obtained from Corporate Lab Administrator.
  • If the issue persists after setting up a proxy, test the SSH command with a public network (Not a Corporate Network).
  • If the public network works fine, the most probability issue comes from the proxy.
  • Please submit an IT ticket to resolve the proxy issue.

Related Products

This article applies to 1 products