# Epson TM-T82 Network Printing: Port 9100 Troubleshooting

> Why a network receipt printer stops printing, and how to prove where: port 9100 sessions, half-open sockets, timeouts and an idempotent print queue.

URL: https://www.matthewswong.com/en/blog/epson-tm-t82-network-printing-troubleshooting/

- Author: Matthews Wong (https://www.matthewswong.com/en/about/)
- Published: 2026-08-18
- Updated: 2026-08-18
- Category: Backend

> **Key takeaway:** A network TM printer listens on TCP port 9100 and accepts one raw print session at a time. Most field failures are a second client holding that session, a half-open socket after a power cut, or a DHCP lease that moved the printer — all of which are diagnosable in under a minute with netcat and ss.

Moving a receipt printer onto the network solves a real problem: one printer, several tills, no cable across the counter. It also replaces a wire you can see with a set of failure modes you cannot, and the first time a shop calls to say printing stopped, none of the usual web debugging instincts help.

This is the troubleshooting order I follow now, from the layer that fails most often to the one that fails least, plus the queue design that makes any of these failures survivable instead of embarrassing.

## What port 9100 actually is

A network TM printer exposes a raw print port on TCP 9100 — the same convention HP established with JetDirect and that virtually every network printer now follows. There is no protocol on top: you open a TCP connection, you write ESC/POS bytes, the printer prints them, and closing the connection signals the end of the job. That simplicity is the appeal and the trap.

The trap is that a raw port has no sessions, no authentication and, on most firmware, no queue. The printer serves one connection; a second client trying to print at the same moment is either refused or left waiting, and your application sees a connection that hangs rather than an error that explains itself.

*The shape of network printing: several clients, one server that can genuinely serve one of them at a time. Every port 9100 problem I have debugged reduces to a violation of the constraint in this diagram. Diagram:*

## The four checks that find most faults

Before touching the application, prove which layer is broken. Each of these takes seconds and eliminates a whole category of cause.

- Is the printer reachable at all? An ARP entry proves it is on this subnet; no entry usually means the address changed or the printer is on the guest network.
- Is the port open? A three-second netcat probe distinguishes a powered-off printer from a busy one and from a firewall rule.
- Can it print without your software? Piping a short byte string plus a cut straight into the port tells you whether the fault is above or below your application.
- Who else is connected? A single established connection from an unexpected host explains almost every intermittent hang, and it is usually an old print queue on a manager's PC that nobody remembers configuring.

In my experience the fourth check finds the problem more often than the other three combined. Shops accumulate print configurations: a spare till, a laptop set up during a trial, a Windows queue that retries forever. Any one of them can hold the session your POS needs.

> Never leave a network receipt printer on DHCP. A lease renewal after a power cut moves the printer to a new address, every till fails at once, and the symptom is indistinguishable from a dead printer. Reserve the address on the router or set it statically, and write it on a label stuck to the printer.

## The half-open socket, and why writes succeed into nothing

The most confusing failure is the one where your code reports success and no paper moves. It happens when the printer disappears — unplugged, power-cycled, switch rebooted — while your process still holds a TCP connection. Nothing informs the operating system, so writes go into a send buffer and return happily until the connection eventually times out, minutes later.

Two habits eliminate it. Open a connection per receipt rather than holding one open, so a dead connection is discarded within one sale rather than persisting all day. And set explicit timeouts and keepalive on the socket, so the kernel probes the peer instead of trusting a link that no longer exists.

## A troubleshooting order that converges

When a shop calls, this sequence gets to a cause in roughly five minutes without needing to be on site.

1. Confirm the address. Ask someone to read the label, then check the printer's own network status page or self test to see what it thinks its address is.
2. Probe the port from the till that is failing, not from your laptop. Different VLAN, different result — and that difference is itself the diagnosis.
3. Print a test string straight to the port. If paper moves, the printer and network are fine and the bug is in the application or its queue.
4. List established connections to port 9100 from every machine in the shop. Kill the stranger.
5. Only then read your application logs, which are now the last remaining suspect rather than the first place to guess.

Writing this sequence into the support runbook did more for our print reliability than any code change, because it stopped the reflex of restarting the POS software as the first response to a network fault.

*Networked counter hardware multiplies the number of devices sharing one small shop network. Each one is another DHCP client, another VLAN question, and another candidate for the connection that is holding your printer's single session. Photo:*

## The queue that makes failures survivable

Given that the network will fail sometimes, the design goal is not to prevent it but to ensure a failed print never loses a sale and never prints twice. That is a database problem, not a printing problem, and the schema below is the whole idea.

The unique constraint on the payment identifier is the load-bearing part. It makes a retry safe, which in turn makes aggressive retrying safe, which is what lets a shop keep selling through a two-minute network blip and get every receipt afterwards.

> Expose the queue depth and the age of the oldest unprinted job as a health metric, and alert on the age rather than the depth. A shop with twelve queued receipts at closing time is fine; a shop with one receipt that has been queued for six minutes has a printer nobody has noticed is offline.

## Choosing between network and local

Network printing is not automatically the better choice. Three situations where I still run USB or serial deliberately.

- One till, one printer, one metre apart. A cable removes an entire class of failure for the price of a cable.
- A shop whose network is a consumer router shared with customer wifi. Print traffic is trivial, but the router's DHCP behaviour under load is not.
- Kitchen printers in a hot, damp environment where a network switch is one more thing to fail. Serial is unfashionable and extremely difficult to kill.

Port 9100 is a beautifully simple interface with one hard rule — one session at a time — and most network printing incidents are that rule being broken by something nobody remembered installing. Diagnose from the network up rather than the application down, keep a per-receipt connection with real timeouts, and put an idempotent queue behind it so the worst case is a delay instead of a lost receipt.

## Sources and further reading

- Epson TM-T82X Technical Reference Guide (network setup, PDF)
- Epson ePOS SDK and Server Direct Print overview
- Epson ESC/POS Command Reference (official command specification)
- Wikipedia: JetDirect and the port 9100 raw printing convention

## Source links

- https://download4.epson.biz/sec_pubs/bs/pdf/TM-T82X_trg_en_revF.pdf
- https://download4.epson.biz/sec_pubs/pos/reference_en/technology/epson_epos_sdk.html
- https://reference.epson-biz.com/modules/ref_escpos/index.php
- https://en.wikipedia.org/wiki/JetDirect

## FAQ

### What is port 9100 on a network receipt printer?

It is the raw print port, the convention HP introduced with JetDirect and that most network printers follow. There is no protocol on top: you open a TCP connection, write ESC/POS bytes, and close the connection to signal end of job. It has no authentication and, on most firmware, no queue.

### Why does the printer accept a connection but print nothing?

Usually a half-open socket. If the printer was unplugged or power-cycled while your process held a connection, writes go into a send buffer and succeed for minutes before the connection times out. Open one connection per receipt, set explicit connect and write timeouts, and enable keepalive so the kernel probes the peer.

### Can two tills print to the same network printer at once?

Not simultaneously. A raw print port serves one session at a time, so a second client is refused or left waiting. In practice the most common cause of intermittent hangs is a forgotten print queue on another machine holding the session — list established connections to port 9100 across the shop before blaming your application.

### Should a network receipt printer use DHCP?

No. A lease renewal after a power cut can move the printer to a new address and every till fails at once, with a symptom indistinguishable from a dead printer. Reserve the address on the router or configure it statically, and write it on a label attached to the printer.

### How do I make a network print failure survivable?

Queue receipts in the database with a unique constraint on the payment id. That single constraint makes retries idempotent, which makes aggressive retrying safe, so a shop can keep selling through a network blip and collect every receipt afterwards. Alert on the age of the oldest unprinted job rather than the queue depth.

---

- HTML version: https://www.matthewswong.com/en/blog/epson-tm-t82-network-printing-troubleshooting/
- Bahasa Indonesia: https://www.matthewswong.com/id/blog/epson-tm-t82-network-printing-troubleshooting/
- Site index for agents: https://www.matthewswong.com/llms.txt
- Sitemap: https://www.matthewswong.com/sitemap.xml
- API description (OpenAPI): https://www.matthewswong.com/openapi.json
