Apart from this one significant problem, the machine seems to be very
good, but I'm grinding my teeth about this issue. Can anyone help?
Java Jive wrote:
Apart from this one significant problem, the machine seems to be very
good, but I'm grinding my teeth about this issue. Can anyone help?
I've got to "look at" a Xerox MFP that got upset by an updated HP
driver, it'll be in a Widows environment, but if I find anything (esp
port numbers) that ought to apply to linux, I'll let you know ...
+ After installing the Debian driver ...
https://www.support.xerox.com/en-gb/product/xerox-c315-multifunction-printer/content/146849
.... I can print from Ubuntu 18, but can NOT scan from it, and this
problem, which has consumed a large proportion of the three days since delivery, is the subject of the rest of this post ...
Apparently this is quite a common problem with these MFP's, regardless
of make. I have been reading posts over the last 5-10 years of others outlining similar problems with makes including HP, Samsung, etc. Here
are some examples of what I've been trawling through:
https://askubuntu.com/questions/1100908/xerox-workcenter-3215-scanner-isnt-recognized-on-18-04
https://unix.stackexchange.com/questions/71849/can-a-linux-computer-receive-scanned-images-from-a-scanner-using-wsd-web-servic
https://askubuntu.com/questions/1262946/ubuntu-20-04-network-printer-works-but-scanner-not-detected
This is a summary of what I've tried so far:
I wondered if the firewall was preventing communication with the MFP, at least as far as TCP/IP ports used for scanning were concerned, but
disabling it with ...
ufw disable
.... made no difference, the MFP scanner still couldn't be found.
I've tried installing libusb-0.1-4 as described in the first post above,
but it made no difference. Indeed, superficially at least, why would
it, when my MFP is connected via the ethernet, not USB as was his? But
I thought I might as well try it anyway.
Also from that post, the debug environment setting SANE_DLL_DEBUG=5
doesn't seem to make any difference, for example I don't seem to get anything extra, let alone useful, out of the test command mentioned in
some of the posts that I've read. The output from ...
SANE_DLL_DEBUG=5 scanimage -L
.... is exactly the same as from ...
scanimage -L
.... ie nada/zilch found.
Both the next two posts describe editing a file in /etc/sane.d,
epkowa.conf in the first, and xerox_mfg.conf in the second, to add lines
of the form ...
# Xerox (R) C315 MFP
tcp <ip-address> [<port>]
.... as per ...
http://www.sane-project.org/man/sane-xerox_mfp.5.html
.... which I have done, trying both without and with several specific
port numbers, all with the firewall still disabled and rebooting after
each edit, but nothing has worked.
The MFP's IP address is fixed by the router, is displayed on the
printer's interface, and pinging it from Ubuntu gets the expected
response, so there is no possibility of that being wrong, which just
leaves the question of which port(s) to try ...
Searching this site ...
https://www.speedguide.net/ports.php
.... for ports mentioning Xerox gets 9 hits, of which only one, 2157,
looked likely, but that didn't work.
Searching the firewall rules on a W7 machine which is able to scan from
the MFP finds ports 3702, 5357, & 5358 are involved in WSD
communications, but none of those worked either.
Printing out the settings from the MFP &/or loading them via its web interface reveals that there is the setting ...
Settings, Network/Ports, Scan to PC Port Range: 9751:12000
.... but 9751 did work either. Moreover, it seems to disagree with ...
Settings, Network/Ports, TCP/IP, TCP/IP Port Access
.... which lists the port status, open or closed, of a number of ports
on the MFP, but the above range is not listed as being in either state. However, that same list also reveals that the following are open ...
TCP 65001 WS-Discovery
TCP 65004 WSD Scan Service
.... but neither of those worked either.
Apart from this one significant problem, the machine seems to be very
good, but I'm grinding my teeth about this issue. Can anyone help?
Further information ...
Further information ...
On 10/03/2024 20:05, Java Jive wrote:
Further information ...
At last I've managed to obtain some debugging information which shows that the MFP is actually being contacted, but is not responding in the manner expected. This page gives a different debugging environment variable, which, unlike the previous one, works:
https://manpages.ubuntu.com/manpages/xenial/man5/sane-xerox_mfp.5.html
"<user>@<machine>:home# SANE_DEBUG_XEROX_MFP=4 scanimage -L
[sanei_debug] Setting debug level of xerox_mfp to 4.
[xerox_mfp] sane_init: Xerox backend (build 13), version != null, authorize != null
[xerox_mfp] sane_xerox_mfp_get_devices: 0x7fff0450b3d0, 0
[xerox_mfp] list_one_device: tcp 192.168.1.127
[xerox_mfp] tcp_dev_open: open tcp 192.168.1.127
[xerox_mfp] :: dev_command(INQUIRY[0x12], 70)
[xerox_mfp] tcp_dev_request: wait for 1024 bytes
[xerox_mfp] tcp_dev_request: error Resource temporarily unavailable, bytes requested: 1024, bytes read: 0
[xerox_mfp] dev_command: illegal response len 0, need 70
[xerox_mfp] tcp_dev_close: closing dev 0x563011ff3d30
[xerox_mfp] list_one_device: dev_inquiry(tcp 192.168.1.127): Error during device I/O
No scanners were identified. If you were expecting something different,
check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation
which came with this software (README, FAQ, manpages)."
There seems to be a discrepancy in the above as to whether the expected response should have been 70 bytes long, or 1024, but anyway it seems from the above that the MFP is found, is sent a message, but either does not reply at all, or else its reply is missed by the PC.
I tried setting tcpdump going in another terminal window and giving the above command again. The result is here (WARNING: lots of hex bytes):
www.macfh.co.uk/Temp/tcp.log
From what I can see, the printer is responding, but the PC is failing to recognise the response. Particularly, if in /etc/sane.d/xerox_mfp.conf I add a port number known to be open in the MFP, 65001 (WS-Discovery), then you see that port number go out in the hex immediately after the IP as the following sequence ...
C0 A8 xx xx C2 B4 FD E9
IP .. .. .. *. .. Port
... (* where I presume the bytes C2 B4 are a standard separator), but this happens 8 times only near the start of the file, beginning at offset 0150 ending at 03A0, while the same IP address as above occurs 16 times in the file, and the more meaningful communication to & from the printer seems to occur towards the end, beginning around offset 09D0, and is repeated a number of times, as if the PC queries, the MFP responds, the PC fails to recognise the response, and so restarts this sequence, which accordingly repeats a few times.
Anyone able to suggest exactly what is failing and how I may be able to fix it?
I tried setting tcpdump going in another terminal window and giving the
above command again. The result is here (WARNING: lots of hex bytes):
www.macfh.co.uk/Temp/tcp.log
From what I can see, the printer is responding, but the PC is failing
to recognise the response. Particularly, if in
/etc/sane.d/xerox_mfp.conf I add a port number known to be open in the
MFP, 65001 (WS-Discovery), then you see that port number go out in the
hex immediately after the IP as the following sequence ...
C0 A8 xx xx C2 B4 FD E9
IP .. .. .. *. .. Port
... (* where I presume the bytes C2 B4 are a standard separator), but
this happens 8 times only near the start of the file, beginning at
offset 0150 ending at 03A0, while the same IP address as above occurs 16 times in the file, and the more meaningful communication to & from the printer seems to occur towards the end, beginning around offset 09D0,
and is repeated a number of times, as if the PC queries, the MFP
responds, the PC fails to recognise the response, and so restarts this sequence, which accordingly repeats a few times.
Anyone able to suggest exactly what is failing and how I may be able to
fix it?
On 10/03/2024 20:05, Java Jive wrote:
Further information ...
... but adding ...
# Xerox C315 MFP
usb 0x0924 0x9806
... to ...
/etc/sane.d/xerox_mfp.conf
... didn't allow ...
scanimage -L
... to find it.
- This ...
simple-scan "smfp:net;<MFP_IP_ADDRESS>"
... does not work, the scanner is not found.
FWIW Sane don't list the WorkCentre 3025 as supported: http://www.sane-project.org/sane-mfgs.html#Z-XEROX
Did you install the Xerox driver for it: https://www.support.xerox.com/en-us/product/workcentre-3025/downloads?language=en&platform=linux
It's very old (2014) so it might not work with a current version of Sane.
- This ...
simple-scan "smfp:net;<MFP_IP_ADDRESS>"
... does not work, the scanner is not found.
It appears 'smfp' is the Xerox closed source old driver, and xerox_mfp is
the open source Sane one. Possibly the above instructions are for the Xerox driver.
In uk.comp.os.linux Theo <theom+news@chiark.greenend.org.uk> wrote:
FWIW Sane don't list the WorkCentre 3025 as supported:
http://www.sane-project.org/sane-mfgs.html#Z-XEROX
Did you install the Xerox driver for it:
https://www.support.xerox.com/en-us/product/workcentre-3025/downloads?language=en&platform=linux
It's very old (2014) so it might not work with a current version of Sane.
Apologies, I misunderstood your model number.
The C315 doesn't appear to
have Linux scanner drivers - there's a .deb to download but it only seems to have printer drivers in it.
- This ...
simple-scan "smfp:net;<MFP_IP_ADDRESS>"
... does not work, the scanner is not found.
It appears 'smfp' is the Xerox closed source old driver, and xerox_mfp is
the open source Sane one. Possibly the above instructions are for the Xerox >> driver.
But this is still true - for your printer there's no smfp driver, so
anything related to smfp doesn't apply to you.
On 3/10/2024 9:19 PM, Java Jive wrote:
On 10/03/2024 20:05, Java Jive wrote:
Further information ...
At last I've managed to obtain some debugging information which shows that the MFP is actually being contacted, but is not responding in the manner expected. This page gives a different debugging environment variable, which, unlike the previous one, works:
https://manpages.ubuntu.com/manpages/xenial/man5/sane-xerox_mfp.5.html
"<user>@<machine>:home# SANE_DEBUG_XEROX_MFP=4 scanimage -L
[sanei_debug] Setting debug level of xerox_mfp to 4.
[xerox_mfp] sane_init: Xerox backend (build 13), version != null, authorize != null
[xerox_mfp] sane_xerox_mfp_get_devices: 0x7fff0450b3d0, 0
[xerox_mfp] list_one_device: tcp 192.168.1.127
[xerox_mfp] tcp_dev_open: open tcp 192.168.1.127
[xerox_mfp] :: dev_command(INQUIRY[0x12], 70)
[xerox_mfp] tcp_dev_request: wait for 1024 bytes
[xerox_mfp] tcp_dev_request: error Resource temporarily unavailable, bytes requested: 1024, bytes read: 0
[xerox_mfp] dev_command: illegal response len 0, need 70
[xerox_mfp] tcp_dev_close: closing dev 0x563011ff3d30
[xerox_mfp] list_one_device: dev_inquiry(tcp 192.168.1.127): Error during device I/O
No scanners were identified. If you were expecting something different,
check that the scanner is plugged in, turned on and detected by the
sane-find-scanner tool (if appropriate). Please read the documentation
which came with this software (README, FAQ, manpages)."
There seems to be a discrepancy in the above as to whether the expected response should have been 70 bytes long, or 1024, but anyway it seems from the above that the MFP is found, is sent a message, but either does not reply at all, or else its reply is missed by the PC.
I tried setting tcpdump going in another terminal window and giving the above command again. The result is here (WARNING: lots of hex bytes):
www.macfh.co.uk/Temp/tcp.log
From what I can see, the printer is responding, but the PC is failing to recognise the response. Particularly, if in /etc/sane.d/xerox_mfp.conf I add a port number known to be open in the MFP, 65001 (WS-Discovery), then you see that port number go out in the hex immediately after the IP as the following sequence ...
C0 A8 xx xx C2 B4 FD E9
IP .. .. .. *. .. Port
... (* where I presume the bytes C2 B4 are a standard separator), but this happens 8 times only near the start of the file, beginning at offset 0150 ending at 03A0, while the same IP address as above occurs 16 times in the file, and the more meaningful communication to & from the printer seems to occur towards the end, beginning around offset 09D0, and is repeated a number of times, as if the PC queries, the MFP responds, the PC fails to recognise the response, and so restarts this sequence, which accordingly repeats a few times.
Anyone able to suggest exactly what is failing and how I may be able to fix it?
First the host uses BJNP and gets no response to repeated (Canon) "Discover" packets.
Then it tries Query Multicast (QM) to the MFP machine.
https://networkengineering.stackexchange.com/questions/53160/what-does-the-output-of-this-tcpdump-mean
"This scheme is called DNS-based Service Discovery (DNS-SD)"
I can see this in Packet 43.
Packet 43 ScannerAvailable=1
[Picture]
https://i.postimg.cc/m2dgsq0s/Packet43.gif
That picture also includes an http:// reference to the device.
Not that this means anything.
So far, it's got as far as asking for details.
*******
I got this, by taking your TCPDUMP file and feeding
it directly into Wireshark. Which was able to parse it.
On 11/03/2024 11:29, Theo wrote:
The C315 doesn't appear to
have Linux scanner drivers - there's a .deb to download but it only
seems to
have printer drivers in it.
Which would explain why I can print but not scan.
"<user>@<machine>:home# SANE_DEBUG_XEROX_MFP=4 scanimage -L
[sanei_debug] Setting debug level of xerox_mfp to 4.
[xerox_mfp] sane_init: Xerox backend (build 13), version != null,
authorize != null
[xerox_mfp] sane_xerox_mfp_get_devices: 0x7fff0450b3d0, 0
[xerox_mfp] list_one_device: tcp 192.168.1.127
[xerox_mfp] tcp_dev_open: open tcp 192.168.1.127
[xerox_mfp] :: dev_command(INQUIRY[0x12], 70)
[xerox_mfp] tcp_dev_request: wait for 1024 bytes
[xerox_mfp] tcp_dev_request: error Resource temporarily unavailable,
bytes requested: 1024, bytes read: 0
[xerox_mfp] dev_command: illegal response len 0, need 70
[xerox_mfp] tcp_dev_close: closing dev 0x563011ff3d30
[xerox_mfp] list_one_device: dev_inquiry(tcp 192.168.1.127): Error
during device I/O"
So I think in both cases the attempted handshake is getting as far as
the initial query being sent to the MFP, and the MFP responding, but the MFP's response is not as expected, but whether that is the fault of the
MFP or the PC sane software I'm not sure. The long history of scanners showing this problem suggests that perhaps the problem is with the sane software, but there again, some of them have been made to work somehow
or other, suggesting it's the fault of the MFP.
Unless some super helpful reply comes in, I don't think I can do much
more, except to push the above information under the nose of Xerox and suggest to them in the strongest possible terms that they might like to
fix the problem.
On 11/03/2024 15.54, Java Jive wrote:
On 11/03/2024 11:29, Theo wrote:
The C315 doesn't appear to
have Linux scanner drivers - there's a .deb to download but it only
seems to
have printer drivers in it.
Which would explain why I can print but not scan.
There seems to have been some success with C235 at least based on a
thread at the Mint forum, seems to require you to install sane-airscan
read the full thread at:
https://forums.linuxmint.com/viewtopic.php?t=364633
Otherwise you can setup a ftp and store scanned documents to the ftp
and from there then do what you need with the image (crop, rotate, what ever).
On 11/03/2024 15:41, J.O. Aho wrote:
read the full thread at:
https://forums.linuxmint.com/viewtopic.php?t=364633
As that seemed promising, I thought I'd give it a try. However, I
couldn't install the sane-airscan package on Ubuntu 18 because of a
library conflict. So I tried in-place upgrading to 20, but the result
was the same, so now I'm on 22, and 'it just works'! Both printing & scanning now working fine.
Thanks very much for that tip.
The only downside is the that the two upgrades made a mess of my customisations, which, along with the double upgrades, is why I've been
slow in coming back to you, as I've had to spend some tedious time
putting everything back to how I want it - at least I've got the user desktops back now; just the awful login screen left to do, but it'll
have to wait for now.
Otherwise you can setup a ftp and store scanned documents to the ftp
and from there then do what you need with the image (crop, rotate,
what ever).
I'd already successfully set up the ability of the MFP to scan to a
share on my QNAP NAS as a backstop against not being able to scan from
some of my systems, partly because a thread from 2017 suggested that alternative solution to a woman with a similar problem with a Samsung
MFP of not being able to scan from Linux. However, now this will only
be needed from the XP PCs, which is an unlikely eventuality in any case.
| Sysop: | DaiTengu |
|---|---|
| Location: | Appleton, WI |
| Users: | 915 |
| Nodes: | 10 (1 / 9) |
| Uptime: | 30:12:58 |
| Calls: | 12,169 |
| Calls today: | 1 |
| Files: | 186,521 |
| Messages: | 2,234,226 |
