Shared folder with network scanner

[bari]

Good morning, someone who can help me, I have installed thunder and I am trying to access from a network printer to be able to save scanned documents in a folder. But in the printer the network unit does not detect me, however from some PCs in the same network it does detect them. Do you know what could be the error? Thanks in advance.

 

[superfour]

I am having the same problem with an HP network scanner. When destination folder is set to a TrueNAS share (with dedicated user/group permissions), scanner can't see it. Scanner works fine with other windows network shares.

 

[Patrick M. Hausen]

Have you tried enabling SMB1?

Services - SMB

 

[superfour]

Have you tried enabling SMB1?

Services - SMB

Life saver! Thank you Patrick :)

 

[CrackedDilithium]

Have you tried enabling SMB1?

Services - SMB

Isn't SMB1 a security risk? Also, this issue does not exist in TrueNAS Core, just Scale from my experience.

 

[Patrick M. Hausen]

It is. Yet there's lots of embedded equipment that does not support anything later.

When Samba finally will retire SMB1 I wonder how we will be booting all our Supermicro systems from virtual media via IPMI? Keep an old Samba installation in a VM? Ideally someone writes a "tiny-smbd" that shares a single folder, with SMB1, read only, and guest access ...

 

[anodos]

It is. Yet there's lots of embedded equipment that does not support anything later.

When Samba finally will retire SMB1 I wonder how we will be booting all our Supermicro systems from virtual media via IPMI? Keep an old Samba installation in a VM? Ideally someone writes a "tiny-smbd" that shares a single folder, with SMB1, read only, and guest access ...

IIRC samba 4.16 basically deprecates MS-DOS clients (including Windows 9x). Samba 4.17 includes option to build without SMB1 support, but we won't be exercising this option at this point. So minimum of 1 - 1.5 years of SMB1 support remaining (as long as we're not talking DOS).

DOS clients will no longer work in BlueFin and the next major FreeBSD-based release.

One of the problems with SMB1 protocol is that it's rather hard to have a "tiny" server supporting it. c.f. MS-CIFS https://docs.microsoft.com/en-us/op.../ms-cifs/d416ff7c-c536-406e-a951-4f04b2fd1d2b and MS-SMB https://winprotocoldoc.blob.core.windows.net/productionwindowsarchives/MS-SMB/[MS-SMB].pdf

 

[CrackedDilithium]

IIRC samba 4.16 basically deprecates MS-DOS clients (including Windows 9x). Samba 4.17 includes option to build without SMB1 support, but we won't be exercising this option at this point. So minimum of 1 - 1.5 years of SMB1 support remaining (as long as we're not talking DOS).

DOS clients will no longer work in BlueFin and the next major FreeBSD-based release.

One of the problems with SMB1 protocol is that it's rather hard to have a "tiny" server supporting it. c.f. MS-CIFS https://docs.microsoft.com/en-us/op.../ms-cifs/d416ff7c-c536-406e-a951-4f04b2fd1d2b and MS-SMB https://winprotocoldoc.blob.core.windows.net/productionwindowsarchives/MS-SMB/[MS-SMB].pdf

But you have to enable SMB1 even on Core right now, correct? The issue that I've been experiencing is that my HP scanner will work with Core WITHOUT SMB1 checked but it will not work with Scale unless I check SMB1.

 

[anodos]

But you have to enable SMB1 even on Core right now, correct? The issue that I've been experiencing is that my HP scanner will work with Core WITHOUT SMB1 checked but it will not work with Scale unless I check SMB1.

Perhaps you have SMB1 enabled via auxiliary parameter in Core? Currently there is no difference in SMB server between Core (13) and SCALE. Alternatively, the change to SMB protocol restarted the SMB server in SCALE and it started working. Maybe compare output of smbstatus -p on both servers. This will show current sessions and include protocol. NT1 == SMB1.

 

[CrackedDilithium]

Perhaps you have SMB1 enabled via auxiliary parameter in Core? Currently there is no difference in SMB server between Core (13) and SCALE. Alternatively, the change to SMB protocol restarted the SMB server in SCALE and it started working. Maybe compare output of smbstatus -p on both servers. This will show current sessions and include protocol. NT1 == SMB1.

So I checked SMB1 on my Scale server and then ran a scan for it to work and it showed that the protocol version was SMB2_02. However, as soon as I uncheck SMB1 again, the HP scanner will no longer connect. I did confirm that on Core it is showing that same exact protocol version when I run a scan.

 

[CrackedDilithium]

It would seem that the checkbox for SMB1 is also effecting SMB2. Is that expected behavior? If not is there anything else that I can provide to help figure out what is occurring?

 

[CrackedDilithium]

So should I create a separate thread for my issue?

 

[mileskoth]

Hey
I totally agreed with you my problem is solved. I am very happy.
For more information see https://www.truenas.com/community/threads/shared-folder-toto-astro-with-network-scanner.100668/

 

[asimkhattak]

Have you tried enabling SMB1?

Services - SMB

faced a headache after facing this issue at my end, but you're the real hero.