Cannot mount NAS samba shares

Troubleshooting
1

Hello everyone
Despite without any issues in the past, I am somehow not able to mount samba shares from a Buffalo NAS on my dietpi running on Rpi4. As a result, ARRs/ deluge/ jellyfin cant be used. Another pi running kodi or various devices around the house can access the shares without any issues.
The only change I can think of is recently setting up a samba server on dietpi itself which I have since uninstalled.
I am using Drive_manager to mount it. Neither admin and its pwd or guest/guest combo work.
I just successfully test mounted another share provided by my Asus router (using guest as used and guest as pwd) and it worked fine.
Can someone help?
Many thanks.

2

What error message do you get when trying to mount it via dietpi-drive_manager?

3

Maybe the nas is providing old SMB v1 share?

4

│ mount error(113): could not connect to 192.168.1.222Unable to find suitable address.

5

Yes I bellieve that is the case. The NAS is very old and still uses Samba v1.

6

You can try mounting the share manually

sudo mount -t cifs //SERVER_NAME_OR_IP/SHARE_NAME /mnt/mount_point -o username=USERNAME,password=PASSWORD,vers=1.0
  • Replace SERVER_NAME_OR_IP with the server’s hostname or IP address.
  • Replace SHARE_NAME with the name of the Samba share.
  • Replace /mnt/mount_point with the local directory where you want to mount the share.
  • Replace USERNAME and PASSWORD with the Samba credentials.
7

No luck :frowning:

[77734.152495] CIFS: VFS: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers
[77734.152516] CIFS: Attempting to mount \192.168.1.222\Movies
[77744.433537] CIFS: VFS: Error connecting to socket. Aborting operation.
[77744.433617] CIFS: VFS: cifs_mount failed w/return code = -115

I tried both admin and guest accounts. I can mount another share from an Asus router without issues.

Also,

— 192.168.1.222 ping statistics —
22 packets transmitted, 0 received, +8 errors, 100% packet loss, time 21506ms
pipe 4

NAS is working fine with other computers, including a pi4 running kodi.

8

any firewall or other component in between that could block access??

9

None that I can think of. There was a dumb switch as I was running out of ethernet ports on the router but I have disconnected it. Had a pi3 running dns server to block ads but is now turned off and now the router is the one providing dns. Both devices are directly plugged into the router. Both can talk to other devices within the network. Dietpi is accessing internet as usual.
The only firewall is the usual Asus router’s firewall. I am not sure about dietpi though. Does it have its own firewall?

10

Not by default, however you can install ufw or any other. Did you installed anything like this? Can you ping the router from DietPi device.

11

Yes, I can ping the router, a mesh node, kodi, etc. No problem there. I dont remember installing ufw. Some package like a samba server may have installed it?

12

Nope, ufw should not be installed along other software title.

IP of NAS is correct?

13

Yes it is correct.
I tried connecting using wifi instead of ethernet and it does connect. I also used a wifi to ethernet adapter to check and that connected too.
For now, I have disabled ethernet and using wlan, everything seems to be working fine.

14

Strange, what you could try is to set a static IP address on ethernet. A different one than the one used on DHCP.