So what are we supposed to do, since we can’t roll back to any previous version - go out and buy another one from a shop that still has the old firmware on it??
Joshash, if it’s not too late, I offer the following tips:
Make sure your WORKGROUP names are the same on all your devices. Older versions of Live/Live+ didn’t have a dependency on workgroup name. Not sure if this new version does, since I’ve moved on to newer boxes.
Also, make sure your PC that is sharing the files can see the WDTV in the workgroup browser:
For that, see if this tutorial for troubleshooting helps:
Did anyone find a fix for this? When I click on Network Shares it doesnt do anything. It is like i am not even pressing the button on the remote. This worked fine before the update. I have tried reseting to factory and also unsharing my drive and sharing it again. Still when i click on network shares it does nothing.
Sometimes, when this happens to me, it helps to reset the network (even though the WD reports that the network is connected).
Go into Network Settings and select to setup the network; just choose Automatic. After the WD box reports that it has successfully connected to the network, the Windows shares then show up in the Network Shares list.
The next time that I shut off the WD box and turn it on again, the same thing happens (the Windows shares do not show up).
I found a fix! I am not sure which of these steps fixed the problem, but this is the process I followed.
[1] Disabled homegroups on Windows 7
[2] Enabled the Guest account in Windows 7
[3] Created a login especially for the wdtv
[4] On the password page in the WDTV for the computer, i simply entered the username and password WITHOUT the machine prefix.
Previously, I needed I7PC\Josh and the password (ie prefixed with the machine name).
I dropped the I7PC prefix.
I can now play from network shares!
If your machine is on a domain, and you need the domain prefix for authentication, I believe this may cause you a problem.
It works, for now.
I have rolled forward to the latest update, and it is still working.
I’d like to add a comment to this.
During my research to solve this problem, I was shocked with the amount of issues firmware updates have caused on this device. I may still need to roll back if I encounter those. My next media player will not be a WD.
Thanks to everyone who posted their experiences on my issue.
Since the last update, when i try to access my Synology NAS Server, i get the message “The network shares cannot be accessed”. To fix this problem i tried to do the following things with no luck:
Reset to factory default
Check the workgroup name
Change the ip adress
Clear login info for network shares
Check right access on my NAS (even if i knew everything is fine as i accessed them just before firmware upgrade)
Synology server reboot
Any idea on how to recover access to my NAS shares ?
As i use 99% of time the WD to access network shares, it became useless.
Note: i own the WD TV live for several years, performed every upgrades and this is the first time i’m encountering such a thing.
Thanks
EDIT: as a last test, i set “Auto logon to shares” to “OFF” and it did the trick. i can now access the shares.
Very strange behaviour as i had cleared login information previously
I leave my post as it can be useful to someone… maybe
To whoever said “so we can say it did not break my WDTV” :-
** Yes, it did BREAK my WDTV. **
Then, I spent four hours repairing it.
This community is so full of people desperately trying to get basic functionality working after these updates that I am amazed there are those who would leap to its defence.
**bleep**, there are those desperate to get something as basic as network shares working on the OUT OF THE BOX DEVICE.
And we haven’t even started talking about the other issues these forums are full of.
Note that once auto logon has been set to OFF, i’ve been able to enter credentials to connect to my shares.
Once this previous step done, i’ve been able to set back auto logon to ON and access my shares again.
i wouldn’t say this firmware broke my wdtv (as i’ve been able to fix it) but there’s definitly an issue with upgrading process as, as you say, it should “work” out of the box.
Now, this is the first time i encountered such an issue in several years and multiple updates, this thing can happen even if it’s highly annoying when you have to deal with it.