Epson Push-to-Scan not working

Hello, @akgt94

Let’s see what we can do to help with your Epson WorkForce device.

After a bit of research, the first step you should try is to reinstall the Epson Scan.  Then, make sure it is not set to Compatibility mode.  Finally, configure Epson Scan for your connection.

We also found information to support launching the Epson Scan before scanning with the start button.  Document Capture Pro for Windows does not support starting a scan from the scanner button over a wireless network.

We did also check on the possibility of the router blocking the ports needed for discovery and found it uses UDP port 2968.  Here are the steps for Port Forwarding, just choose your router model for device-specific instructions.

We hope this information is useful. Let us know if you have any other questions,

Meaghan, AT&T Community Specialist

Oops, I missed this. I have a new 5268AC gateway and I am still trying to get it to work.

I sort of understand the answer, but can't figure out the implementation.  Either I got the implementation wrong, or that isn't the solution.

For clarification, on the computers, the Epson Event Manager sees the scanner. Epson Scan software can pull scans from the scanner. But on the Epson control panel, "Scan to PC" is unable to discover any computers on the LAN.

In the Applications, Pinholes and DMZ page,

• I chose the printer
• added a new user-defined application called "Epson"
• Defined it to UDP ports 2968-2968
• Added the "Epson" application to the "printer" "computer"
• Confirmed that when you choose the printer in "select a computer", "Epson" is listed in its hosted applications list.

The Scan to PC function on the printer's control panel still can't discover any computers on the LAN.  I power-cycled the printer and that didn't help. Turned off Windows firewall and the printer still can't discover any computers on the LAN.

I have some other notes from Epson support.  I didn't get enough information to know which devices needed them and whether they were incoming or outgoing.  Not sure if others are being blocked on the LAN by the gateway.

• TCP 3620
• TCP 3621
• UDP 3629
• (TBD) 2968
• (TBD) 1865
• (TBD) 3298

... what's also confusing about this answer is I understand port forwarding to allow communication between a computer on the LAN and a computer outside the LAN.  I've not seen port forwarding used in the context to allow two computers inside the LAN to communicate with each other.

I monitored traffic between printer/scanner and computer in a second router where it is possible push-to-scan works. Then I compare the traffic data with the router where push-to-scan does not work. I have found this IGMP issue.  It is necessary disable IGMP snooping on router.

The issue was solved by disabling IGMP Snooping at router.
I replace router by another model. Push to Scan works. Then wireshark was used to capture network traffic between computer and epson printer/scanner.
It was verified several packets IGMPv3  and process forming multicast groups. These IGMP  packets and multicast grouping forming process does not appear.

Then when I disable IGMP snooping, push-to-scan works
. In fact there  was any blocking tcp/ud port 2968, It is an IGMP issue. 

I'm not sure where you disabled IGMP snooping, because AT&T Gateways do not have such a feature, and the IGMPv3 processing that they do cannot be disabled.

@andregmedeiros it is not necessary, or helpful, to post your observations that are irrelevant to AT&T customers on multiple threads.  I have removed the most recent duplicated information from this thread. 

Further action, which may including blocking your account, may be taken if you continue to violate forum guidelines (to whit: (a) posting content that is not relevant to AT&T services, and (b) making duplicate posts).  You were offered an opportunity to read these guidelines and agreed to follow them when you created your community account.

Closing thread based on age and incorrect information.