01-15-2014 08:02 PM
I used to be able to see my shares, but could not connect to explorer "Network name is not found"...
No I just get this: "error click for details"
Java permsission issue by the look of it.
I wish they would dump the use of java!
01-16-2014 10:51 AM - edited 01-16-2014 11:41 AM
Try uninstalling and reinstalling Java. Also try it with another browser.
01-17-2014 01:40 PM
Java 7 update 45
Control Panel >> Java >> Security >> medium
Java still displays that the wd2go.com certificate is outdated.
But it works now.
Tested with Internet Explorer and with FireFox.
01-22-2014 05:08 PM
This worked for me also - I hate to lower the security level to medium - any other thoughts???
I tried to enter the websir=te into the Java exception table but got another error that this didn't work because it was using multiple websites.
01-23-2014 01:45 AM
Even on medium security with various tweaks to parameters I can no longer access my brothers Mybook, over the internet. java just says certificate is out of date and will not be acceted until WD get a new one, latest Java installed today, but would not work even on earlier version.
01-23-2014 05:49 PM
I had a similar problem on my Vista laptop
I called WD MyCloud Support at 1 800 275 4932.
The rep said there is a known incompatibility with the Java 7 Update 51. He advised that I uninstall 7.51, and download and install Java 7 update 45. I did this and also updated Vista to the latest service pack.
Now WD My Cloud.exe can open my shared folders, but it is really slow to open my music files (.wav). A 37 Mb file takes 2'30" to open.
I an connect through the web app, after bypassing a couple of security warning dialogues from Java. Again the download time is very slow.
NOTE: on my iPad MyCloud app, the download is almost instantanious.
This is becoming incredibly frustrating. I get the same java errors and cannot access my drive outside of my home network. Based on other posts in this community, this has been a known issue for well over six months. Why is it taking so long to provide a fix? I'm quickly losing faith that WD has any intention of correcting the problem.