You hit print. The Epson spits out Communication Error on its LCD, or Windows throws 0x0000011b when the job fails. The printer itself is fine. Every time I've seen this in the last five years, it's the network layer — the printer and the computer stopped agreeing on where the printer lives. The fix order below goes from 30 seconds to 15 minutes. Stop as soon as your job prints.
What's actually happening: the printer lost its IP lease, or the router moved it, or the PC cached the old address. Epson's driver keeps talking to the ghost of the old IP. That's the error.
Fix 1 — The 30-second fix
Power-cycle in the right order. This matters more than people think.
- Turn the printer off with its physical power button. Wait 30 seconds. Not 5 — 30. The Wi-Fi module inside needs to fully release the DHCP lease.
- While it's off, restart your router. Unplug it, count to 15, plug it back in. Wait for the 2.4GHz light to go solid.
- Turn the printer back on. Wait for the Wi-Fi icon to stop blinking.
- Print a network status sheet: on most Epson models hold the Wi-Fi button until both lights flash, release, then press Start. On ET-2720 / ET-2760, it's Network Status from the home menu.
That sheet gives you the printer's current IP. If it's different from what your PC thinks, that's your whole problem. Fix 2 handles it.
About 40% of these calls end here. The router had reassigned the IP while the printer was asleep — Epson's deep sleep after 5 minutes on battery-less models is aggressive — and the driver was knocking on the wrong door.
Fix 2 — The 5-minute fix: pin the IP
DHCP is convenient and hostile. Your router hands the Epson a new IP every time the lease expires (default 24 hours on most ISP routers), and the Windows/Mac driver keeps the old one. The real fix isn't "reinstall the driver." It's giving the printer a fixed address.
Two ways. Pick one.
Option A — DHCP reservation on the router (best)
- Log into your router. Common addresses:
192.168.1.1,192.168.0.1, or192.168.50.1for Asus. - Find DHCP Reservation or Static Lease. On TP-Link it's under Network > DHCP > Address Reservation. On Asus it's under LAN > DHCP Server > Manually Assigned IP.
- Grab the printer's MAC from the network status sheet you just printed. Format looks like
A4:5E:60:xx:xx:xx. - Assign it an IP outside the DHCP pool. If your pool is .100–.200, give the printer .50.
Option B — Static IP on the printer
On the printer's LCD: Settings > Network Settings > Wi-Fi Setup > Manual. Enter your SSID, pick Manual for IP, and set something like 192.168.1.50, subnet 255.255.255.0, gateway 192.168.1.1. Reboot.
Then on the PC, delete the old printer and re-add it by IP. Windows: Add printer > The printer that I want isn't listed > Add a printer using TCP/IP address. Enter the pinned IP. Mac: System Settings > Printers & Scanners > + > IP tab, protocol HP Jetdirect – Socket, port 9100.
This one fix eliminates 80% of recurring Communication Errors. I've seen the same WF-3820 throw this error weekly for a year at a small office, and a DHCP reservation ended it permanently.
Fix 3 — The 15-minute fix: band and firewall surgery
If the printer still drops off, you've got one of three things going on.
2.4GHz vs 5GHz band steering
Every Epson consumer model — ET, XP, WF series — is 2.4GHz only. If your router uses a single SSID for both bands (band steering), the printer sometimes tries to associate with 5GHz and fails silently. Split the bands in the router admin. Name them MyWiFi and MyWiFi-5G. Connect the printer to the 2.4GHz one only.
That single change fixes Communication Errors on Eero, Google Nest Wifi, and any ISP combo router that ships with band steering on by default. Which is most of them since 2019.
Windows firewall and Bonjour
Windows Defender sometimes blocks the Epson's discovery port. Open an admin Command Prompt and run:
netsh advfirewall firewall add rule name="Epson RAW Print" dir=in action=allow protocol=TCP localport=9100Also allow UDP 3289 — that's EpsonNet's discovery port. Without it, the status monitor in Windows shows the printer as offline even when it's reachable.
Router client isolation / AP isolation
Guest Wi-Fi networks don't talk to the LAN. If you moved the printer to a guest SSID during setup, that's your problem. Same for routers with AP Isolation or Client Isolation enabled. Turn it off for the main network.
MAC address filtering
If you enabled it and forgot — and everyone does — check the router's MAC filter list. Add the printer's MAC with a clear label. Twenty seconds of work, saves an hour of confusion later.
When the printer itself is the problem
Two hardware things to rule out before you spend more time on the network.
- Wi-Fi module gone bad. If the network status sheet shows no SSID detected even after a reset, or the Wi-Fi LED never comes on, the radio board is dead. Happens on ET-2720 units past 3 years old with heat exposure near a window.
- Firmware corruption after a failed update. Epson pushed a bad update to WF-2830 units in early 2022 that broke Wi-Fi on some serial ranges. Check Settings > Firmware Update and let it finish over USB if Wi-Fi won't hold.
If both check out and the printer still fails, connect it via USB once. If USB works, it's the network — go back to Fix 2. If USB also fails with a Communication Error, the mainboard or formatter board is the culprit and you're looking at a repair quote, not a settings problem.
The quick version
Power-cycle in order. Pin the IP with a DHCP reservation. Split your Wi-Fi bands so the printer only sees 2.4GHz. Open TCP 9100 and UDP 3289 on Windows. Skip everything else — reinstalling the driver, "compatibility mode," and running Epson's network setup wizard a fourth time won't help if the IP keeps moving.