Bird
0
0

A user runs ssh user@host but the connection hangs and never completes. What could be a likely cause?

medium📝 Debug Q7 of 15
Linux CLI - SSH and Remote Access
A user runs ssh user@host but the connection hangs and never completes. What could be a likely cause?
AFirewall blocking SSH port 22
BIncorrect SSH command syntax
CUser's password is expired
DRemote server uses Telnet instead of SSH
Step-by-Step Solution
Solution:

  1. Step 1: Analyze connection hang

    If SSH hangs, it often means network traffic is blocked or dropped.

  2. Step 2: Identify common network block

    Firewall blocking port 22 (default SSH port) is a common cause.

  3. Final Answer:

    Firewall blocking SSH port 22 -> Option A

  4. Quick Check:

    Connection hang = Firewall block = A [OK]
Quick Trick: Check firewall rules if SSH hangs [OK]
Common Mistakes:
  • Assuming syntax error causes hang
  • Thinking expired password causes hang
  • Believing remote server uses Telnet by default

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Linux CLI Quizzes
Archiving and Compression - Why compression saves storage and bandwidth - Quiz 5medium Archiving and Compression - tar (create and extract archives) - Quiz 11easy Archiving and Compression - Why compression saves storage and bandwidth - Quiz 11easy Cron and Scheduling - Editing crontab (crontab -e) - Quiz 13medium Cron and Scheduling - Cron log monitoring - Quiz 1easy Cron and Scheduling - Common cron expressions - Quiz 11easy Environment and Configuration - PATH variable management - Quiz 1easy Package Management - yum/dnf (RHEL/CentOS) basics - Quiz 15hard SSH and Remote Access - SSH tunneling (port forwarding) - Quiz 14medium System Administration - System logs (/var/log) - Quiz 8hard