I hope you don’t mean that here should be a machine on ALL THE TIME in order for WD live to work (ie; be the master browser?)
YES I mean exactly that. If you don’t have a machine on, then you can’t possibly be sharing anything! And if you have ONE machine that’s sharing, that machine MUST be a capable master browser. That’s how SMB works. It’s defined in the standard, and the expectation of a functioning master browser within the workgroup is IMPLICIT in any platform or appliance that conforms to the standard.
WD does fail in one regard here: If the WD is the box that is sharing to ANOTHER WD box, and no other PC is on the network, it will not work, since the WD won’t be the master. I’ve gone round with WD on this one, but it’s beside the point, as that’s not the scenario you are describing.
This thing should work straight out of the box,
I have SIX WD live variants. I have three WDTV Lives, one Live+, and two Live Hubs. Every one of them worked “out of the box.” The only time that was NOT the case was when Windows released “Windows Live” into the public late last year. That new suite exposed a Samba bug that affected any device running Samba 3.4.x or earlier. WD had a fix for that a few months later.
Why should the user have to disable security and adjust all kinds of STANDARD security features?
To make it work. That’d be a pretty good reason… If you are diliberately blocking a necessary protocol, you expect WD to work around that block? Sorry, that’s not how firewalls work, or how they SHOULD work. That’s the point of a firewall. If you block Samba, Samba breaks.
I never had to manually modify firewall rules or disable them, since Windows FIrewall automatically adjusts when you turn on SHARING to allow SMB / NBNS / etc. If you’re using a third-party firewall, you’ll have to do it yourself.
Why can I mount shares on my ubuntu box that live on my windows machines and they are persistent?
It depends on how you are mounting those shares. I would bet you’re not using the DISCOVERY service on your Ubuntu box; you’re probably doing something like:
mount -t cifs “\servername\sharename” -o etc.etc.
or putting an equivalent entry into /etc/fstab
Explicit mounts don’t use the discovery service, nor does it require the master browser, since you’re not browsing, you’re targetting the mountpoint to a specific device so that all that is necessary is an NBNS lookup.
The WD depends on the DISOVERY service (and Master Browser) to simply discover that your PC EXISTS in the workgroup.
looking forward to your properly configured machine information.
I’ve posted it here hundreds of times, including in my stickied FAQ, and it’s been verified probably thousands of times by other users.