Why does my My Cloud keep disappearing from my network?

I try to browse to either \ip address\path or \nameOfMyCloud\path and I can’t. I can ping the IP address. I get “Windows cannot access…” error. In the past, I’ve rebooted and it has resolved – but it seems I have to do this EVERY time. Why is the My Cloud so hard to use on Windows 10, and it seems to be getting harder over time?

Why is this such a difficult thing?

I had a similar thing happen to my My Cloud plus other devices in my house.

Resolved it by going into my Modem/Router’s advanced settings and finding an option called … Address Reservation

I was able to find the My Cloud’s IP (and MAC Address) and assign it a local static IP number which never changes and does not conflict with other devices.

Did this for every other device in my house … haven’t had anything drop off the network or change IP address or cannot be accessed since. :slight_smile:

Couple of general troubleshooting suggestions. Like the previous person suggested, access your local network router and assign/reserve an IP address for the My Cloud. Each time the network or My Cloud is rebooted it should then be assigned the same IP address.

Microsoft may have disabled SMB1.0/CIFS in Windows 10, reenable this option to see if the issue resolves itself.

How to Enable SMB 1.0/CIFS File Sharing Support on Windows 10

Temporary disable any security/antivirus software. Some of these programs may interfere with accessing local network devices.

Make sure the Network Type on the Windows computer is set to Private and not Public.

Because the MyCloud software is using Linux, is several years old, and is not being updated to maintain good Win10 compatibility. As suggested above; I think MyCloud primarily uses SMB (SMB1?) for communication. . . and Windows is moving away from that protocol for security reasons.

Having said that. . . .
* I have no trouble accessing drives using \ipaddess or \NameOfMyCloud
* No, I do not regularly “see” the MyCloud devices on the Navigation pane of Windows explorer
* I do use static IP addresses
* I have been forced to disable IPV6 on all machines (don’t ask me why I had to do this - - → but I did)
* I do have SMB1 specifically enabled on all machines
* I verified that the “workgroup name” for all devices is the same (they got messed up once)
* All Win10 devices treat my home network as a “Private” (home) network.

MyCloud runs on Linux (as does most of the internet btw :-). It can use SMB or NFS to share files. It runs Samba 4.3.11 (which you can verify by ssh into the MyCloud and running smbd -V) and will negotiate SMB dialects to 3.02 which is good enough for local networks. SMB1 has been deprecated by Windows, which is why it is disabled by default on recent Windows. SMB1 has security issues; version SMB2+ have improved copy functions, performance etc. For Mac users, Samba 4.3.11 has enhanced functionality & compatibility IF you force dialect SMB2 or higher.
There is a certain irony that Windows users are recommend to re-enable an old SMB1 that was replaced by SMB2 in Windows Vista in 2006…

Well, us poor windows users like to see the my cloud products show up in the “file explorer” navigation pane.

Apparently, the only way to make that happen is to have SMB1 enabled.

I saw apparently. . . because I don’t think it works 100% of the time. (I can always access by typing the ip address of the drive)

I sympathize, but it has been years since I had to use windows, but I did find this site:

…which if you skip down to the summary basically says to:
Set the startup type of the Function Discovery Provider Host and the Function Discovery Resource Publication services to Automatic

Been there.
Done that.

meh

NAS_user,

IP address is and always has been reserved, for this and some of my other devices. I have, in the past, re-enabled the SMB 1.0 support – not sure why that doesn’t stay re-enabled, but I’ll try it again. Disabled my firewall (Norton) - no change. Network type is private.

I should’ve mentioned that I’ve been through all these things, before. That’s why I’m so frustrated.

You probably need to run Wireshark https://www.wireshark.org/ to capture the protocol that allows the mycloud to be seen by File Explorer in the navigation pane.
On my Macs, I mount the mycloud using the smb://user@mycloud/share format…it stays mounted, is always visible in Finder (sim. to your File Explorer), always available.
In /etc/samba/smb-global.conf I have disabled the whole netbios structure:
disable netbios = yes
dns proxy = no
smb ports = 445