search

SimulPiscator / AirSane

Publish SANE scanners to MacOS, Android, and Windows via Apple AirScan.
GNU General Public License v3.0
251 stars 26 forks source link

Failed to Connect from Image Capture #32

Closed hftsai256 closed 3 years ago

hftsai256 commented 4 years ago

I have set up AirSane server on Debian Buster/Arm64 and can download scanned images on http://:8090. On MacOS Catalina side, the scanner pops up in Image Capture and also shown up as Bonjour Scanner. However it throws the error "Failed to open a connection to the device (-21345)".

I then tried to get some log on the server end as instructed: sudo -u saned airsaned --debug=true --access-log=- It shows nothing when I am connecting with Image Capture. However it can tell me when I access the web interface. I'm wondering if my avahi is not set up properly?

SimulPiscator commented 4 years ago

I remember having such problems when ipv6 was disabled on the device running AirSane. You should make sure that ipv6 is enabled on your local network as well.

To check which information is being sent through avahi, you can download the "Discovery" utility from the Mac App Store (http://www.tildesoft.com/). It will let you browse all services announced on your local network.

hftsai256 commented 4 years ago

I renewed DHCP with ipv6 addresses enabled. Image Capture can now connect without issue. Thanks for your help and all the hard work to make this happened :)

himanshubabal commented 3 years ago

I renewed DHCP with ipv6 addresses enabled. Image Capture can now connect without issue. Thanks for your help and all the hard work to make this happened :)

I am facing the same issue. Can you please clarify what 'renewing DHCP Lease' means & how to do it.

SimulPiscator commented 3 years ago 
sudo ifdown eth0
sudo ifup eth0

should renew the DHCP lease on the machine running AirSane (replace eth0 with the name of your ethernet device, using sudo ifconfig to get a list of devices). Alternatively, rebooting the machine will renew the DHCP lease as well.

himanshubabal commented 3 years ago

Rebooting the machine worked. Thanks for the prompt reply