Cloud POS cannot bind printer after Wi‑Fi change — fix discovery & network settings
Joe B.
Expert ★★★★★ 27,853 satisfied customers
Specialities: Cloud POS (Square/Toast/Clover/Lightspeed/Shopify POS), Star Micronics & Epson thermal printers, Networks (DHCP/VLAN), iPad/Android terminals
POS can’t find printer after router/SSID change — Square, Toast, Clover, Lightspeed, Shopify POS
Quick answer: the accepted fix
Accepted fix when POS printer not connecting after Wi‑Fi/router change: verify POS and printer are on the same SSID/subnet, find the printer’s IP address, bind/add by IP in your POS app, then set a DHCP reservation (or static IP). Ensure mDNS/Bonjour is allowed and port 9100/IPP/LPR are open.
POS cannot find printer after SSID/password change
Reconfigure Wi‑Fi printers with the new SSID and WPA2‑PSK; for Ethernet printers, make sure switches and APs bridge the same VLAN. Disable guest isolation and enable multicast/mDNS so discovery for StarPRNT and Epson ePOS works.
How to verify binding & test kitchen tickets
Print the self‑test/configuration page from your Star/Epson to confirm IP and protocol, then from the POS app run Test Print for both Receipt and Kitchen profiles. If prints stall, try RAW 9100 for Star or IPP/LPR for Epson and check firewall rules.
Cloud POS printer — troubleshooting checklist
Most “can’t bind printer” problems trace to IP/subnet mismatches or discovery being blocked.
Quick path: same LAN/subnet → confirm IP via self‑test → add by IP in POS app → reserve IP in DHCP → allow mDNS/Bonjour and TCP 9100 / 631 / 515 → ensure 2.4 GHz support and no client isolation.
Disclaimer: This information is AI-generated and intended for general guidance only. For advice specific to your environment, please consult a verified expert on Whizz-Tech before making decisions.
Getting Started Is Easy
Ask for help, 24/7
Members enjoy round-the-clock access to 12,000+ verified Experts for POS, networking, and thermal printer issues.
Expert will respond in minutes
We match you with a POS networking specialist. Talk, text, or chat — whichever you prefer.
Save time & money
No scheduling hassles or expensive on-site visits. We’ll restore ticket printing fast.
FAQ
Why can’t my Cloud POS bind the printer after a Wi‑Fi change?
Usually the printer and POS are on different subnets/SSIDs, or the printer kept an old static IP. Put both on the same LAN, discover the printer’s IP, and add/bind it by IP with a DHCP reservation.
Square/Toast says “No printers found”. What now?
Discovery (mDNS/Bonjour/StarPRNT) may be blocked. Add the printer by its IP address, ensure TCP 9100 is allowed, and disable client isolation or guest mode.
Receipt printer online but kitchen tickets don’t print
Map the correct printer profile/route in the POS app (Kitchen/Bar). If using different VLANs, allow inter‑VLAN multicast and open 9100/631/515.
Should I use static IP or DHCP reservation?
Use a DHCP reservation in the router — simpler to manage and prevents the printer from drifting to a new IP.
2.4 GHz vs 5 GHz — does it matter?
Many Wi‑Fi printers support only 2.4 GHz. Keep your POS device on the same SSID and allow multicast for discovery.
| Symptom | Likely cause | Quick fix |
|---|---|---|
| POS cannot find printer | Different subnet/VLAN; mDNS blocked | Same LAN/SSID; allow Bonjour; add by IP; reserve IP |
| Printer added, then disappears | DHCP lease changed | Create DHCP reservation or set static IP |
| Kitchen tickets not printing | Wrong profile/port; firewall rules | Map kitchen route; open 9100/631/515; use RAW/IPP/LPR per brand |
| Wi‑Fi printer not joining | Old SSID/password; 5 GHz only | Reconfigure SSID (2.4 GHz); WPA2‑PSK; disable isolation |
Step‑by‑step (Square/Lightspeed/Toast)
- Print the self‑test from Star/Epson to get the current IP and network mode.
- Confirm POS terminal and printer share the same subnet (first three octets match).
- In the POS app, Add/Bind printer by IP; choose the correct protocol (StarPRNT/RAW 9100 for Star; IPP/LPR for Epson).
- In your router, create a DHCP reservation for the printer’s MAC.
- Allow mDNS/Bonjour and open TCP 9100, 631, 515; disable client isolation.
Step‑by‑step (Wi‑Fi Epson/Star on iPad/Android)
- Reset to AP mode and join the printer’s temporary network.
- Configure new SSID/WPA2‑PSK and set DHCP/static IP in the web config.
- Reconnect tablet to the venue Wi‑Fi (2.4 GHz), then add the printer in the POS app by IP.
- Run a Test Print for receipt and kitchen profiles.
Sources
- Square — Connect a network receipt printer
- Toast — Printer setup & troubleshooting
- Star Micronics — StarPRNT & mC‑Print guides
- Epson — ePOS/TM‑m30/TM‑T88VI support
- Shopify POS — Receipt printer setup
Filed under: Label / thermal / POS / shipping labels
Related articles
- Revel POS prints restaurant modifiers tiny — font rule
- Toast POS Kitchen Dockets Losing Text at the Edge — What the DPI Setting Is Cutting Off and How to Get Full Tickets Printing
- QuickBooks POS thermal tax prints blurry — DPI & driver checks you can do safely
- Odoo POS receipts print giant text — ESC/POS scaling
- Clover POS thermal prints reversed characters — encoding toggle
- Shopify POS to Star/Bixolon over Bluetooth — pairing mode & profile selection
- 58mm POS receipt truncates taxes on long orders — fix totals & template width
- Toast POS kitchen printer not printing — port/protocol fix