Shared folder not accessible from Windows

1st Official Post

    Hi, hoping someone can help me out with a SMB / CIFS issue.


    I am running OMV5 (Raspberry Pi Lite OS) on a Raspberry Pi4, which is connected over wired Ethernet. Full disclosure - I have not set a static IP address to date, and the server has run faultlessly for 2 years or more despite that.


    I was able to access my network shared folder from a Windows PC up until yesterday 03/09/25 and all was working fine. Since that time, I have changed my Modem / Router which has obviously allocated a different IP address and I can now no longer access my shared folder from the Windows machine.


    I am able to log into the web interface using the new IP, the Pi is able to check for updates, the Mini Dlna plugin is serving media over the network just fine but the shared network folder is no longer accessible from Windows. I am also certain Windows has not installed any updates since before the network share was working ok. I have tried deleting the network share, disabled the SMB / CIFS service, rebooted and then re enabled / recreated it to no avail.


    I am sure I have made a simple rookie error, but nothing I have been able to try has resolved the issue. I should also say that I can no longer ssh into the Pi using my usual hostname and password either? Any help gratefully received, please keep in mind I am a rookie. Many thanks.

    It sounds like the new router is not resolving hostnames to ip addresses. Not all routers do that.


    If you want to continue using hostnames instead of the ip address of the server, you can try appending .local (or whatever the workgroup/domain name is in place of "local") to the end of the hostname, or you can set up a local DNS server/forwarder for your LAN like pihole or dnsmasq and have your systems use it as the primary dns server.


    Personally, I would set the ip address of the server to a static reservation in the router and us the ip address for all connections.

    Asrock B450M, AMD 5600G, 64GB RAM, 6 x 4TB RAID 5 array, 2 x 10TB RAID 1 array, 100GB SSD for OS, 1TB SSD for docker and VMs, 1TB external SSD for fsarchiver OS and docker data daily backups

    Many thanks for the reply. I certainly think the Router is the problem, but it was a routine replacement of the same make / model as before - I am sure the Firmware might be different.


    Anyway, I have reserved the IP from within the Router, I also noticed that the Friendly Name (hostname) 'omvserver' is there in the device details. From within the omv web gui, I tried to append .local to the hostname, but OMV would not let me do that (invalid hostname). I am able to access the shared folder by using the IP address in file explorer and have mapped that as a Network Drive and so I am at least functional now.


    I remain a little perplexed; all Dlna devices on the network can see Minidlna and Minimserver running on the Pi, I used to be able to see and expand these from within Windows file explorer but they are also no longer accessible. When time permits, I will try and reconnect the old Router as it was working fine before.


    Thanks again for taking the time to reply, I appreciate it.

Participate now!

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

Register Yourself Login