Why is eSCL support not real?

[funkerwolf]

Why is eSCL support not real? Why doesn’t it work despite the checkbox being enabled in the printer settings via the web-admin interface?
Why can't naps2 detect it? Why are the ports for IP connection not specified anywhere? 

I was just horrified by the fact that HP drivers somehow depend on FDResPub.
Like other services in Windows, they were turned off to reduce broadcast traffic in the organization's local network.
Because of this, the driver installer cannot see the printer directly at the specified IP address! But when adding the printer through Windows, it does print, but scanning is simply impossible to implement.  
Not to mention how the driver installer installs a bunch of bloatware that needs to be removed separately by hand in the form of various plugins, why is this necessary!? 

But surprisingly, the M426-M427 series printers work perfectly with eSCL for some reason.

[Kuroi_Kenshi]

Hi @funkerwolf,

Welcome to the HP Support Community!

Thanks for reaching out!

We're thrilled to have the opportunity to assist you and provide a solution.

I understand your frustration regarding eSCL support on your HP printer, not working as expected despite being enabled in the web interface, and the difficulties with scanning and driver behavior in Windows environments. Here’s a detailed explanation and some guidance.

1. eSCL Support Limitations

eSCL (Apple AirPrint / Epson eSCL standard) is primarily intended for basic printing and AirPrint scanning.

Many HP printers claim eSCL support for printing, but scanning via eSCL is often limited or unsupported on Windows because:

Windows doesn’t natively implement eSCL scanning.

Third-party apps like NAPS2 rely on standard protocols (WSD, TWAIN, or WIA) rather than eSCL.

2. Dependency on FDResPub (Function Discovery Resource Publication)

HP’s “enhanced discovery” and driver installer rely on Windows network discovery services, including FDResPub.

If these services are disabled (to reduce broadcast traffic), the installer cannot detect printers over the network by IP.

However, once the printer is manually added in Windows (via IP), basic printing works, but scanning fails because the eSCL/WSD services aren’t available or fully implemented.

3. Port & Protocol Limitations

eSCL doesn’t use fixed TCP ports in the traditional sense like IPP or LPR. It relies on Bonjour/mDNS for service discovery.

That’s why Windows apps cannot detect it without discovery services running.

HP documentation often does not specify IP ports because eSCL assumes zero-configuration networking (mDNS/Bonjour).

4. Why M426/M427 Series Work

Some newer HP models (e.g., M426/M427) implement full eSCL/WSD scanning support on Windows.

Older or consumer-class printers may only implement partial AirPrint/eSCL, suitable for macOS or iOS scanning, not Windows apps.

5. Driver Installer Behavior

HP drivers install multiple plugins and helper services to support scanning, fax, and network discovery.

While it seems like bloatware, these components are required for:

Network printer discovery.

HP Scan and Smart functionality.

AirPrint and eSCL emulation on Windows.

Disabling unnecessary services is possible, but may break scanning or discovery features.

6. Workarounds for Windows Scanning

Use WIA or TWAIN drivers instead of eSCL.

Access the printer via USB or IP using standard HP drivers for scanning.

For network scanning, ensure FDResPub, SSDP Discovery, and Function Discovery Provider Host services are running.

Alternatively, use HP Smart on iOS/macOS if AirPrint scanning is sufficient.

I hope this helps.

I'm glad I could help! 😊 If this resolved your issue, please mark it as "Accepted Solution" and click "Yes" on "Was this reply helpful?" Your feedback not only keeps us going but also helps others find the solution faster! 👍✨

Take care and have an amazing day ahead! 🚀

Best regards,

[funkerwolf]

I need a solution to the problem, not back and forth. This service can no longer be reactivated because it does not start with error 0x8007273a. WIA/TWAIN is also tied to this service in your drivers for this multifunction device. Please give me the old drivers where they work directly without this service or any other workaround. The M426dw integrates perfectly into NAPS2 via eSCL without these drivers.

I am just amazed at how we have made it to the quarter of the 21st century and such problems are even possible. And you should know how much your drivers have drained our blood, especially with the m1132 and the constant need to disable smart install. 

And surprisingly, m125rnw can somehow work without this service, why is that?

[Kuroi_Kenshi]

Hi @funkerwolf,

Hi! I see the screenshots and understand the issue: your HP Color LaserJet MFP (older or consumer-class model) shows that eSCL (AirPrint) printing works, but scanning via eSCL is not working in Windows, especially with apps like NAPS2, and the FDResPub (Function Discovery Resource Publication) service is disabled, which breaks WIA/TWAIN scanning. You’re asking for a workaround or older drivers that don’t depend on these services.

Here’s a clear approach:

1. Understanding the Limitation

eSCL in older HP models is primarily designed for AirPrint (printing from iOS/macOS).

Windows apps like NAPS2 rely on WIA/TWAIN, which in turn depends on FDResPub, SSDP Discovery, and Function Discovery Provider Host services.

If these services are off, the HP driver installer cannot detect the printer, and scanning fails.

Unlike M426/M427 series, older models do not implement full eSCL scanning support on Windows.

2. Workarounds Without Re-Enabling FDResPub

Option A: Use USB Directly

Connect the printer via USB to the PC.

Use HP TWAIN or WIA drivers for scanning.

This bypasses network discovery and FDResPub entirely.

Option B: Use Standard HP IP Driver

Add printer via TCP/IP (manual IP) in Windows.

Install only “Basic HP Print and Scan” drivers if available.

Avoid installing full-feature HP Smart/Enhanced driver suite. This sometimes allows scanning without depending on FDResPub.

Option C: Use HP Smart on iOS/macOS

If AirPrint scanning is sufficient, scan from HP Smart app on iOS/macOS and save to the PC.

3. Notes

There is no official way to fully enable eSCL scanning on Windows if the printer only supports AirPrint scanning.

NAPS2 cannot detect eSCL printers without Bonjour/mDNS services.

Disabling FDResPub is a common restriction in corporate environments; scanning via standard drivers or USB is usually the only reliable option.

I hope this helps.

I'm glad I could help! 😊 If this resolved your issue, please mark it as "Accepted Solution" and click "Yes" on "Was this reply helpful?" Your feedback not only keeps us going but also helps others find the solution faster! 👍✨

Take care and have an amazing day ahead! 🚀

Best regards,

[funkerwolf · Accepted solution]

The problem was solved by replacing it with the Kyocera FS-1025MFP, which works perfectly over the network and is installed in just a couple of clicks.

[Kuroi_Kenshi]

Hi,

A huge thank you for marking this post as the 'Accepted Solution'! We're thrilled that we could help resolve your issue. 

If you have any more questions or need further assistance, please don't hesitate to ask. We're here to help! 

Thanks again for your confirmation, and we wish you an amazing day ahead! 

Best Regards,