A serial console provides direct, out-of-band access to a device for initial configuration, troubleshooting, and recovery when network access is unavailable. Connecting with PuTTY on Windows 11 makes it possible to interact with the device’s console port using a familiar GUI.
Serial consoles use a local serial interface exposed by Windows as a COM port (built-in UART, USB-to-serial adapter, or a vendor console cable). PuTTY opens that port and exchanges raw text with the device using the selected communication parameters such as Speed (baud), Data bits, Parity, Stop bits, and Flow control.
Console settings must match the device, or output appears garbled or stays blank. Serial access is also not encrypted, so physical access to the cable and port equals privileged access; keep consoles secured and disconnect when finished.
Steps to connect to a serial console in PuTTY:
- Connect a USB-to-serial adapter to the PC when no physical serial port is available.
- Connect the console cable to the device’s console or serial port.
- Open Device Manager in Windows 11.
- Expand Ports (COM & LPT) in Device Manager.
- Note the COM port number for the serial adapter.
- Launch PuTTY.
- Select Serial under Connection type.
- Enter the COM port (for example, COM3) in Serial line.
- Enter the device’s Speed (baud) value (for example, 9600) in Speed.
Common console speeds are 9600 and 115200.
- Open Connection → Serial in the left category tree.
- Set Data bits to 8.
- Set Stop bits to 1.
- Set Parity to None.
- Set Flow control to None unless the device documentation specifies otherwise.
A mismatched Flow control setting can block typing or prevent any output.
- Enter a name in Saved Sessions under Session.
- Click Save to store the serial settings.
Saving the profile keeps serial settings ready for the next connection.
- Click Open to start the serial session.
Serial sessions are unencrypted; treat console access like a root password on a cable.
- Confirm console access by checking for a login prompt or boot messages.
Garbled characters usually mean the wrong Speed (baud), while a blank screen often indicates the wrong COM port or Flow control setting.
- Press Enter to refresh the console when the screen is idle.
Use Special Command → Break only when interrupting the bootloader is required.
Mohd Shakir Zakaria is a cloud architect with deep roots in software development and open-source advocacy. Certified in AWS, Red Hat, VMware, ITIL, and Linux, he specializes in designing and managing robust cloud and on-premises infrastructures.
