Hi,
I’m experiencing an ESCL scanning issue with NAPS2 8.3.2 and an Epson XP-830 Series scanner.
The scanner’s correct IP address is:
192.168.2.86
The scanner advertises itself via Bonjour/mDNS as:
EPSON655ACB.local → 192.168.2.86
Windows DNS resolution is also correct:
Resolve-DnsName EPSON655ACB.local
EPSON655ACB.local A 192.168.2.86
However, during ESCL discovery NAPS2 logs:
ARecord EPSON655ACB.local ... 192.168.2.86
SRVRecord ... 443 EPSON655ACB.local
...
Discovered ESCL Service:
ipv4 192.168.2.86
host EPSON655ACB.local
port 443
It also reports:
endpoint 192.168.0.1:5353
NAPS2 subsequently constructs the ESCL connection URI incorrectly as:
https://192.168.0.1:443/eSCL
instead of:
https://192.168.2.86:443/eSCL
This results in:
System.Xml.XmlException:
'src' is an unexpected token.
The expected token is '='.
Line 1, position 670.
The HTTP GET returns GET OK, but NAPS2 is contacting the wrong host.
Important observation
The NAPS2 profile initially contains the correct URI:
https://192.168.2.86:443/eSCL
However, after starting a scan, NAPS2 changes it back to:
https://192.168.0.1:443/eSCL
This happens even after deleting/recreating the NAPS2 profile and configuration.
Suspected cause
The mDNS RemoteEndpoint is:
192.168.0.1:5353
while the scanner's actual IPv4 address is:
192.168.2.86
It appears that NAPS2 8.3.2 may be using the mDNS responder's RemoteEndpoint when constructing the ESCL connection URI, instead of using the discovered scanner IPv4 address (IpV4).
This would explain why the profile is automatically rewritten to:
https://192.168.0.1:443/eSCL
even though the scanner is correctly discovered as 192.168.2.86.
Could you please check whether RemoteEndpoint is intentionally used when constructing the ESCL connection URI? In this case it appears to represent the mDNS responder rather than the scanner itself.
Thanks!
Hi,
I’m experiencing an ESCL scanning issue with NAPS2 8.3.2 and an Epson XP-830 Series scanner.
The scanner’s correct IP address is:
192.168.2.86
The scanner advertises itself via Bonjour/mDNS as:
EPSON655ACB.local → 192.168.2.86
Windows DNS resolution is also correct:
Resolve-DnsName EPSON655ACB.local
EPSON655ACB.local A 192.168.2.86
However, during ESCL discovery NAPS2 logs:
ARecord EPSON655ACB.local ... 192.168.2.86
SRVRecord ... 443 EPSON655ACB.local
...
Discovered ESCL Service:
ipv4 192.168.2.86
host EPSON655ACB.local
port 443
It also reports:
endpoint 192.168.0.1:5353
NAPS2 subsequently constructs the ESCL connection URI incorrectly as:
https://192.168.0.1:443/eSCL
instead of:
https://192.168.2.86:443/eSCL
This results in:
System.Xml.XmlException:
'src' is an unexpected token.
The expected token is '='.
Line 1, position 670.
The HTTP GET returns GET OK, but NAPS2 is contacting the wrong host.
Important observation
The NAPS2 profile initially contains the correct URI:
https://192.168.2.86:443/eSCL
However, after starting a scan, NAPS2 changes it back to:
https://192.168.0.1:443/eSCL
This happens even after deleting/recreating the NAPS2 profile and configuration.
Suspected cause
The mDNS RemoteEndpoint is:
192.168.0.1:5353
while the scanner's actual IPv4 address is:
192.168.2.86
It appears that NAPS2 8.3.2 may be using the mDNS responder's RemoteEndpoint when constructing the ESCL connection URI, instead of using the discovered scanner IPv4 address (IpV4).
This would explain why the profile is automatically rewritten to:
https://192.168.0.1:443/eSCL
even though the scanner is correctly discovered as 192.168.2.86.
Could you please check whether RemoteEndpoint is intentionally used when constructing the ESCL connection URI? In this case it appears to represent the mDNS responder rather than the scanner itself.
Thanks!