WD My Cloud Drive Vanished from Network

When This Happens

You open File Explorer on your Windows 10 or 11 machine, click Network, and your WD My Cloud drive isn't there. Or you try the My Cloud web dashboard by typing its IP in a browser, and you get "This site can't be reached." The blue light on the front of the drive is solid, but it's like it got kicked off the party.

This usually happens after one of two things: a firmware update (the drive auto-updated itself to something like 02.00.00-xxx) or a router reboot. Power outage? Router reset? Yeah, that's the trigger. Last month a client lost power for 30 seconds and his My Cloud went dead on the network for two days until I showed him this.

Root Cause – The Drive Forgets Its Network Credentials

The WD My Cloud runs a stripped-down Linux inside. When the firmware updates or the router drops the lease, the drive's network configuration gets scrambled. It might still have an IP address, but it's a wrong one — a 169.254.x.x APIPA address, which means it's talking to itself, not your network. Or it's got the old router's gateway. The drive's SMB service (the thing that shares folders) is still running, but nobody can find it because the network layer is broken.

The fix isn't rebooting the drive or unplugging it. Those just repeat the same problem. You need to force the drive to get a fresh, correct network assignment.

Real Fix – Reset Network Settings and Set Static IP

1. Find your router's admin page. Open a browser (Chrome, Edge, whatever). Type your router's IP — usually 192.168.0.1 or 192.168.1.1. Log in with your admin credentials. If you don't know them, check the sticker on the router or call your ISP.
2. Find the DHCP client list. On most routers, it's under "Attached Devices" or "DHCP Leases." Look for something named "WDMyCloud" or "MyCloud" — the MAC address will start with 00:90:A9. Write down its current IP address if you see it. If it's not there, skip to step 4.
3. Reserve that IP as a static lease. In the same router section, look for "Address Reservation" or "Static DHCP." Add the My Cloud's MAC address and assign it a fixed IP — use the same one it had, or pick something outside the DHCP range, like 192.168.1.200. Apply the change. This stops the drive from losing its IP after future router reboots.
4. Reset the My Cloud's network config. On the My Cloud itself, find the reset button — it's a tiny pinhole on the back near the Ethernet port. Use a paperclip. Press and hold for 10 seconds while the drive is powered on. The light will flash orange then blue. Release. This wipes the network settings and forces the drive to request a new DHCP lease.
5. Wait 5 minutes. Seriously. The drive takes a while to boot and renegotiate the network. Go make coffee. Check the router's client list again — you should see the My Cloud with the IP you reserved.
6. Test access. Open File Explorer. Type \\\ in the address bar. If you set 192.168.1.200, type \\192.168.1.200\. You should see the Shares folder. If it asks for credentials, use admin / password (defaults) or whatever you set.

If It Still Fails

Try these in order:

• Check the Ethernet cable. I've seen a loose cable cause this. Reseat both ends. If you have a spare, swap it.
• Disable Windows firewall temporarily. Turn off Windows Defender Firewall for 2 minutes. If the drive shows up, add an exception for SMB traffic (port 445).
• Update the My Cloud firmware manually. Download the latest .bin file from WD's support site for your model (My Cloud, My Cloud EX2, etc.). Use the reset button method to enter recovery mode (hold reset for 40 seconds), then upload the firmware via the web interface at 192.168.0.1 (static IP during recovery).
• Check for IP conflict. If two devices have the same IP, one gets kicked. Ping the IP from a command prompt — if you get replies from a different MAC address, you've got a conflict. Change the reserved IP to something else.

If none of that works, the drive's motherboard might be toast. Had a client whose WD My Cloud Gen 2 just died after a firmware update — no light, no network. That's a hardware swap. But in 9 out of 10 cases, the reset and static IP fix works.