How do I make my NSA310 visible in Windows File Explorer?

Mijzelf

Your Entware-ng is using an outdated repo mirror. That is because it inherited the url from where MetaRepository was installed, which contains that outdated mirror. You can redo that, but you can also edit the repo list.

Install WinSCP, and use it to connect to the NAS. Navigate to /opt/etc/opkg/, there you will find a textfile containing the repo urls. Edit the file, and exchange https://mijzelf.duckdns.org/zyxel/Entware-ng/binaries/armv5/ by https://zyxel.ddnss.eu/Users/Mijzelf/Entware-ng/binaries/armv5/ . Then do an 'opkg update' again, it should download the list from zyxel.ddnss.eu.

SteveG

My Entware-ng? :-)

I installed WinSCP and navigated from root

to /opt

to /etc

and found opkg.conf which I opened to reveal:

I see the second line shows http:// not https:// as your last message refers to. Does this make a difference and should I use http:// or https://

I guess I'm editing something that's going to make a difference so just want to be sure.

Thanks

Mijzelf

Does this make a difference and should I use http:// or https://

To be honest, I don't know. opkg will try to download the file Packages.gz from that address (and subsequent any packages you want to install from that repo). opkg does or does not support https, and that old version from opkg is or is not able to read the https certificate in use.

If it fails, nothing is broken. 'opkg update' will just fail to download Packages.gz, tell you so in it's output, and continue using the previous version of that file (the one from mijzelf.duckdns.org). Then you can simply change the protocol and try again.

SteveG

OK. So first I edited opkg.conf line 2 with https:// and then opkg update and that failed.

Then I edited opkg.conf line to to http:// and then opkg update - that appeared to work.

Then entered the next line: /opt/etc/init.d/S08samba stop and got a not found message:

I used WinSCP to navigate to /opt/etc/init.d and see this:

No sign of S08samba.

I used WinSCP to try and find something related to samba and found this in /root/etc/samba

So, one step forward and another brick wall. Am I any closer?

Mijzelf

You have successfully updated the local database of remote Entware-ng packages. But you didn't install the wanted package:

opkg install zyxel-samba-replacement

SteveG

OK. I used the command you supplied, which I had used previously. This time it appears to have installed and configured the zyxel-samba-replacement.

Then I went back to the commands in the forum:

  /opt/etc/init.d/S08samba stop

  chmod a-x /opt/etc/init.d/S08samba

  chmod a+x /opt/etc/init.d/S09ZyXELSambaReplacement

didn't bring up any errors but the last one did:

    /opt/etc/init.d/S09ZyXELSambaReplacement start

The first 9 lines in the screenshot above are from yesterday.

So close and another brick wall. What did I miss/get wrong this time?

SteveG

This is a screenshot of the /opt/var/lock folder

Mijzelf

I think it should work now. Have you already tried to access the NAS using explorer?

SteveG

My Windows 11 PC (MSI-B550M-PRO-V) still cannot see either of my Zyxel NASs in File Explorer. It could, prior to the Windows 24H2 update.

My Windows 10 PC (Gigabyte1) File Explorer/Network shows:

as it did previously. However, when I now try to navigate into the shares (eg admin) I get the following network error:

Previously I gould navigate into the shares and see all my data. Looks like a backward step.

NSA310 is the Zyxel NSA310 NAS I've been working on. SOHONAS is my second Zyxel NSA310.

WinSCP still appears to be connected to NSA310 on the original tab. I opened another tab and logged into it again.

Any ideas?

Mijzelf

Any ideas?

Complicated. Entware's samba has been started, and has been running for at least 28 minutes. You dump of /opt/var/lock proves that. All files there are samba dust, and browse.dat is created/updated 28 minutes after the other files. (Al those .tdb files are some kind of databases).

You can check if 'a' samba is running at the moment by executing ps. This shows all running programs, and samba consists of 2 daemons, smbd and nmbd.

W10 should simply work, there is enough feedback about that. I'd expect W11 24H2 to also work, as I haven't read anything about dropped downcompatibility, apart from SMB1. But I can't remember if there is actual feedback that zyxel-samba-replacement actually works for 24H2.

My Windows 11 PC (MSI-B550M-PRO-V) still cannot see either of my Zyxel NASs in File Explorer.

As I said in my first post in this thread, I don't know if the NAS should be visible, but it should be accessible. It might not show up, but you should be able to type \\NSA310\ or \\<ip-of-nas>\ to browse it's content.

About the win10 box, have you rebooted it after changing samba? If you didn't, it might assume it's still talking to the same server, and trying to use cached credentials, or something like that.