I am trying to get rid of these messages so I can have a clean console screen without any errors. I've been runing my freenas 9.3 (Dec 2014) edition very successfully, since Dec 2014. I did look many places to find reasonable explanation.If I am not mistaken there is a link of a small Lan-Scan program which is tell you who the local master is. I couldn't open the link you are referring to, but I believe it looks familiar. I do that because it really is up 24x7 and there's no reason to not let it be the master all of the time. My main FreeNAS system is set to be the master browser. It just depends on how you want to run your network. You can have either one enabled while the other is disabled. The hostname lookups and the master browser settings are not exclusive or inclusive, and they do unrelated things. I disable it if its failing because it adds no value if your network doesn't support it.
#Flame bonjour browser full#
But for home users that don't have all the required prerequisites, it won't work and you'll just end up with a log full of failed hostname lookups.
It's a security feature, and for large enterprises it can be useful. The hostname lookup feature simply tells FreeNAS to resolve the IP and hostname given by the client (often Windows) and verify that the info is correct per DNS. It doesn't guarantee it will win the election, but its very likely to. Totally necessary for workgroups to have a "master", and by checking the box the FreeNAS system tries to make itself the highest priority for "winning" the election for the master browser. So the master browser option is kind-of explained here:
0 kommentar(er)
