Boarding pass printers offline — Wi-Fi channel config & roaming fixes

Joe B.

Expert ★★★★★ 27,853 satisfied customers

Specialities: Windows 11/10, Printers, Networking, Group Policy, Print Servers

Airport/airline thermal printers offline — Wi-Fi channel plan, 2.4 GHz vs 5 GHz, DFS, band steering, DTIM & power-save

Technician

Hey! We’ll get your boarding pass printers back online. These thermal printers (Zebra, Epson TM, Honeywell) often drop due to Wi-Fi channel conflicts, DFS radar hits, or aggressive band steering.
A few questions: model/brand? Fixed kiosk, gate counter, or mobile cart? SSID uses WPA2-Enterprise (802.1X) or WPA2-PSK? Are queues RAW 9100, LPR, or IPP/IPP-over-TLS? And do disconnects happen during peak flights or when carts move between concourses?

Customer

Gate counters use Zebra ZD620 on Wi-Fi. They flip to Offline every few minutes. We’re on WPA2-Enterprise, single SSID for staff devices. APs are set to auto channel with band steering to 5 GHz. Printers use DHCP.

Technician

Understood. Airports are noisy RF environments. With auto channel and band steering, APs may push printers between 2.4 GHz and 5 GHz or onto DFS channels (52–144). When radar triggers, APs evacuate the channel — printers go Offline. Also, roaming thresholds/DTIM values or U-APSD power save can starve print traffic.
Plan: 1) Lock a clean non-DFS 5 GHz channel (36/40/44/48) or use 2.4 GHz 1/6/11 with 20 MHz width. 2) Disable band steering for printer MACs or put them on a printer-only SSID. 3) Fix IP addressing (DHCP reservation or static). 4) Tweak DTIM, min RSSI, and WMM so raw-9100/LPR stays stable.

Customer

We can create a separate SSID for printers. What channel settings do you recommend exactly? The site has overlapping terminals.

Technician

Step 1 — Build a predictable channel plan
• 5 GHz: choose non-DFS channels 36/40/44/48 only; set 20 MHz width for reliability; disable auto-channel on APs serving printers.
• 2.4 GHz (only if required): use 1/6/11 only, 20 MHz width; avoid overlapping channels.
• Lower AP power to reduce co-channel interference; target RSSI −55 to −65 dBm at counters.
• Keep DTIM at 2–3 and disable U-APSD power save on the printer SSID; enable WMM for consistent queueing.

Customer

Noted. We also see printers change IP after reboots, then Windows queues can’t find them. Any best practice?

Technician

Step 2 — Stabilize addressing
• Use DHCP reservations (or static IP) per printer on a dedicated VLAN with short lease (2–4 hrs) but bound to MAC.
• Disable client isolation on the printer SSID/VLAN if a print server or POS host must reach printers via RAW 9100, LPR, or IPP.
• Exempt printers from captive portal/web-auth; allow mDNS only if needed; otherwise block broadcast noise.

Customer

We put them on the new SSID and locked channels, but a few still sleep and drop. Any device settings to change?

Technician

Step 3 — Apply settings in printer service mode
• Disable deep sleep / power save for the Wi-Fi module; set Roaming to low/medium so the printer sticks to the nearest AP.
• Lock 5 GHz only if supported; otherwise lock to 2.4 GHz channel 1/6/11 matching the AP plan; turn off band steering on the device.
• Set interface to 802.11n with 20 MHz HT; turn off 40 MHz/80 MHz; keep country code/region correct.
• Save and reboot from service menu so the NIC loads new RF parameters at boot.

Customer

After that, they’re stable but print jobs still pause randomly. Queue type is RAW 9100 from a Windows Server.

Technician

Step 4 — Tune the print path
• On the print server, switch test queues to LPR (queue name lp or vendor-specific) if RAW stalls; or use IPP for better retransmissions.
• Enable bi-directional support only if needed. Disable SNMP status if AP isolation blocks it.
• Keep driver packages minimal — for thermal printers use the vendor driver or Class driver with receipt/boarding-pass template.

Customer

We run mobile check-in carts. When they roll between concourses, printers drop and reconnect to different APs.

Technician

For mobile carts:
• Set minimum RSSI on the SSID so clients roam before links get weak (e.g., kick below −70 dBm).
• Use the same non-DFS 5 GHz channel group across the route; avoid channel switches mid-path.
• Consider 802.11r/k/v fast-roaming if the printer supports it (many do not). If unsupported, keep a conservative power level and overlapping cells.

Customer

After all changes, the Offline status is gone and counters can print boarding passes again. Any final checks?

Technician

Final checks:
• Confirm each printer shows a strong RSSI (−55 to −65 dBm) and a static/DHCP-reserved IP.
• Verify APs near gates use your fixed non-DFS 5 GHz channels or 2.4 GHz 1/6/11 — no auto channel for those cells.
• Document SSID, VLAN, channel, queue type (RAW/LPR/IPP) and keep a laminated card in the counter drawer for quick recovery.

Customer

Perfect — boarding pass printers stay online and print instantly. Thanks!

Technician

Summary: To fix boarding pass printers offline, lock a predictable Wi-Fi channel plan (5 GHz non-DFS or 2.4 GHz 1/6/11), disable band steering for printers, set DHCP reservations, adjust DTIM/RSSI, and apply device settings in service mode. Need help mapping channels or editing SSID policy? Open the chat.

Quick answer: the accepted fix

Accepted fix when boarding pass printers show Offline: create a printer-only SSID/VLAN, lock APs to non-DFS 5 GHz (36/40/44/48) or 2.4 GHz 1/6/11 at 20 MHz, disable band steering for printer MACs, set DHCP reservations, tune DTIM and min RSSI, then apply radio settings in service mode. Use RAW 9100, LPR, or IPP based on stability tests.

FAQ

Step-by-step (Windows / Server)

1. Create printer-only SSID/VLAN; exempt from captive portal; enable WMM.
2. Fix APs to non-DFS 5 GHz (or 2.4 GHz 1/6/11) with 20 MHz width; set target RSSI −55…−65 dBm.
3. Reserve printer IPs in DHCP; update queues (RAW 9100/LPR/IPP) with the correct address.
4. On printers, use service mode to lock band/channel and disable deep sleep; reboot devices.

Note for macOS / CUPS

1. Add printers via IP (IPP or LPR) to the reserved IP; avoid discovery that may switch bands.
2. Test sustained prints; if retries spike, move to 5 GHz non-DFS or tighten RSSI thresholds.

Sources

• Cisco — Wi-Fi design & channel planning
• Meraki — SSID and radio best practices
• Zebra — Wireless printer configuration guides

Matt ● replies in < 1 min

Technician Expert

⭐⭐⭐⭐⭐ Trusted by 27,000+ customers

Alex · Expert's Assistant

Start Chat

5 Tech Support Specialists are online right now.