Repair GuideJun 14, 2026Β·11 min read

POS Terminal Offline or Won't Connect? Network Troubleshooting from Link Light to Processor

A field guide to a POS terminal that's offline or can't connect β€” the connection chain from terminal to switch to ISP to processor, link-light and IP checks, a reboot-in-order routine, isolating local vs internet vs processor faults, and Wi-Fi vs wired.

The fast triage

An β€œoffline” POS panics a busy counter, but the fault is rarely the terminal itself β€” it’s one broken link in a chain that runs from the terminal, through your switch and router, out to the internet, and on to the payment processor. Find the broken link by working outward:

CheckWhat it tells you
1. Link lights at terminal & switchNo light = cable or port β€” a physical breakβ€”
2. Terminal has a valid IPNo/odd IP = DHCP, conflict or configβ€”
3. Another device on the LAN online?Others offline too = router/modem/ISPβ€”
4. Internet works but cards failProcessor/gateway or a blocked portβ€”
5. Reboot in order; isolate; escalateConfirms the link and who to callβ€”
Work the chain outward: cable β†’ local network β†’ internet β†’ processor. The first broken link is your fault domain.

The connection chain (where it breaks)

A card transaction crosses five links. Knowing the chain tells you which links a symptom rules in or out:

POSterminalSwitch /routerModemInternetISPProcessorgatewayyour gearyour ISPthird party
The connection chain. An 'offline' POS is a break somewhere along it β€” diagnosis is finding which link, from the cable outward.
  • Terminal ↔ switch: cable, port, link light, the terminal’s NIC/interface card.
  • Switch/router/modem: local network, IP addressing, the device being up.
  • Internet/ISP: your line β€” affects every device, not just the POS.
  • Processor/gateway: the payment back-end β€” internet works but cards still fail.

Reading the symptom

Match the symptom to narrow which link to check first:

SymptomMost likely link
No link light at the terminalCable / port / NIC β€” physicalβ€”
Terminal has no/odd IP (169.254.x.x)DHCP not reachable, or IP conflictβ€”
Whole site has no internetModem/router or ISP outageβ€”
Only the POS is offline, others fineTerminal config, or processor/gatewayβ€”
Internet OK but cards decline/timeoutProcessor/gateway, or a blocked firewall portβ€”
Drops offline intermittently (Wi-Fi)Signal/interference β€” consider wiredβ€”
A self-assigned 169.254 address means no DHCP; 'only the POS' points at the terminal or the processor, not your internet.

Step-by-step: isolate the broken link

Work the sequence in order. Each step proves one link good so you stop guessing:

  1. 1

    Check the physical link

    Confirm the cable is seated and the link lights are on at both the terminal and the switch/router. Reseat or swap the cable; try another switch port. No light = stop here and fix the physical layer.
  2. 2

    Reboot in order

    Power-cycle from the internet inward: modem β†’ (sync) β†’ router β†’ switch β†’ POS terminal. This gives each device a fresh address from the one upstream.
  3. 3

    Check the terminal's IP

    Confirm a valid IP, gateway and DNS (not a 169.254 self-assigned address). For a fixed terminal, a static IP or DHCP reservation avoids address churn.
  4. 4

    Test internet from another device

    Put a phone or PC on the same network. If it has no internet, the fault is router/modem/ISP. If it’s fine, the fault is the POS or the processor.
  5. 5

    Isolate the processor / ports

    Internet works but cards still fail? Check the processor/gateway status, and that the firewall allows your processor’s required ports/addresses. Then call the processor if needed.
    Caution: Don't reconfigure firewall rules blindly β€” confirm the exact ports/addresses your processor documents.
The full isolation sequence β€” physical first, then addressing, then internet, then processor.

Wi-Fi vs wired for a POS

How a terminal connects shapes how often it drops. For a fixed till, wired wins; Wi-Fi is for mobility:

Wired EthernetWi-Fi
ReliabilityHigh, steadyVariable (signal, congestion)
Latency for card authLow, consistentHigher, more jitter
Interference / dead spotsNonePossible
Best forFixed tills, ATMsTablet / mobile POS
Intermittent-offline fixβ€”Often: move to wired
A fixed terminal that drops offline on Wi-Fi is the classic case for switching to wired Ethernet.

Parts, and when it's not your network

Most network faults are config or the cable, not a part β€” but when hardware is the cause, here’s what to check and source:

ItemNote
Network cableSwap-test first; the cheapest and most common faultβ€”
Terminal NIC / interface cardConfirm with a known-good cable/port before replacingβ€”
Switch / router portTry a different port; a dead port mimics a dead NICβ€”
Processor / ISP (not a part)Internet-OK-but-cards-fail = call them, don't swap partsβ€”
Cable β†’ port β†’ NIC, in that order. 'Internet works but cards fail' is rarely something you can fix by replacing a part.

Browse network and interface parts in our interface cards and cables & connectors categories, and boards in mainboards. If the printer (not the terminal) is the thing that won’t connect, see our printer interface & connectivity guide; if the terminal won’t boot at all, the won’t-boot guide. Tell us your terminal model and we’ll match the right interface card or cable.

Frequently Asked Questions

My POS says it's offline β€” where do I start?
Start at the physical layer and work outward. Check the network cable and the link light at both the terminal and the switch/router; no light means a cable or port problem. Then confirm the terminal has a valid IP address, that other devices on the same network can reach the internet, and only then suspect the payment processor or gateway. Working outward from cable β†’ local network β†’ internet β†’ processor finds the broken link fastest.
How do I tell if it's my network or the payment processor that's down?
Test whether other devices on the same network have internet. If your phone or a back-office PC on the same Wi-Fi/LAN browses fine but only the POS can't transact, the problem is the POS or the processor/gateway, not your internet. If nothing on the network has internet, it's your router/modem or ISP. If everything has internet but card transactions still fail, it's almost certainly the processor or gateway β€” check their status page or call them.
What's the right order to reboot things?
Power-cycle from the internet inward: modem first, wait for it to fully sync, then the router, then the network switch, then the POS terminal. Rebooting in that order lets each device get a fresh address and connection from the one upstream of it. Rebooting the POS alone rarely helps if the problem is upstream β€” and rebooting everything at once can leave devices with stale addresses.
Should my POS use a static IP or DHCP?
Either works, but a fixed device like a POS terminal or a network receipt printer is often more reliable on a static IP (or a DHCP reservation), so its address never changes and the POS software can always find it. DHCP is simpler to set up but can hand out a new address after a reboot, which breaks a hard-coded printer or terminal reference. If your POS keeps 'losing' a printer or going offline after power cuts, a static IP/reservation usually fixes it.
Is Wi-Fi or wired Ethernet better for a POS terminal?
Wired Ethernet is more reliable for a fixed till β€” no signal drops, no interference, and steadier latency for card authorization. Wi-Fi is fine for tablet/mobile POS and where cabling isn't practical, but it's more exposed to congestion, dead spots and interference. If a fixed terminal drops offline intermittently on Wi-Fi, moving it to wired Ethernet is often the single most effective fix.
Could a firewall or the terminal's network card be the problem?
Yes. A firewall (on the router or network) can block the ports the POS needs to reach its gateway, so the terminal has internet but still can't transact β€” check that your processor's required ports/addresses are allowed. Less commonly, the terminal's own network interface (onboard NIC or an interface card) or its cable has failed; test the same cable/port with a known-good device to confirm before replacing the card.

Sources & further reading

  1. Troubleshoot a POS that's offline / network issues β€” Square
  2. Network & Connectivity Troubleshooting for POS β€” Lightspeed Retail
  3. Troubleshoot Network Connectivity (basics) β€” Cisco
  4. Static IP vs DHCP β€” which to use β€” TP-Link
  5. Wired vs Wireless for Business Devices β€” Intel

Related guides

Related categories

Featured parts in this guide

Need the parts mentioned in this guide?

Genuine OEM and quality-tested aftermarket parts for IBM, Toshiba, NCR, Diebold, Wincor and Hyosung systems β€” with worldwide shipping.