My Cloud does not connect to network

My Cloud OS 3 Personal & Network Attached Storage My Cloud Mirror
1

Yesterday I received and installed my My Cloud Mirror device by following the (very short) installation manual.

It is hooked up to an Asus (RT-N66U) router using the included network cable.

The blue leds on the front of the device all light up solid (HDDs + Power).
A green led in the back also shows the device has successfully setup a network connection.

However when trying to perform the setup (My Cloud) the device is never detected (tried from several devices, all of which Windows 10 laptops/tablets). Unfortunately I was not able to use a mobile device to try this as Edge browser is not supported (boo!) and all our phones use Windows 10.

Also the device is not part of the list of clients of the router, which makes me wonder why the device would indicate it successfully has established a network connection.

The only thing the router log shows is a device trying to connect using an IP (192.168.192.54) which is outside the subnet mask (255.255.255.0, 192.168.2.*). However, I am not sure this is actually the My Cloud trying to connect.

Obviously the router is configured to act as DHCP and provide dynamic IPs to clients.

Is it possible the My Cloud uses a static IP out of the box? What else can I try?

Edit: Note that I have tried to reset the device using both available methods (4 sec hot reset, 40 sec cold reset)

2

First thing I’d try is a different cable. Either that or try connecting the MCM directly to the Ethernet port of one of your laptops and see if it can see it that way. But I would suspect you have either a dodgy cable or less likely a dodgy port on your router (that can be easily checked by moving it to another one, or checking the existing port with another device like a laptop).

The MCM by default should get its address etc by DHCP - you have to specifically set it up via its dashboard to be static.

The only other thing I can think of is if you’ve got mac address filtering or something like that on the router. Unlikely I guess, but worth mentioning.

1 Like
3

Changing the cable fixed the issue!

I feel silly for not thinking of this myself, however I was not expecting a brand new cable provided with the device not to be working… assumptions… assumptions…

Thank you very much for your help.

4

You’re welcome, glad it’s resolved :smiley:

It happens more often than you’d credit (and not just WD) for such peripheral and add-on stuff, hence being the first thing to eliminate. Any pre-shipment testing the device gets will almost certainly not involve the cable that’s in the box.