// Troubleshooting guide
Cannot SSH to a Cisco switch or router
Separate reachability, SSH service, VTY configuration and access lists to find why SSH management fails.
1 min read#ccna#ssh#security#troubleshooting
Symptoms
- Connection refused when opening SSH
- Connection times out
- SSH connects but the login is rejected
- SSH works from one subnet but not another
Timeout or refused?
- Timeout → the packets never arrive or the reply never returns: addressing, gateway, routing, or an ACL dropping silently.
- Refused → the device answered but is not listening for SSH on that address, or the VTY lines reject it.
- Login rejected → credentials or the authentication method.
Reachability
ping <device-address>
On a switch, check the management SVI is up (show ip interface brief) and that ip default-gateway is set — without it the switch can answer only hosts on its own subnet.
Is SSH enabled?
show ip ssh
show crypto key mypubkey rsa
SSH needs a hostname other than the default, a domain name, and an RSA key (crypto key generate rsa modulus 2048). "SSH Disabled" in show ip ssh means no key exists.
VTY lines
show running-config | section line vty
transport input ssh(orall) must be present.login localneeds ausernameto exist;loginalone needs a line password.- Are all lines busy?
show userslists the active sessions.
Access class
access-class NAME in on the VTY lines filters by source address. If SSH works from one subnet only, check that ACL and its counters with show access-lists.
Credentials
login local with a username that has privilege 1 logs in to user EXEC mode — the login works, but enable needs the enable secret. Use privilege 15 for administrators, or give them the enable secret.