Can't access share via IP address

    Hello. Tried OMV v5 and v6 without success. I create a SMB shared folder and I can access it via \\OMV\Folder but not with \\192.168.0.238\Folder

    When I do


    ping omv


    I see such replies


    Pinging omv.local [fe80::20c:29ff:feea:2222%14] with 32 bytes of data:

    Reply from fe80::20c:29ff:feea:2222%14: time<1ms


    But in the config I see that IPv6 is set to disabled.


    What's wrong with this software? How can I access a shared folder via OMV's IP?


    When I enabled-disabled IPv6 it became truly disabled, so now ping looks ordinary


    ping omv

    Pinging omv [192.168.0.238] with 32 bytes of data:

    Reply from 192.168.0.238: bytes=32 time<1ms TTL=64


    But funny thing, now I can't access my share even via name \\OMV\Folder

    Looks like OMV became undiscoverable - I don't see it in Network anymore.


    There's a bunch of shares from Windows PCs in my network, and they work fine via IP.

    perhaps can help: Windows 10 Creators failure to locate CIFS/SMB shares

    Thank you for the reply, but I don't quite follow what should I do with that. If you mean I need to enable SMBv1.0 client on the PC I try to access OMV share from - it's enabled. The only one example of paths there is using name, not IP (net use V: \\OMVCPUNAME\SHARENAME /PERSISTENT:YES). And as I said - after disabling IPv6 (no other settings were be touched) I can't access my share even via name, and OMV is no more visible in Network discovery. As I don't understand how it could be Windows' issue when I tweak OMV's settings and suddenly things that somehow worked prior, now became inaccessible.

    Youtube videos about OMV is strict and simple: create share, enable SMB, pick created share it its settings and it is that. Yet again: I can access shared folder created on other Windows hosts, but can't access shared folder created on OMV host. But peps in that thread suggest it's clients (my Windows) issue, not servers (OMVs).

    Sorry for brag, but my intention with OMV was not install Windows to create shares, but install specialized system, where it should be more reliable and simple.

    strange things happens on latest update if disble IPV6: RE: warning during updates

    If you use the built in File app on iOS devices you can access smb shares on OMV.

    In the file app, if you can’t find the default file app, go to App Store type in search type in File and hit enter.

    The default Apple file app will be the one with a plane blue folder -Files.

    Developer is APPLE.

    CLICK OPEN, in the left side bar click the … in a circle, click connect to server.

    In the top address bar type in your NAS server address: should be something like smb://192.168.1.10/Storage/Personal/User

    Then choose the share/username and password for the share you want.

    I do this making a folder for individuals in the household, making a user folder and password for each.

    That way my wife can download/back up the millions of pictures and videos she takes of grad kids and cat from her iPhone.

    Quote from zaqik

    Thank you for the reply, but I don't quite follow what should I do with that.

    As I don't understand how it could be Windows' issue when I tweak OMV's settings and suddenly things that somehow worked prior, now became inaccessible.

    But peps in that thread suggest it's clients (my Windows) issue, not servers (OMVs).

    Sorry for brag, but my intention with OMV was not install Windows to create shares, but install specialized system, where it should be more reliable and simple.

    Oh Boy, where should i start with?


    First of all, i would kindly suggest to dig deeper into some basic networking knowledge, teaching yourself, what is an IPv4-Address

    and what is it needed for. Openmediavault must be installed on a static ipv4-address! (IPv6 could be completely disabled in your LAN)

    The Client to access openmediavault can be Windows, Linux, Mac or anything else, as it only needs "SMB" or "NFS" (CIFS) - Support.

    The Server (like you consider omv correctly) is offering different services on different file systems (FAT/NTFS/ext4).

    To fully obtain access to a NAS, you need "File Sharing" in Windows enabled, and - regardless what operating system you are using - a stable IP-subnet of your network adapter with classic IPv4 like "192.168.178.x". Linux Computer do come with pre-installed SMB-Client, so no need to tinker with!

    Your PC and OMV should be part of the same IP-Subnet, like mentioned above (PC = 192.168.x.1 and OMV=192.168.x.x)

    DE | EN; 81er Jahrgang Spätlese, OMV Bastler, erfahrener PC-Geek, Linux begeistert, mag alles was Strom oder Netzwerk braucht 8o

    sorry my friend, good try, but the Threadopener needs more "basic help" regarding simple usage of Local Area Network, don' t you think?

    DE | EN; 81er Jahrgang Spätlese, OMV Bastler, erfahrener PC-Geek, Linux begeistert, mag alles was Strom oder Netzwerk braucht 8o

    Not sure what you mean there but this works for me. I hope I didn't confuse you, or maybe I had dumb luck.

    To make clear, hat is the /Storage/Personal/User is the relative share on the OMV storage.

    Under services, SMB/CIFS shares enabled.

    Sorry for the delay been traveling...

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!

Register Yourself Login