plugout.net

I there,

for once in a very long time, I need to access my fvdw-powered NAS from Windows 10. So I disabled the "Turn pff SMB while AFP is on", and checked the SMB server ws enabled from the status table, but alas, Windows 10 can't see it and can't connect to it. It gives unspecified error code 0x80004005 right away, not after a few seconds as I'd expect from trying to "talk" to the NAS.

Same result for \\fvdwsl-base.local and for \\192.168.1.10 (fvdwsl being finicky with hostname propagation)

Insights?

Hi Cubytus,

can you post the output

Code: Select all

 ps axf|grep mbd

Can't do that either. I have no SSH access to this fvdwsl-powered NAS since this is a Windows. Any option I could check from the web interface?

You can install and use a program like putty to get ssh access whenbusing windows

Here is the result

Code: Select all

root@fvdwsl-base:/ # ps axf|grep mbd
20406 pts/0    S+     0:00          \_ grep mbd
19248 ?        Ss     0:05 /usr/sbin/nmbd -D -l /var/log/samba
19251 ?        Ss     0:00 /usr/sbin/smbd -D -l /var/log/samba
19257 ?        S      0:00  \_ /usr/sbin/smbd -D -l /var/log/samba
19258 ?        S      0:00  \_ /usr/sbin/smbd -D -l /var/log/samba

EDIT:dual posting.

Well samba is running. Likekely you us samba 3.0.37 which uses smb1 protocol. Windows 10 has that protocol disabled by default. You can enable it in windows. Se for example here https://zappiti.uservoice.com/knowledgebase/articles/1830778--network-smb1-sharing-protocol-on-windows-10

In fact, it's running Samba 4.10.18-patched, and protocol 1 is disabled...

Error code 0x80004005 in win10 means problem with sharing files in a network.
Did you enable sharing in win10?

See for example here https://appuals.com/solved-how-to-fix-error-0x80004005/#:~:text=Error%200x80004005%20is%20translated%20as,Windows%20Updates%20fails%20to%20install.
Point 2

There are more sites describing this problem

I have 5 SMB-shared devices on this LAN (LibreELEC, OMV, Synology, fvdw, another Win 10 Pro PC). All are invisible except one (first problem with Windows 10). The only visible one runs OpenMediaVault. However, all are accessible when I type their address directly in Windows Explorer except the fvdw-powered NAS (so that's a fvdw-related issue). On the Mac (not sharing anything via SMB), all 5 devices are visible and accessible.

I added the LocalAccountTokenFilterPolicy key, to no avail. I have no "Microsoft 6to4 devices".

Would it have anything to do with hostname propagation or Bonjour browsing? It wouldn't be the first time fvdw has trouble being seen on the LAN, doesn't show its hostname right away (or at all) to the router, only allows connection through its IP.