How to scan with a wifi networked Epson L355 on Ubuntu 14.04 (trusty)

Long story short – possible, but no walk in the park. Beginning to think we linux users are masochists. The price of absolute power, I suppose.

It’s a shame my ScanSnap 1500 broke down sometime ago. Not so much broke-down, rather some nasty looking goo started leaking out of it and I thought it a good idea not to power it up until I took a look under the hood and work out what’s going on. Like many things, this has been put on the back-burner.

There’s really not much need to scan documents anymore, and with the amount of time I spent on this particular technical safari, I wished I’d just added my signature to the required documents electronically.

Those who have been following along will know my Epson L3551 has a clogged print head such that it now only functions as a scanner. My backup scanner, if you will, which has been elevated to my primary one due to the issues with the ScanSnap.

Like Joko says, “If you’ve got two, you’ve got one.”

TL;DR – Success, of sorts, seems mostly acheivable

Keep in mind this post documents my experience in getting the L355 scanner working with the SANE backends in Ubuntu Trusty (14.04).

After 12 hours of struggle2 the solution appeared from an unlikely source. (original page in Spanish – translation here.)

For me, it was critical to have the epson2 SANE backend activated.

I’m glad I persevered to the point where I have a working linux front-end app (skanlite) which is able to communicate to my wifi connected Epson L355 and produce good quality scans. I need to start skanlite using the following: skanlite -d net: 3 otherwise sometimes it doesn’t detect the scanner.

That’s enough for me – I was NOT able to get the Epson iscan app working or get xsane to detect the network-attached scanner4 (it would detect the scanner if connected via USB.)

Other folks seem to have both of the above configurations working. YMMV.

tROUBLESHOOTING – things to check

  1. RTFM
    There’s some excellent info here. Work through the document it may well fix your issue and in many cases summerizes the information which follows.

  2. Check libsane is installed

    If your distro doesn’t contain the required version then head here.

  3. Check the printer has been assigned a static IP address and is connected to your router via wifi, which will require you know the correct SSID/Network key

    You’ll likely need to do this via the Windows-based Epson utilities or alternatively could try a WPS connection by pressing the wifi button on the printer for 3 seconds. One imagines DHCP would automatically assign the printer an IP address which you would then want to change.

    Here’s a YT video which may help:

    If this is completed correctly the wifi light on the front of the printer should be solid green.

  4. Ensure scanimage can detect the printer and try out a test scan via the command line.

  5. IF YOU WANT TO USE iscan (Image Scan app from Epson), download the correct linux drivers for the Epson L355.

    Otherwise, they are not necessary.

    Firstly, I had to check if I’m using a 32-bit or 64-bit version of Ubuntu using uname -m which returns i686 = 32-bit. Ok.

    Then I had to download the correct iscan package iscan-bundle-2.30.4.x86.deb.tar.gz from Epson via this URL. Epson have kindly provided a handy manual. Read it!


    I took a look inside my Downloads directory to see similar files previously downloaded.

    I have a memory of trying to get this working years ago, but ran into difficulties and ended up running it using a samba via a windows box. The above shows the battle took place in 2015 – all I can recall is I lost on that occasion 🙁

    After extracting the payload from the tar.gz file I ran the script and then iscan, and received the following:

    Googling Could not send command to scanner. Check the scanner’s status you’ll likely come across this article:

    Get Epson iScan to work in Ubuntu with a networked/wireless scanner

    If you see this error upon starting iScan aka “Image Scan for Linux”: “Could not send command to scanner. Check the scanner’s status.” It means the iScan couldn’t find the scanner. This happens often if it’s not connected via USB, but lives in a wireless network for instance.

  6. You may need to modify some symbolic links and update to

    There are reports of a libsane update breaking 3rd-party plugins.

    Here is what my current /usr/lib/sane folder contents:

    When looking at the above, I’m unsure why the files in /usr/local/lib appear to be newer than those in ../i386-linux-gnu. I’m hesitant to play with things here as it’s now working to a degree I’m happy with.

    I believe it happened as a result of running this:

    I have a memory of modifying the above symlinks based on this post from SO.

    Epson GT-S50 scanner not working after upgrade to 18.04 from 16.04

    Since the upgrade, my Epson scanner GT-S50 (Epkowa driver). It gets detected ( dmesg) when plugged in: [ 3755.680091] usb 3-4.4.1: new high-speed USB device number 8 using ehci-pci [ 3755.789893] usb 3-4.4.1: New USB device found, idVendor=04b8, idProduct=0137 [ 3755.789895] usb 3-4.4.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 3755.789896] usb 3-4.4.1: Product: EPSON Scanner [ 3755.789897] usb 3-4.4.1: Manufacturer: EPSON But when starting either “Image Scan!”

    Q: Which config file is used? Which libsane is used?

    As can be seen from the above, the current directory plays a part in how sane loads the backends. (Note the highlighted lines.)

    As per the man page:

    This environment variable specifies the list of directories that may contain the
    configuration file. Under UNIX, the directories are separated by a colon (‘:’),
    under OS/2, they are separated by a semi-colon (‘;’). If this variable is not set,
    the configuration file is searched in two default directories: first, the current
    working directory (“.”) and then in /etc/sane.d. If the value of the environment
    variable ends with the directory separator character, then the default directories
    are searched after the explicitly specified directories. For example, setting
    SANE_CONFIG_DIR to “/tmp/config:” would result in directories “tmp/config”, “.”,
    and “/etc/sane.d” being searched (in this order).

    You can see below I get different results depending on where the command-line invocation is issued.
    Works if in the /etc/sane.d/ directory ; fails to find scanner otherwise.

    I wanted to delve under the hood to determine which files and sockets were being opened when I fired up skanlite. Below is some truncated output using the lsof command.

    Ideally I need to fix this – have not done so at the time of writing. I also note the use of port 1865 on the Epson (default, specified explicitly in the config file) however nmap doesn’t list this as an open port on the printer?

  7. /etc/sane.d/dll.conf – The backend configuration file.
    My working version contains the following lines:

  8. Ensure the file /etc/udev/rules.d/79-udev-epson.rules is present.
    Mine contains the following:

    If you need more information on udev rules read this

  9. scanimage may detect your webcam.

    To fix this, edit your vl4.conf file and comment out all the device lines.

  10. nmap is your friend
    Firstly, scan your entire subnet to see what devices are active, and ensure your scanner is one of them.

    Then get specific open port information on your scanner. It should look something like this:

    What are those strange ports you ask?

    Ensure your printer is not connected to the internet lest you want be punkd.

  11. /etc/sane.d/net.conf
    The only active line I have in this file is:

  12. /etc/sane.d/epson2.conf

  13. /etc/sane.d/epkowa.conf

  14. Check /etc/default/saned *if applicable*

    Q: Does saned (daemon) need to be running? – NO ; I have been able to use skanlite to scan from my wifi networked Epson L355 without the daemon running.

    saned is the SANE (Scanner Access Now Easy) daemon that allows remote clients to access image acquisition devices available on the local host.

    Graphically, here’s the best explanation I’ve found (source:

  15. Fallback to USB cable connection

    It’s worth doing this fairly early on. Knowing it works via USB will provide warm fuzzies!

  16. Fallback to Windows, if you must

    When you’ve worked these types of problems you usually know when it’s time to throw in the towel. During my early iterations of trying to get this up-and-running, I had to call time and go down this road

    This type of troubleshooting tends to chew through the hours and I simply needed the problem solved i.e. the documents scanned.

    It was time to get things working under Windows, which in my case meant firing up my Virtualbox VM with Win10 guest OS5.

    Download the latest drivers/utilities (I thought I was smart having located the CD which came with the printer – a bad move as this version was not suited to Win 10 and I had to uninstall / re-install the correct one [Epsonnet setup manager 03-Aug-2015 31,32Mb]

    Even this was no picnic but in the end it worked!

  17. Notes

    1. Purchased at Officemate in Thailand.
    2. Some PEBKAC here – I had an unknown duplicate IP address issue. Argh!
    3. source:
    4. Even xsane net: fails to work.
    5. Yeah my WIN 10 hasn’t been activated – don’t see any downside here, downloaded the ISO from MS. Ref:,5717.html
    6.strace worth a look if you are really stuck. Use the -o flag to redirect output for further investigation. Will help you locate what’s *really* going on under the hood.

    7. Note to self – don’t buy another Epson printer. You’ve owned enough in this lifetime.
    8. Restarting ubuntu networking:
    9. Confirming SANE support for Epson L355:

    10. Webconfig doesn’t seem to work. Pointing the browser to the printers IP address just gives me the following screen:

    11. A good SANE network tute here:
    12. When connected via USB, I managed to get the scanner working with xsane but the scan quality was poor. Setings? Maybe, I’ll admit. Interestingly, iscan still refused to play ball.

Leave a Reply

1 Comment on "How to scan with a wifi networked Epson L355 on Ubuntu 14.04 (trusty)"

Notify of
Sort by:   newest | oldest | most voted

I’d rather play bridge.