I have set up a My Book Live 2Gb drive with a fixed IP address and with two new shares. On installation, the firmware was automatically upgraded to the latest release, and this seemed OK. Access from local PCs was fine, so I proceeded to set up remote access as per the instructions. Everything seemed to go as it should, the account was created and verified and I can log in from a remote PC into WD2GO and the drive is displayed. When I select the option to show the shares, the web page just times out and eventually comes up with an error to say the web page is not available.
The implication of your answer is that an http connection should be working, so after having logged in to WD2go as usual and selected the option to display the shares, I waited till the web page timed out (as in the first post above) and then changed the URL to http instead of https. The connection then proceeded as expected and I was able to access all my files. So does this indicate that the cause of the problem is that https connections are being blocked by the firewall?
I’m relatively new to the My Book Live, but am having some issues accessing my content remotely. I think I’m getting further than others in this thread but I’m not 100% sure.
I’m able to log into the WD2Go website from an outside location. I’m also able to Connect my shared folder to my work PC (the outside location) and it shows up as a mapped drive on my work PC (which was super easy and worked great). I’m able to see all my files stored on the MBL, but when I try to open a file, Windows Media Player (for opening videos) just hangs and never plays the file I’ve selected.
Similarly, when I use the WD2Go app from an outside WiFi network, the same thing happens - I can browse my files through the app, but when I try to open them, the app just hangs.
I’m not very familiar with altering my router settings (port forwarding, etc), so if there was some sort of tutorial with screenshots and specific steps to take to solve this issue, that’s what I would probably need if I have to do anything too crazy.
Any help (in layman’s terms) would be appreciated. One of the main reasons I bought the MBL was to be able to access its content on multiple devices while outside my home network.
I am having similar issue, I can get the drive connected on the internal network no problem but when I try to connect via wd2go and connect to the drive, I can not open a file.
the dirve connects fine and I can see the files but it prompts me for a username and password in order to open a file. I have put in every UN and PW that I have. I even created new users with new privilages. do I need to enter a domain?
I added a picture to my MBL and tried to open it via the WD2Go app. Amazingly, it worked! Videos, however, still will not open. Is it because they’re too large? Would “port forwarding” help in this case to make the transfer of large files quicker?
I am still not able to open any files via my work PC. I am starting to get the feeling that this may be due to settings on my work network - - locked down for security reasons. I will have to try mapping the drive at home while connected to another WiFi network… just not sure how!
An update! The router which the MBL is behind is a Thomson TG585v7, which is not one designed to make things easy to use. I added filters on the firewall to allow FTP, HTTP and HTTPS server access to the IP address of the MBL, which I thought should resolve the issue. It didn’t. In the end, I went into MBL Dashboard, and under Settings, Remote Access, Configure; under Connection Options I set Windows XP compatibility. Remote Access now seems to work as it should. Which doesn’t seem to make sense seing I was trying remote access from a Windows 7 PC. I can also confirm that it does work from a remote PC running Windows XP.
XP Compatibility mode FORCES the MBL to use ports 80 and 443 (the other modes allow any available port to be used.)
IIRC, This is because Windows XP won’t allow a secure HTTP connection to anything OTHER than those ports when using WebDAV (which is the protocol WD 2go uses)-- Windows 7 doesn’t care what port it’s using.
This has not worked for me :(, tried setting it up manually to those ports too. I openned port forwarding, firewall and port triggering to the mbl ports 80 and 443. My router (netgear DGNG3300 matches the rule from my phone (android) on port 80 but the phone doesnt connect?
If WebDav can use any port for HTTPS connections, not just 443, how can you be sure that the firewall will not stop the traffic on that port? This is presumably the cause of the initial problem?
If the MBL were to be configured to use manual settings, rather than automatic, i.e to set the MBL to use ports 80 and 443, is this the same as forcing Windows XP compatibility? Should I use such manual settings rather than Windows XP compatibility?
