On 04/12/2011 01:58 PM, John Andersen wrote:
The only thing that has changed on the network is one computer is currently powered off. No other changes. You might want to figure out which computer is the browse master on your network. Sometimes SAMBA (nmdb portion) dies or becomes confused. This is especially true for
On 4/12/2011 11:44 AM, Jim Flanagan wrote: those machines running on wifi, or switching from wifi to wired connections. Then its hard to find shares. Sometimes a horribly out of date windows machine becomes browse master and you end up having to reboot lots of computers till you find out which one it was.
I always find pick a linux machine that is going to be on all the time (my server) and which will never go into power saving mode. In that machine I set OS LEVEL = 65 in /etc/samba/smb.conf. This makes it win all browser elections. From then on its very reliable.
I've ofter wondered about that. The way a certain machine decides to be browser master seems pretty nebulous. Great tip, thanks. Do I need to find out which one is currently browser master, or just set my linux server, and the old current master which ever one that is will relinquish? Thanks for the advice on AppArmour by the way. I've not felt the need to run that before, small home network. But I do beleive in having additional layers of security where possible. After I get things stabilized here I'll turn it back on and give it a try. Best, Jim F -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org