Support os x el capitan

[Ralphael]

@Ralphael

Connecting to the Cloud Locally without a fixed IP

The name of your Cloud is located under “Settings” “General” “Device Name”. The default is WDMyCloud. In theory when you first turn on your Cloud when it is connected to the router (give it a few minutes for your network to refresh), you should see your Cloud when you click on browse on both Mac and PC.

There is no longer a problem with El Capitan with finder.

Now remember if you don’t have your shares set up yet, then the only Shares you will find is Public. Eventually you will want to connect to your own private shares so read your manual.PC1. go to computers2. map network drive3. click on browse

Mac1. On the Finder’s menu, select “GO” and "Connect to Server"2. Click on Browse

Remember that the Cloud is really an endpoint device, meaning that if you don’t see the Cloud, it isn’t the Cloud’s fault if you haven’t plugged it in or the there are no Network roads leading up to the Cloud.

However theoretically for the most part you can just plug in your cloud using DHCP and access your device using the device name without a static IP. If you do somehow cannot find the cloud using the device name, then you have to check your router to see what IP it has assigned to your Cloud; this is much like an address on your house. If you don’t know the house address, then the cabbie won’t know how to get there.

Another reason that in previous Firmware Versions that many users could not see the device name in browse was that the cloud was busy performing its media scans. Remember to put a stop to the scans by using the methods outlined in the beginning of the post; everything just seems to be dependant on stopping those scans.

By browsing your “router” which you enter on Safari as 192.168.0.1 <== this number can vary with different households, you can find the ip that is assigned to your cloud. This is the same ip that you use for your dashboard on Safari, like 192.168.0.15 which brings up your Cloud Dashboard.

Once you get the ip, map by click on “GO” in your Finder Menu, then select “Connect to Server”

Type in your server Address, or click on Browse to see what is on your local network. At my house I am using a new AC WiFi Router on top of my existing internet router so what happens is that I cannot see my Clouds because they are on another network. I think this is the trouble that a lot of users get into. If you cannot see your Cloud using Browse, you can access your Cloud using an IP and you have to determine that IP on your own; either by viewing your router status or logging page, or by guessing and trying incrementally ip numbers on the safari page

here are some examples of mine
smb://192.168.0.16 <== this is a cloud that is set to DHCP and has gotten the ip from the old router

smb://WDMyCloud/Cloudy <== same cloud that was set to DHCP but you have to be on the same network i.e. 192.168.0 otherwise the name of the device WDMyCloud won’t resolve itself. This name is set on your Cloud Dashboard and the default is WDMyCloud. Cloudy is the share name that you create under shares.

afp://192.168.0.16 <== connecting using afp. AFP is slower for file transfers but quicker for huge directories like photos, ebooks or music. When I say huge, I mean 10,000 entries or more. Use SMB for all or most connections.

My Mac has two different network connections. When it uses WiFi, it has an ip of 192.168.100.26 <== notice the 192.168.100. When it is on ethernet, I use a fixed IP of 192.168.0.123 <=== notice the 192.168.0

So I think I covered everything. I had never had a problem with El Capitan through its various versions. I have a Macbook 12" that sleeps and switches between ethernet and Wifi with the clouds connected between the switching. I have another mac that is permanently connected to one of the clouds for my entertainment center that sleeps for most of the time.

None of my devices disconnects from my mac… unless… my router resets… then you might see a mapped drive drop out.

Good luck…