My network consist of multiple Windows 2016 servers (with domain) and Windows 10 clients.
The OMV is a fresh install, created a user, share etc. ... all pretty staright forward. The OMV machine can be seen in network neighborhood but when I try to access it I get prompted for username and password which is then rejected. I double checked and it is correct and the user is also give read/write privileges on the share.
I am aware of this guide: [HOW-TO] Connect to OMV SMB shares with Windows 10 - **Update - Loss of SMB Guest Shares** 11/26/18
But working through it not helped to solve the problem. Of course I cannot change the network type to private since it is in a domain. I enabled insecure guest logins, forced SMBv2 on Windows and OMV (with max and min protocol) and even installed SMBv1 support (again) on a Windows client for testing which not helped. I am really clueless.
Cannot access SMB shares
-
- OMV 4.x
- gelöst
- sebr
-
-
Have you checked this:
https://bgstack15.wordpress.co…ntlm-for-windows-clients/
HKLM\SYSTEM\CurrentControlSet\Control\Lsa
set to 3, 4 or 5 worked for me.
See here for definition
-
Thank a lot! That solved the problem!
-
-
Thank a lot! That solved the problem!
Which link? For future reference, what worked?
-
Have you checked this:
https://bgstack15.wordpress.co…ntlm-for-windows-clients/
HKLM\SYSTEM\CurrentControlSet\Control\Lsa
set to 3, 4 or 5 worked for me.
See here for definition
I need a bit closer at this, especially if it works in an AD domain. (AD domains have a good number of barriers set to prevent connections to unknown or rogue servers.)
Which level are you using (above) and which version of Windows client are you using?
-
Which level are you using (above) and which version of Windows client are you using?
Windows 10 Home
Currently I use level 5, but when I tested level 3 and 4 were also working.
-
-
What I'm getting from the errata seems to indicate that the same registry key works on Servers as well as clients.
This key seems to effectively erase AD domain boundaries for non-Windows servers.If you don't mind this should go into the Win10 How-To for tough client cases and AD domains.
-
Worked in this case, worked in my case, might also work in other cases.
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!