SULDR Forums Supported Printers Printing Questions Scanning Questions General Questions Samsung Installer

SCX-3405FW printing, but not scanning

Started by zhum, September 14, 2016, 07:17:20

Previous topic - Next topic


MFU is connected to network only. I have two networks in one real network segment: 192.168.169.* and real addresses, say

First machine is Linux Mint 17.3, it has real address, say, I can print, but I cannot see scanner:

$ /opt/Samsung/mfp/bin/netdiscovery
# DEBUG: Network printers discovery utility
ip: slp: 0,0,0,0 snmp: 1,1,0 vendor: Samsung dsc: "SCX-3400 Series"

I have installed: libtiff3-suld, suld-configurator-1-qt4, suld-driver-4.00.35, suld-driver-common-1, suld-network-2, suld-ppd-1,
suld-printer-pdf-fix, suld-scantopc, suld-scantopc-gui, suldr-keyrin.

Second machine - server, it has two physical interfaces: eth0 for Internet connection and eth1 - the same as I wrote above (say, eth1 have addresses and I cannot see this MFU at all (it seems, it scans only FIRST interface).

Here I have installed: libtiff3-suld, suld-configurator-1-qt4, suld-driver-4.00.35, suld-driver-common-1, suld-network-2,  suld-ppd-1, suld-printer-pdf-fix, suld-scantopc, suld-scantopc-gui, suldr-keyring.

how can I bring my scanner working?



I cannot see this MFU at any computer. One "sees" only wrong network segment, and another cannot detect it as scanner, but can detect as printer. Windows machine can scan. I could scan with samsung drivers, for one year. I seems to become bad after upgrade from Linux Mint 17.1 to 17.3 (ubuntu 14.04 to 16.04), but I'm not sure.


I don't think the driver was ever intended to be deployed in this sort of setting, so I don't think there is anything about the driver itself that can be changed to address this.  Perhaps there is some way to modify the network configuration or use some sort of port forwarding to work around this limitation, but I don't have any experience that I can share.

Repository Information Legal Contact Alternative Drivers