Working fine on home network - laptop, ps3, wdtv live media player etc…
Works great on iphone and and android phones aswell as google nexus 7 tablet, both on the home network and remotely using the wd2go app.
Here is the problem - When I am in work, i log in fine to wd2go, i hit ‘open in explorer’… I am able to see the files, but i am unable to play them or copy them. I notice that the device is mapped as a FAT device and is displaying the storage capacity of my local C:/…
I have read on here that loads of people have similar issues and it seems to be a webdav issue, maybe?, but i just cannot seem to find a solid solution to it… Can anyone help?
When you’re using WD 2go, all the things you describe are “normal.”
Copy can LOOK like it’s not working, because Windows Explorer, when you Right-Click or select a file, starts examining the file immediately looking at metadata, thumbnails, etc. This is a “feature” of explorer, because explorer expects all of the files to be local, where performance is VERY good. But when it’s actually connected via the internet, the performance isn’t good enough to do all that.
But it WILL work, if you give it time to do its thing. If your internet speeds are slow, it can take a VERY long time.
Copying via Command Line works a lot faster, in many cases, as does using other methods OTHER than Windows Explorer.
Drive mapped as a FAT drive and reporting local drive capacity.
Again, that’s normal. Network drives are neither FAT nor NTFS. They’re “Network.” But Microsoft doesn’t indicate that, it just indicates FAT for WebDAV and NTFS for anything that’s CIFS.
I’m not sure why you’re getting those errors. I’m having no problems wiht mine from work… (Though, I seldom use it because our internet bandwidth usage is monitored and reported…)
Well i dont mind if it is coming up as my C:\ storage and i dont mind that it is Fat instead of NTFS…
I just want to be able to copy from a remote location and watch the movies from a remote location.
Is there a way of accessing the NAS remotely but not going through the WD2go URL, such as ftp or a direct url to your router
such as http:\IP_ADDRESS\Public because when i try this, i actually get prompted with a username and pw box but it will not accept the username and pw that i use with my NAS… This is driving me mad…
Why? All i want to be able to do is access the files remotely… It is a feature of the appliance so why is it so hard for me to do? Using the WD2go interface will always map it as FAT and this is on 20-30 Windows XP & 7 Machines that i have tried… All Pcs have same end results… Drive will map, files can be viewed but they cannot be accessed or copied and the pc will hang and need a forced reboot…HELP
I am at work now, and I just copied a 588 Mbyte movie from my MBL.
The PC sat there “Calculating…” for about 3.5 minutes while it was copying the file to some temporary space, and then about 10 seconds copying it from the temporary space to the destination. I could tell it was actually copying (even though the status screen did not indicate it) because the Windows Network Monitor graph was showing about 40% utilization of a 100 meg connection.
240 seconds total to copy 588 Mbytes – equates to about 2.4 Mbytes / second transfer, or about 20 megabits/sec.
My internet upload speed is 35-40 megabits per second, so all in all, the transfer was reasonably fast. I don’t know if my company’s internet QoS policies would have affected it, but we only have a 300 megabit/second internet shared by 15,000 people…
Just tried the waiting game… I copied a 250MB file and after 30 secs or so, it started to copy… Then an 800MB file done the same… When i try a 2GB file though (using TeraCopy) rather than Windows Copy, it will not copy and the PC freezes…
I see from going through the forum that anyone who is suffering similar issues are struggling to copy, stream and then having their PC freeze.
This is what I think is going on – and it’s a guess. It’ll take a lot of research to prove it.
*some* parts of windows have no idea what *other* parts of the OS are doing.
This is proven by the fact that the Explorer window will go “Not Responding” when even right-clicking a large file before the Pop-up menu appears. But it’s obvious that OTHER parts of Windows are still doing things – copying the file to the WebDAV Cache directory (a hidden, protected path in Windows 7. Not sure how XP does things.)
In your case, what I think may be happening is that the “■■■■■” parts of the OS are timing out – it’s taking too long for the “other” part of the OS to do its thing, like moving the file to the cache directory.
If it takes too long, the OS throws up its hands and gives an error, even though, if it were to wait long enough, it’d work.
Not a bad theory except when copying a file that is over 2GB, you get the error immediately saying cannot read from source file or disk
The thing is, i cannot understand how more people are not giving out about not been able to copy files over 2gb as this seems to be a popular device and one of the key elements of it, is the NAS WD2Go feature…
At least i know know when the PC is hanging, i dont need to force reboot anymore as i know the file is actually copying… I wonder if i have set a setting somewhere on router or my dashboard where i have told the device not to copy a file over 2gb. I don’t think i did though.
