I am going to try this one last time before giving up. I have a setup of OMV on ESXi on a Dell PowerEdge r720 server everything is set up and working properly except for one thing, which for me is the most important thing, I need a secure connection from a Windows 2016 server to a shared folder on the OMV. I have tried just about every configuration I can think of and with the help of several others on these forums have tried just about everything imaginable and I still cannot connect to a secure folder via the 2016 server. Does anyone on these forums have experience with Windows 2016 server connectivity issues, and has found a way for this to work?
Connectivity issues with Windows 2016 server connecting to OMV on ESXi
-
-
I don't know what you mean exactly when you say secure connection. But take a look at this thread, maybe it will help you.
-
Well I have OMV5 on ESXi with just two shared folders; one for staff, one for private. All machines BUT my Windows 2016 server can attach to both the staff (unsecured) and private (secured) folders with the proper credentials. Only the Windows 2016 server cannot access the private folder. I attempt to connect and I get the typical windows credentials popup. Once I get past that, I can't log onto the private share. I have tried the reg edit of the allowguestaccess thing, but still nada. I have SMB2 enabled, but I did try SMB1 and 3 on the server and still nothing.
-
-
OMV5 SMB NOT ACCESIBLE ON WINDOWS SERVER2019
Take a look here, maybe it's the same problem.
but I did try SMB1 and 3 on the server
I would not configure SMB1, it is insecure.
-
OMV5 SMB NOT ACCESIBLE ON WINDOWS SERVER2019
Take a look here, maybe it's the same problem.
I would not configure SMB1, it is insecure.
I tried this (many times) no joy! SMB1 is *NOT* enabled...
-
The OP of that thread got it somehow, and I don't know how. I hope he still responds, it is a recent thread. We should have asked him how he did it before we considered the thread resolved. It is a pity that the threads often do not provide all the information for the one who comes after.
In any case I am convinced that the problem is with Windows Server. Can you check if the domain configuration influences the problem?
-
-
The OP of that thread got it somehow, and I don't know how. I hope he still responds, it is a recent thread. We should have asked him how he did it before we considered the thread resolved. It is a pity that the threads often do not provide all the information for the one who comes after.
In any case I am convinced that the problem is with Windows Server. Can you check if the domain configuration influences the problem?
I am also convinced that is it the Windows server as well. I have been working on this for over 2 months now with no resolution. I have tried everything from regedits to allow guess access, allow insecure guest access, tried SMB1-3 - everything! I can get to public, non-password folders no problem, it's the protected folders that I can't seem to into. I get the usual windows security popup (which I don't think I would be getting since it's a samba share) and I have had many very helpful volunteers on here do screen shares with me on here to no avail. They too scratch their heads in disillusion. This seems to be a common topic on OMV forums, yet no one seems to have a resolution. It's just mind-boggling that windows 7, windows 10 machines can connect to this protected share, but not my server?
-
Soma posted a link in the other thread.
https://social.technet.microso…ows-server-2019-smb-share
I just read at the bottom of the page that someone managed to solve it by enabling insecure guest access. I don't know if this would solve your problems. You saw it?
-
Soma posted a link in the other thread.
https://social.technet.microso…ows-server-2019-smb-share
I just read at the bottom of the page that someone managed to solve it by enabling insecure guest access. I don't know if this would solve your problems. You saw it?
Yeah I saw that, tried it, still nada
-
-
I found this.
[HOW-TO] Connect to OMV SMB shares with Windows 10 and Microsoft Servers
I downloaded the document and read it (as best I could, in my poor English).
It is old but it seems that this problem comes from a long time ago. Which reinforces the theory that the problem really is in Windows Server and its historical restrictions in its battle with Linux.
If you want to read it, notice that it talks about domains, and also configure it in OMV as WORKGROUP.
-
I found this.
[HOW-TO] Connect to OMV SMB shares with Windows 10 and Microsoft Servers
I downloaded the document and read it (as best I could, in my poor English).
It is old but it seems that this problem comes from a long time ago. Which reinforces the theory that the problem really is in Windows Server and its historical restrictions in its battle with Linux.
If you want to read it, notice that it talks about domains, and also configure it in OMV as WORKGROUP.
I've read it - still no help.
-
I have curiousity. Is the problem only with OMV or any Linux system? Have you tried from Ubuntu, Linux Mint ...?
-
-
I have curiousity. Is the problem only with OMV or any Linux system? Have you tried from Ubuntu, Linux Mint ...?
Good question. I used "best practices" using debian 64 bit as the OS. Haven't tried anything else.
-
I have tried just about every configuration I can think of and with the help of several others on these forums have tried just about everything imaginable and I still cannot connect to a secure folder via the 2016 server.
It is known (from what I've seen) that Windows Servers have problems.
(There are several threads about the same and no perfect solution, if any)
So:
Have you considered alternatives to SAMBA?
You can try to create a NFS share and mount that share just to the Windows Server (or to the Clients that you want)
This is something I came across, never done it ( last time I ran Windows Server was v2008 )
How To Provide NFS Network Shares to Specific Clients (rootusers.com)
How To Mount An NFS Share In Windows Server 2016 (rootusers.com)
Those "HowTos" seem simple and well written. Just have a reading and see if it fits your need,
-
It's an interesting idea, but I am trying to transfer files FROM my Win2016 server to the OMV5 secure share. Incredible that there is not an easier way to do this?
-
-
Incredible that there is not an easier way to do this?
Has you can see, even googling a bit (lot) there is still no straight answer/solution to what you want,
Or you can try to make "samba" an "active directory domain controller"
samba-ad-dc isn't install with OMV so, if you want to try it, run on a VM or a spare rig (an extra Pi that you might have or other SBC)
Doing this on OMV will probably kill your installation (it disables the systemd-resolved smbd nmbd and winbind)
How to deploy Samba on Linux as an Active Directory Domain Controller - TechRepublic
Really don't have any better options,
-
What user are you logging into the Win2016 server
-
What user are you logging into the Win2016 server
I have tried both a domain and non-domain user, I just wiped the entire VM. I have tried so many things, probably best to start over (if possible)
-
-
I have tried both a domain and non-domain user
That's interesting, a domain user particularly the domain admin I would expect to fail, but a local user belonging to the admin group (not domain admin) should work.
I used OMV with server 2012, when we replaced the server, the old server was deployed with OMV as a backup using iscsi target. I set up a new user on the Windows server and used the same user name on OMV and it worked well.
-
That's interesting, a domain user particularly the domain admin I would expect to fail, but a local user belonging to the admin group (not domain admin) should work.
I used OMV with server 2012, when we replaced the server, the old server was deployed with OMV as a backup using iscsi target. I set up a new user on the Windows server and used the same user name on OMV and it worked well.
You set up a new "local" user on the server?
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!