I have a MBL and it was working fine. I use it to stream files to my apple TV. i cannot connect to the MBL in win explorer. I am still able to see it w/ the apple tv tho. i can still play files from it.
i can ping it. 10.0.0.106 pings. i can connect to the UI in a web browser.
when i click network under settings it says “no internet access”.
if i set it to static and then back to dhcp it will have internet access.
then it only shows up under storage in win explorer. i cannot access folders or map a network drive or anything like that.
i’ve seen A LOT of topics on this w/ few to no resolutions.
is the drive just bad? none of the data is really crucial. should i just buy a new one? why does this seem to happen to MBL often? they cannot be accessed in windows anymore after a while.
i plan on contacting support but doubt they will be able to help me.
If you can access the dashboard as you mentioned, under windows explorer (not IE), type:
\\10.0.0.106
If that works, map a share using that IP.
Most of the time, if set for DHCP, if the IP changes, DNS does not get updated for whatever, reason. Usually can be fix by flushing DNS on the clients, but all can be avoided by setting MBL to static, or making a DCHP reservation on your DHCP server which is usually your router.
Now, to access MBL in the LAN, no need for internet access. Internet access on MBL is only needed for remote access (WAN) and automatic firmware updates (WAN as well). If you have internet access under DHCP but not static, a setting is not correct for static IP.
And no, your drive is not bad (at least I do not think so). However, that is not excuse to not have a backup of important files regardless of NAS brand.
If none of the above fixes the issue, samba service might be hung. From Dashboard, reboot device. Whatever you do, DO NOT JUST UNPLUG the power cord.
in windows explorer , when i would type that - it would just bring up the UI interface.
i was messing around w/ this for hours and i finally got it to work.
i restarted the MBL, it still says no internet access.
i opened up wd link - and was able to map the drive in there.
i have 4 shares - all 3 were mapped except for Public for some reason. so i mapped public to E: and then i was able to access it in win explorer.
also, i’m running the short diag on it and it is hung at 90%.
not sure why that was happening but it seems to be working now.
