This said, I do not need to make these kind of changes on my Windows 10 PCs when accessing a SMB shared drive residing on a commercial NAS. To me it is clearly a Windows 10 issue as I can access the OMV's SMB shares with Windows 7, macOS High Sierra, Ubuntu MATE without any additional setup. This did work for my PCs running Windows 10 Home and Professional back some time ago. Have a look at my posting ' Windows 10 Creators failure to locate CIFS/SMB shares' to workaround the issue you're facing by simply launching the 'Local Security Policy' tool, and under the branch 'Security Options' and then under the option 'Network Security: LAN Manager authentication level', just change the settings from 'Send LM & NTLM - use NTLMv2 session security if negotiated' to 'Send NTLMv2 responses only'. Why wild guessing when you can have a look what's going can you confirm that Event Viewer -> Applications and Services Logs -> Microsoft -> Windows -> SMBClient provides reasonable information with Win10?

' message the name resolution part is already resolved and it's about permissions or something elseĪlso just like any Unix or Linux out there Windows has logging functionality (Event Log - has been enhanced/fixed wrt SMB connection problems years ago).

If then you get the ''Windows cannot access.

If this resolves to the IP address of your OMV box, then try to access \openmediavault.local.

In cmd.exe (or whatever the Windows command line is called these days) execute ping openmediavault.local.

If this resolves to the IP address of your OMV box, then try to access \openmediavault.

In cmd.exe (or whatever the Windows command line is called these days) execute ping openmediavault.

Is it an issue with service propagation/location (name resolution)? Or something with permissions? To nail this down you could try some steps on each Win10 host and compare: In general it's a good idea to try to see at which stage a connection attempt is failing.

Hp connection manager and windows guest