NAS326 desktop unreachable

KenG

I have 2 NAS326's on my local network. Until a few weeks ago I could reach the desktop using the IP address in Firefox for each of the devices. Now, I can easily reach the first 326, but the other gives me the message "Problem Loading Page. Unable to Connect. Firefox can’t establish a connection to the server at 192.168.1.XX". Unfortunately, this also happens when using the FindMe utility - the 326 is found on pairing, but a connection can't be made. The other 326 works fine. I can connect to both using File Manager and see shares and files but without access to the Desktop I cannot create new shares or users. Any help/suggestions would be greatly appreciated!

Mijzelf

A factory reset doesn't touch the disks. So yes, if you don't use any additional packages, you only have to rebuild the users, and re-enable the shares. (After a reset they are ordinary directories)

I never used FindMe (I won't use cloud services if I can avoid it), but I suppose in this case it's just a fancy way to reveal the internal IP address of the NAS?

Mijzelf

Have you already tried to reboot the NAS?

KenG

Yes, no difference…

Mijzelf

Did you change anything in your network? Maybe somehow the IPv4 address is occupied, and the File Manager can work via IPv6.

KenG

As far as I can tell nothing has been changed, neither 326 has IPv6 enabled. The problem device can be located and paired to MyZyxelCloud (but can be found but not opened by findme.zyxel.com). Perhaps I should just try a reset? I have not created any novel shares and everything is backed up on a remote drive, so all I would have to rebuild would be users?

Many thanks for your prompt assist!

Mijzelf

A factory reset doesn't touch the disks. So yes, if you don't use any additional packages, you only have to rebuild the users, and re-enable the shares. (After a reset they are ordinary directories)

I never used FindMe (I won't use cloud services if I can avoid it), but I suppose in this case it's just a fancy way to reveal the internal IP address of the NAS?

KenG

Thanks for the advice/reassurance - I did the reset - it did cause a day or so of fiddling to get back to normal, largely due to Win11 locking up (completely, required hard reset, many times) - I had set up some mounted shares and these were unavailable, because I had forgotten that I had changed the default name of the NAS - once re-named and with separate ports properly assigned within the NAS and the (BT) hub, all is now back to normal!😊