SSH Connection Issue: "No route to host" Error when Connecting to DevCloud

[DevPriyansh]

Hello Intel DevCloud Community,

I am facing an issue while trying to connect to Intel DevCloud via SSH. Below is the exact command I used and the error message I received:

Command:

ssh -J guest@146.152.226.75 devcloud@192.168.6.2

Error Message:

channel 0: open failed: connect failed: No route to host
stdio forwarding failed

Troubleshooting Steps I Have Tried:

1. Checked Network Access:

   • My internet connection is stable.
   • I am able to ping 146.152.226.75 successfully.
   • I tried connecting directly to the jump host (guest@146.152.226.75) using SSH, and it worked.

2. Checked DevCloud Status:

   • I logged into the Intel DevCloud web portal, and there were no reported outages.

3. Verified Port Accessibility:

   • I used nc -zv 192.168.6.2 22 from the jump host, but it failed, indicating that the target server might not be reachable.

4. Checked Firewall Rules:

   • I suspect that there may be firewall restrictions on the jump host preventing access to 192.168.6.2:22.

5. Tried Different SSH Options:

   • I disabled strict host key checking:

     ssh -o StrictHostKeyChecking=no -J guest@146.152.226.75 devcloud@192.168.6.2

   • I also enabled verbose logging to debug further:

     ssh -vvv -J guest@146.152.226.75 devcloud@192.168.6.2

     The logs indicate that the connection attempt fails when trying to reach 192.168.6.2 from the jump host.

Request for Assistance

Has anyone else encountered this issue recently? Is there any known downtime or configuration change affecting access to 192.168.6.2?

Any guidance or suggestions would be greatly appreciated!

Thank you!

[Faiz_Intel]

Hi DevPriyansh,

Thank you for reaching out to us.

We apologize for the inconvenience that you are experiencing. To ensure we can assist you effectively, please provide the following details. If not applicable, please use 'N/A'. We appreciate your cooperation, and we look forward to resolving this matter promptly.

1. Severity level of the issue: Low/Medium/High/Critical

2. Reservation details:-

- Instance type: 

- Instance ID/Resource ID: 

- Instance name: 

- Start time/Created at: 

- Instance IP address: 

- Region: us-region-1/us-region-2/us-region-3

3. Cloud account ID: 

4. Is there any important data stored on the instance? Yes/No

5. Can the IDC support team access the instance and perform the required operations to validate or fix an issue if needed? Yes/No

Regards,

Faiz

[DevPriyansh]

hello faiz 

firstly thanks for addressing my issue

here are the details you you asked.

1. severity of the issue = medium

2. Reservation Details

 1. instance type - Intel® Data Center GPU Flex 170 (single GPU) with 4th Generation Intel® Xeon® Scalable processors

 2. resource id - reservation-5792

 3. instance name - mistral-inferencing

 4. Created time - 19\02\2025

 5. instance ip address - 192.168.6.2

 6. instance region - us-Region-2

3. cloud account id - 175692083598

4. Is there any important data stored on the instance - actually no this instance started yesterday so for now i dont have any important data but i waited 2 days for this to approve i dont want to loose this instance.

5. Can the IDC support team access the instance and perform the required operations to validate or fix an issue if needed - so yes you can access my instance but please fix this issue i think mistakenly i shutted down the instance using some wrong command please check and fix this 

best regards 

priyansh jain

pjain2@cougars.ccis.edu

[Faiz_Intel]

Hi DevPriyansh,

Thank you for providing the information. I have escalated your case to the appropriate team for further investigation of this matter. Upon receiving their feedback, I will provide you with an update. We greatly appreciate your patience.

Regards,

Faiz

[Faiz_Intel · Accepted solution]

Hi DevPriyansh,

Thank you for your patience. We have been informed that the issue has been resolved. Could you please try again and let us know if the issue persists?

Regards,

Faiz

[Faiz_Intel]

This thread will no longer be monitored since this issue has been resolved. If you need any additional information from Intel, please submit a new question.