Using an HP OfficeJet Pro 9000 series to scan to a TrueNAS 12 SMB share

[mikevankuik]

Hello everyone,

Although the people at HP where very polite they couldn't help me because TrueNAS isn't Windows or MacOS.

That said I personally don't believe the issue to be with the OS one is running,

The problem itself is quite easy, the printer (HP OfficeJet Pro 9010) has the option to save scans to a network folder.
It can utilize SMB 1, 2 or 3 for this.

So far I couldn't get the printer to save files to my TrueNAS 12 system which I can reach fine with either, Microsoft Windows 10, MacOS or Ubuntu.
Having an old Netgear ReadyNas Duo v1 which does only support SMBv1 as far as my knowledge goes, I did get it to work.

So I conclusion I know that the scanning and saving to a network share can and indeed does work.

However, this ReadyNas Duo is only still in my home because the people at Sonos seem to have a little trouble implementing SMB 2 or higher in their products.
Naturally I would like my printer which is capable of these higher versions of SMB to save the scans to the TrueNAS shares.

Below I've added screenshots of the settings on the printer (which has a web interface) and settings in TrueNAS.

I've not been able to figure out what is going wrong here yet, I hope you can point me in the right direction or even tell me what I'm doing wrong.

SMB 2 and 3 are enabled

The network share I'm trying to reach

The settings

TrueNAS 12 settings

ACL Share

ACL Filesystem

 

[mikevankuik]

Not sure if it had to do anything with it, but I upgraded from TrueNAS-12.0-U1 to TrueNAS-12.0-U2.

After I posted my issue on the FB group Ray Sundland was giving me some pointers on where to look.
I actually already did the permissions checking back on TrueNAS-12.0-U1 so I wasn't very hopeful but it can't hurt resetting them once again.
This time however I'm on TrueNAS-12.0-U2, it seems to work as expected.
Although with this cavate which is not an issue for me, that I have to provide the printer with a username for it to work.
If no username is given and I tell it to go anonymous it won't work, if I give it a username and no password it will just work.

Now this is how I went about it.

I removed the ACL on the file system first.

Then I removed the share.

And as the last step I re-created the share.
Take not that I checked the "Allow Guest Access"checkbox.

You could configure the dataset later, but it's just as easy as doing it right here and now.

I've selected the "Open" preset because that's right for me, please consider that my settings might not be optimal for your use case.

I also select to have both recursively and apply to child datasets checked. This will warn you about potentially making files or folders unavailable. This due to the permission changes that are being forced upon the files and folders. Again not an issue in my use case but your needs might be different so be careful.