first of all: THANK YOU for this wonderful OS. It is really a great NAS. I love it!!!
Everything is running fine here with a fresh OMV 5 install. My version is regularly updated, current version is:
The only thing that REALLY bothers me are reproducible SMB problems. They occur once I reboot a windows 10 machine - current version:
Windows 10 Pro (64) version 1909 (Build 18363.1139)
Every time I reboot one of my WIndows machines, they start up with disconnected OMV 5 SMB shares. When this first occurred, I naturally assumed, Windows would be the culprit: I restarted the machines, reinstalled SMB 1 protocol, and tried a LOT of tweaks I found over the net.
At one point I thought: What about OMV 5? So I checked all info I could find and this lead me to flip the switch under SMB/CIFS that allows for the server to announce itself to Windows clients
(Sorry if this is not the proper English wording, I run OMV 5 in German)
This, unfortunately, did also not solve the problem.
In my desparation, I restarted OMV, even though I was able to log on via the browser and could see that all was running fine.
And I was surprised: The shares were visible in Windows after the OMV reboot.
Today, this happened again and I tried to find information about the way OMV is communicating its SMB shares . i found out that this is done via NetBios but could not find any preferences to adjust.
Then I tried one thing: I stopped the SMB server and restarted it manually.
The Windows shares popped up IMMEDIATELY.
So, I suspect something with the service announcing itself is not working in the way I would like the shares to behave.
Now, my questions are:
What is behind this?
Is there something I can do?
All I want is to make OMV behave like I need it: running quietly in the background, being present in the form of shared drives as soon I choose a shared drive.
Again: Thank you VERY much for OMV. Even more so if you can help me solve this very annoying problem.