Keyboard not working
What “Keyboard not working” usually means
When PuTTY reports Keyboard not working, the client has already attempted a network or protocol step and failed before a normal interactive shell is available. This guide explains what the message usually means on Windows clients, which local settings to verify first, and when the problem is almost certainly on the server, firewall, or DNS path rather than inside the PuTTY GUI.
Keystrokes do not reach the remote shell as expected—local focus issues, wrong keyboard mode, sticky terminal states, or remote applications capturing input.
Independent resource: Putty.info is educational only and is not affiliated with the official PuTTY project. Compare symptoms against the official documentation for your installed version.
Symptoms you will see
Operators usually notice this failure in one of a few repeatable ways. Capture the exact dialog text, the hostname and port from the Session panel, and whether the failure happens before or after a username prompt—those details decide which checklist below applies.
- Typing produces nothing or unexpected escape sequences.
- Backspace/Delete behaviour inverted.
- Function keys misbehave inside editors.
Likely causes ranked by frequency
Several independent conditions can produce the same client-facing wording. Work from the outside in: reachability first, protocol selection second, authentication third. Changing key files will not fix a TCP refusal, and opening a wider firewall will not fix a rejected public key.
- Wrong window focused; input goes elsewhere.
- Terminal → Keyboard mappings mismatched to remote stty settings.
- Remote application in raw mode after a crash left the tty odd (reset needed).
- AltGr/layout issues on international keyboards.
Step-by-step client checks
Use this ordered checklist on a workstation you control. Prefer saved sessions so Host Name, Port, and Connection type stay consistent while you isolate one variable at a time.
- Click inside the terminal to focus; try Enter.
- Run reset on the remote side from a second working session if available.
- Review Terminal → Keyboard for Backspace/Delete mapping.
- Test locally in Notepad that the physical keyboard works.
- Disable experimental key macros or automations sending keys into the window.
- Compare behaviour in a fresh saved session with defaults.
Do not paste private keys, passphrases, or production passwords into Putty.info tools or contact forms. Diagnose locally with PuTTY, Plink, PSCP, or PSFTP from an official install.
When it is a server or network issue
If only certain hosts fail, check readline/term settings and whether users land in restricted menus expecting different key bindings.
If TCP connects from another network path but fails from yours, involve the network team with traceroute/path evidence rather than repeatedly regenerating keys. If authentication fails after a banner appears, collect the server sshd logs for the same timestamp and username—client-side retries alone rarely reveal AccountLocked, Match blocks, or AllowUsers denials.