USA high-intent model guide
Epson EcoTank ET-2800: Offline or Wi-Fi Not Working
This guide focuses specifically on the EcoTank ET-2800, a wireless ink-tank all-in-one, when it is offline or Wi-Fi. Start by separating a printer-side fault from the Wi-Fi / network queue or network path before reinstalling or resetting anything.
Direct answer
What this usually means
The printer is powered on but cannot be discovered reliably, appears Offline, or loses the wireless path used by computers and phones.
Most likely causes
- Printer and computer are on different or isolated networks
- Router name or password changed
- The printer received a new IP address
- A stale queue still points at an old network path
Safe fix order
- Check the printer wireless/network status without resetting it.
- Confirm the computer or phone and printer use the same normal LAN, not guest Wi-Fi.
- Print or view the printer network report when the model supports it and note the current address.
- Restart the printer and client device before changing router settings.
- Use the exact manufacturer setup workflow if the printer must be rejoined to Wi-Fi.
Model-specific context
Why the EcoTank ET-2800 path matters
Epson describes the ET-2800 as a wireless EcoTank all-in-one and provides model-specific support and setup resources.
Do not assume instructions for a similarly named model are interchangeable. Confirm the full model before drivers, firmware, supplies or resets.
OS / connection context
Wi-Fi / network
This page targets offline or Wi-Fi on Wi-Fi / network. The printer itself should be checked for a physical or consumable alert before software changes are made.
Printer Offline: 3 Safe Checks
A short original walkthrough of printer status, local network and print-queue checks before driver reinstallation.
Official sources
Use these sources to verify model-specific procedures, current drivers and platform behavior.
Related routes for this exact problem
Need support with this exact EcoTank ET-2800 issue?
The support form can carry this page context into the request.
Start contextual support