NSA325 Share permissions

Options

I have a strange problem accessing user created shares on my old NSA325 ( I know it is no longer supported but it was doing the job).

From Windows 11 (and Wind 10) I can not access any user created shares on the device, I can access the built-in shares, music, video, etc.

If I try to map a network drive it fails with the "check spelling" error.

I have the Entware-ng samba server installed and running.

As well as moving to Windows 11, I have made quite a lot of changes to my home network, went from powerline adapters to wi-fi mesh, so that may have something to do with it.

All Replies

  • suisei
    suisei Posts: 78  Ally Member
    10 Comments Friend Collector First Answer
    edited December 2023
    Options

    Make sure the privileges on the shared folder. For any spelling errors, consider using simple naming to check for potential issues.

  • suisei
    suisei Posts: 78  Ally Member
    10 Comments Friend Collector First Answer
    Options

  • RedScotLFC
    Options

    I have checked permissions and spelling. The permissions are the same as the built-in shares which I can access

  • Mijzelf
    Mijzelf Posts: 2,645  Guru Member
    First Anniversary 10 Comments Friend Collector First Answer
    Options

    I can think of several reasons why those shares don't work. The Entware samba uses /opt/etc/smb/samba.conf, or something like that, while the firmware generates an /etc/smb/samba.conf. To copy with that, /opt/etc/smb/samba.conf has to include /etc/smb/samba.conf (or you have to maintain the conf file yourself). So have a look if that is the case. And have a look if there could be something in /etc/smb/samba.conf between the build-in shares and the user created ones, which could somehow 'end the include'.

    Another thing is login. The samba passwords are stored in /etc/smb/smbpassword or something like that. I don't know where Entware samba looks for them. It could have it's own file, in which case all 'firmware' passwords are wrong. Maybe the file /opt/etc/smb/smbpassword was a symlink to the firmware one, and somehow the symlink is exchange by a copy of the firmware file at some point in time.

Consumer Product Help Center