No access from Windows 10 (Error 0x80004005)

[fvdw]

AFAIK Being visible in network folder of windows 10 is dependent if windows 10 can find the device which is assigned being master browser. That device supplies a list with all hostnames in the lan. If the master browser is in suspend mode it might not answer to calls to supply the list.vIf the master browser is for a certain time not responding there will be elected a new master browser.
So it might take while until a nas is detected in windows 10.
However the fvdw-sl nas should always respond when using its ip in explorer as you also described. It is a windows 10 issue, I do not know anything which can be done to improve visibility.
Note in windows 7 the detection was much better.
Ps Needles to mention is that windows 10 must have enabled smb1 protocol to have smb nas detected by hostname in explorer

[Cubytus]

So here we have two problems:
Visibility
How would I find out who is the master browser? I may not fully understand, but isn't Bonjour suppposed to advertise any host to each other? The Mac doesn't display this bad behaviour after all. In any case, all 5 devices are online and not set to sleep or turn off, so that shouldn't be an issue. And BTW this Windows 10 computer has been turned on for the past 48 hours, that's plenty of time for discovery or set a new master browser.

What I understood from your first message was that SMB1 was a deprecated protocol that is and should be disabled on every LAN device. I enabled it following these instructions, since the option was not displayed in Windows features.

Also, you can activate it using this process :

1. Click on the Start menu
2. Type cmd to find the command prompt
3. Right click on "Command Prompt"
4. Select "Run as administrator"
5. Type the following command : DISM /Online /Enable-Feature /All /FeatureName:SMB1Protocol
6. Confirm

I rebooted the computer, then enabled SMB1 on fvdw, still to no avail. It stays invisible, even though other devices do show up properly this time.

Accessibility
Even after these tweaks, when I call the fvdw NAS through its IP, the error is the exact same one: 0x80004005.
Double-clicking the Synology NAS gives a list of shared folders (correct behaviour), while the OMV NAS gives 0x80070035 error (another incorrect behaviour). :hairpull

Why is enabling SMB1 still necessary in Windows 10 even if it's less secure, slower, etc.?
How could Mac OS X got SMB sharing mostly right 8 years ago but Win 10 still struggles with its own protocol?
More fundamentally, why is fvdw the only firmware to cause issues with hostnames and still doesn't support Bonjour properly?

Network sharing nightmares was one of the reasons I left Windows 15 years ago. 15 years after, it's still not ironed out. Now I realize this is a rant, but I'd really like fvdw to become truly plug-and-play and match its stability (347 days uptime and counting, when I replaced the UPS unit.)

[Jocko]

Hi

If I remember rightly, another member had similar behaviour as you.

First can you confirm if at least one share on your cloudbox is not a public share. if not create a private share with at least one authorized user account
And check now if you can connect to this share from your win10 (file explorer) by entering its full path

Code: Select all

\\192.168.1.10\yourprivatesharename\

Later if you succeed, can you check this time if all the shares are listed if you use now the address

Code: Select all

\\192.168.1.10

If you have this behaviour that means guest anonymous account is disabled with smb2/3 protocol on your win10
(see: https://learn.microsoft.com/en-us/troub ... by-default)

Other remark: if you enable Bonjour service (avahi) on the nas, your Mac hosts (finder) should detect it

[Cubytus]

OK I just checked that. Indeed, all shares save for one are private. So I typed the address

Code: Select all

\\192.168.1.10\tr-downloads

Same error as before.

Avahi is enabled by default since AFP is enabled too. It readily displays in the Mac, but always automatically connects using SMB protocol, which is annoying. The router never received the hostname (don't know if both are linked).

Now, even though I wasn't attempting to use the only public share, I followed the instructions you posted from Microsoft's website and added the

Code: Select all

AllowInsecureGuestAuth

key and finally the shares appeared after typing the IP + share name!!! :woohoo
Also works when typing the hostname.

When I double-click on a private share, it asks for credentials (normal, as I haven't stored them before). However, I would like it to NOT display those shares until properly authenticated, like it does on Mac.

So one part of the issue is solved, but avahi doesn't seem to perform its announcing job properly, as I still have to explicitely type in a hostname or address.