by hostname I get error:
"\\omv.domain.com\SHARENAME is not accessible. You might not have permissions....."
in same box..
"Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. DIsuconnect all previous connectos the th server or shared resource and try again."
by IP I get in.
**I have been deleting connections in "net use" on the windows client between each test. By hostname of the OMV box it just doesn't work. 
If your local router supports local DNS, you'd access your server as in the following example:
\\OMV-Luray\
Based on the following setting:
Otherwise there's nothing wrong with connecting using the IP address.
Sometimes (not sure when) you have to add a .local
\\OMV-Luray.local\
\\OMV-Luray.local\
Good point.
In X86 builds, "local" is the suggested default domain suffix during the Debian OS setup. Since I'm peer-to-peer (no domain) I clear out the field.
SBC's are built in another way where the default (local) is probably still in place.
In any case, a domain suffix is another item that may or may not be supported by a consumer router. One way, or the other, it should work.
Alles anzeigenIf your local router supports local DNS, you'd access your server as in the following example:
\\OMV-Luray\
Based on the following setting:
Otherwise there's nothing wrong with connecting using the IP address.
Good point.
In X86 builds, "local" is the suggested default domain suffix during the Debian OS setup. Since I'm peer-to-peer (no domain) I clear out the field.
SBC's are built in another way where the default (local) is probably still in place.
In any case, a domain suffix is another item that may or may not be supported by a consumer router. One way, or the other, it should work.
We have FQDN and dedicated DNS for our environment.
In the boxes of screenshot from @crashtest we have
Hostname: omvhostname
Doman name: our.domain.com
The server address is \\omhostname.our.domain.com
But as I said, doesn't work.
OMV is the only app/server we're having issues with.
Thought someone here might know why or a trick to get it going... I'll keep troubleshooting it locally.
If you have DNS, most servers do the translation from any name in their table (to include aliases) to IP address.
I don't have any ideas. Sorry.
If you have DNS, most servers do the translation from any name in their table (to include aliases) to IP address.
I don't have any ideas. Sorry.
Rebooted the DNS server and it seems to have worked the bugs out. 
It's strange because I was able to resolve the FQDN for omvhostname from the clients just fine. Whatever. "did you try turning it off and on again?" wins again.
that's the part that has to be wrong even in a windows domain environment it's <domainname>.local so for instance our school domain is schoolname.local for the school, however depending on what being done sometimes just the <domainname> without the local will work.
We're using a real/valid domain. Maybe issue you're talking about is related to dns domain suffix search list in your environment?
"did you try turning it off and on again?" wins again.
Yep. Sometimes a reboot can do the trick.
Back in my Windows days one guy I knew always said; "Rebootion is the Solution".
Yes, but I think it is a bit exaggerated that I have to restart my car every now an then
I hope it is not running Windows
We're using a real/valid domain. Maybe issue you're talking about is related to dns domain suffix search list in your environment?
That's why I deleted the post when the brain kicked in
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!
