I’ve been reading how people have been bricking their devices by entering a bad fixed IP on their devices and subsequently not being able to access the device at all.
Now since I haven’t tried this, I have no idea if it would work, but if anyone that has a bricked Cloud due to a bad fixed IP and cannot reset, lets give this a try.
1 PC or Mac with ethernet connection (cannot be wifi)
1 bricked Cloud
As I’ve discovered, which is a nice feature of the cloud, is the ability to connect it directly to a PC/mac and it will autoconfigure itself without needing crossover ethernet cable.
So connect the pc with the WD cloud
what we want to do in step 3 is to discover the wrong IP and subnet that you have entered. If you know the numbers go to step 4.
2a. on the PC, go to the type in area for search program and type in cmd to get to a command prompt
2b. on a Mac, go to Application, Utilities and select Terminal.app
- type arp -a (this will possibly show all the devices ip that is connected to your computer).
Now if your computer doesn’t match the subnet of the WD cloud, arp might not return any information, but you can play around with a fixed ip on your computer without any danger to your computer. When you are done, just reset your computer to DHCP.
Try different subnets which is usually variations of 255.255.255.0 or even 0.0.0.0 because you typed it in wrong. If you can get a response from the WD Cloud to give up the numbers then you halfway there.
3b. It is a possibility that your router may log the ip and subnet mask as it is attached. So try logging into your router to see the logs on what activities and attempts have been made. If you are lucky and do get the ip and subnet masks, then you might be able to web/ui or ssh into the bricked device.
- you got the IP and subnet? great!! so lets change your IP and subnet on your computer to a fixed IP that is one digit different from your WD Cloud.
so lets say your WD Cloud is set to 192.168.1.240 subnet 255.255.255.0 we can set your PC to 192.168.1.241 with a subnet of 255.255.255.0
- now bring up the web browser and type in 192.168.1.240 and hopefully that might bring up the WD Cloud UI… and if it does… change it back to DHCP
optionally just try wdmycloud.local on your web browser…
Logic behind this is that you want to be in the same subnet mask (this is the second set of numbers when you enter the fixed IP address) as your WD Cloud. Different subnets is usually the reason that you cannot see each other or the router being unable to recognize your device. The other problems are incorrect gateways, incorrect DNS etc. But if you can get on the same subnet, and you know the IP, then you can activate the web/UI and reset the fixed IP to DHCP.
Good luck… if this does work… come back and tell me so… if it doesn’t work… come back and tell me so…