01-02-2013 07:41 AM
I'm having trouble connecting through wd2go.com. I've registered my 2tb My book and it shows up when I log in at wd2go.com but when I select view shares my browser (ie) just times out and doesn't show anything.
I'm using DHCP in my router and tried prot forwarding without using a static ip address. I've not tried a static ip yet and I've not used another browser.
Can anyone help?
Solved! Go to Solution.
01-03-2013 06:00 AM
Here is the status of my remote access.
Again when I'm on my WiFi at home I can connect through wd2go.com. I'm not sure if the internet connection at work is causing this problem. I'm going to get my brother to try it when he gets home and I'll report back.
01-08-2013 04:55 PM
I've been super busy so I've not had a chance to get my brother to try. He is going to try tonight to see if it is just my work connection that is causing a problem. I'll hopfully have an answer later tonight.
01-09-2013 12:25 PM
Could it be a possibility, that Java has to be up to date?
It worked now once on my PC, but I have set up a folder for my collegue and he has the same problem, when clicking on the device picture. "Page can't be loaded..." or whatever ;o(
01-09-2013 04:21 PM
No, he was not able to connect. This is really getting frustrating. I cannot connect to my drive unless I'm at home. WD2go.com doesn't work at this time and my mobile app on my tablet won't connect unless I'm at home either. Please, someone help. I've read the manual and tried everything it says and still nothing. I've been messing with computer since the late '80's so I know my way around. I've always liked WD products but this one is starting to doubt my perception.
I'll try updating my java but I don't think that's the problem. It's got to be either the drive or my router.
01-10-2013 02:31 AM
Still the same problem with my access.
Neither mobile is working (can't be connected - Error 504) and when opening the drive via web on wd2go.com, the browser crashes.
Same with my brothers, who I made a login for.
01-10-2013 05:37 AM
There appears to be a bug with UPnP within some routers that doesnt allow the MBL to create a UPnP entry for itself. Even though on the MBL GUI, it says "Port forwarding connection established", it might be showing this in error.
If your router has UPnP enabled, then disable it and within the MBL GUI select "Manual" connection method and then manually forward the two ports (80 & 443) to the IP Address assigned to your MBL. Always ensure your MBL has a static IP Address (either by assigning it via its MAC address in your Router, or select "Static IP" from within the MBL GUI).
I had the same issue a while ago, and it took me a while to find the cause and resolve it. You have to be sure you forward the ports within the router after disabling UPnP otherwise the MBL will resort to a relay connection (via WD's servers).
This issue isnt very well documented, but WD did admit to this problem a little while ago. It is admitted in this post: