So after many years of WD cloud/live usage, I can say with 99.99% certainty that it isn’t the cloud fault even though it may look like it; i.e. plugging in the cloud the internet goes down, unplug and the internet goes back up.
- make sure you switch off static ip and set it to DHCP. (This is to remove any DNS ip assignments of which I have now come to believe to be the main cause of all troubles)
- make sure you turn off all reserves or at least check that you don’t have reserves for the cloud.
- if you are using reserves, make sure you set them outside the range of the DHCP. e.g. DHCP assignments from 192.168.0.10 to 192.168.0.100 and reserves set at 192.168.0.150 and so on.
- Shut down your cloud
- reboot your router
- unplug any USB attached drives
- start up the cloud
If you hear the cloud gurgling, the sound the cloud makes when it is scanning for files and you cannot get access to the cloud, yes it could be the cloud being very busy with the scans.
You could SSH into the cloud to turn off the scans… or
upon boot up and once you are able to access the dashboard,
- turn off cloud access
- turn off media switches like iTunes, DLNA
- reboot and wait for your cloud to settle
If you are setting a static IP, the DNS servers are usually pointed back to the router 192.168.0.1 which is generally the safest. However you can point it to google DNS servers which are 184.108.40.206 and 220.127.116.11 which may or may not make your cloud faster. This is debatable since your router DNS servers may point to somewhere ISP internally and may be slower than Google DNS servers. On the latest cloud firmware, there is a button that you can click to set it to Google DNS.
This is what I’ve discovered over the years.
If your internet is down, i.e. router cannot connect to the internet but the router is still connected to your cable ISP server, all external DNS services will be unavailable… thus if you are pointed to Google DNS, your Cloud may lock up while accessing any files. Why? I am guessing that it uses the DNS services to confirm the data route. Yes this is exactly what happened to me. The first few seconds of a movie would play then it would lock up making me think that the Cloud hard drive is encountering errors. I can still see the directory, but just cannot access the files.
The other problem when using google DNS is when you don’t have internet, you won’t be able to resolve the address of your cloud with yourcloudname.local
Pointing the DNS server back to the router does seem to eliminate the problems. i.e. DNS servers 192.168.0.1
Also, putting a switch between your router and all your devices at home will prevent your home network going down when your router/internet goes down. For my pervious older router, when the internet goes down (at the ISP server point), my router would reboot causing my whole home network to go down. A switch separates the router from my home network.
Thus I could take out the router and still watch a movie streaming from my Cloud to my mac.
I have also added an Apple Airport Extreme to handle the AC Wifi on my home network, thus wifi is separate from my router/modem. The router/modem still handles the DHCP as well as handling the ports.
You can use google DNS or OpenDNS servers for the quicker responses but if you encounter problems, switch it back to 192.168.0.1