Wanted: Working scan to network folder (SAMBA)

[ts7495]

Hi,

I try to use scan to network folder on my HP OfficeJet Pro 9015 for several days now. Without any success. I'm lost.

I try to scan to a share on my Linux server (Debian) running SAMBA (2:4.9.5+dfsg-5). The target share is world writeable (guest ok = yes) and working from my workstations. The printer does not authenticate for the fileshare (no credentials configured).

When I try to scan to that folder, the printer claims about some (unspecified) network issues. When using tcpdump on the server I can see the printer connecting. But the connection is closed directly.

Does anybody have a working SAMBA configuration I could try?

[ShlomiL]

1. Click the top bar icons or swipe it down and click the ethernet or wireless icon to locate the IP Address of your printer.
2. Browse this IP to access the EWS page of your printer.
3. From the EWS, click the Settings tab.
4. Under Preferences, select Date & Time.
5. Make sure the Current Printer Time is set to GMT.
   To determine GMT, open an internet browser, and then search for What is the current GMT time.

   NOTE:

   Do not use the Sync Nowoption.

6. Click Apply to save any changes

Now check if you may see any difference when clicking the test button for the scan folder profile and check if that may help.

[ts7495]

Hallo ShlomiL

thank you for your fast reply,

I read about the GMT "solution" and tested it before posting. I just repeated the test with the same result: Still not working.

Just to avoid any misconfiguration on my site: a Screenshot showing the time of my printer, server and GMT.

Is there anything wrong.with my configuration?

[ShlomiL]

Thanks for the information @ts7495, this

seems

correct indeed and have 1 hour difference than your local time.

I would also suggest to try authenticating with a local user credentials and see if that may make any difference.

Also, could you please let me know the exact network path used, to see if that seems correct.

Shlomi

[ts7495]

Hello @ShlomiL,

thanks for your feedback and support.

I just tried scanning to a network folder with username/password authentication. This failed, too. Using the same credentials within Linux file manager the share works fine.

The configured network path to my share is:

Guest-Writable: \\australien.se____.____orf.priv\scanner

Authenticated Access: \\australien.se____.____orf.priv\scanner1

The smb.conf:

[global]
workgroup = ____WEG
interfaces = br0.32 tun0 tun1
bind interfaces only = yes
log file = /var/log/samba/log.%m
max log size = 1000
logging = file
panic action = /usr/share/samba/panic-action %d
server role = standalone server
obey pam restrictions = yes
unix password sync = yes
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
pam password change = yes
map to guest = bad user
usershare allow guests = yes
[homes]
comment = Home Directories
browseable = no
read only = yes
create mask = 0700
directory mask = 0700
valid users = %S
[printers]
comment = All Printers
browseable = no
path = /var/spool/samba
printable = yes
guest ok = no
read only = yes
create mask = 0700
[print$]
comment = Printer Drivers
path = /var/lib/samba/printers
browseable = yes
read only = yes
guest ok = no
[scanner]
path = /mnt/media/public/Scanner
public = yes
writable = yes
comment = smb share
printable = no
guest ok = yes
[scanner1]
comment = A new share
path = /mnt/media/public/Scanner1
browseable = yes
read only = no
guest ok = no
valid users = scanner

If helpful I coud post some sceenshots of my printer configuration, too.

Thomas

[ts7495]

Update: I don't know why. But I could solve my issue by (a) not using hostname but the IP address of the smaba server and (b) login to the samba server without credentials (without user/password).

I will continue to investiage and post my findings.

[linuxturtle]

Did you also use the GMT kludge?  I can't get this to work no matter what I do or how I try to connect (GMT time, credentials or not, IP address or DNS).  I just bought this thing, and I'm close to solving the problem by taking it back to Costco, and buying an Epson Eco-tank AIO.

[linuxturtle]

Fixed:  Sort-of.  Well, I'll be darned, I found a "solution" to the problem, although I must confess I don't really understand why it works.

If I force samba to only serve SMB2 or lower protocol, everything works fine.  I just added this line in smb.conf in the [global] section, and restarted smbd on the samba server:

server max protocol = SMB2

[ts7495]

Is password authentication working when limiting to SMB2 (or lower)?

I thought I'd tested with SMB2. But my memories might be false 😉

[linuxturtle]

Indeed, authentication works for me now, and no need for the GMT kludge either. I never got it working before with guest writable (no auth) access though, so something is different between our setups.