New error after 9.2.1.7 upgrade from 9.2.1.6 (standard_fail_register)

[shanky22]

192.168.0.135 is my FREENAS box IP. It started giving this error after upgrading to 9.2.1.7 x64.

Aug 15 01:00:46 FREENAS nmbd[2991]: STATUS=daemon 'nmbd' finished starting up and ready to serve connectionsbecome_local_master_fail2: failed to register name WORKGROUP<1d> on subnet 192.168.0.135. Failed to become a local master browser.
Aug 15 01:00:46 FREENAS nmbd[2991]: [2014/08/15 01:00:46.406211, 0] ../source3/nmbd/nmbd_namelistdb.c:320(standard_fail_register)
Aug 15 01:00:46 FREENAS nmbd[2991]: standard_fail_register: Failed to register/refresh name WORKGROUP<1d> on subnet 192.168.0.135

 

[dlavigne]

Did you ever figure this out?

 

[Jailer]

I'm getting the same error on my new install of 9.3. I can connect to my shares fine but this error is being generated in the console.

 

[dlavigne]

Is the "local master" box checked in Services -> CIFS? If so, try unchecking it.

 

[Jailer]

It was so I stopped cifs and made the change and restarted and it still generates this error. Since I'm not having trouble connecting to my shares should I just ignore it?

 

[dlavigne]

I guess... Weird it still gives the error.

 

[Jailer]

Ok I got this one figured out, at least for a windows machine. It's not a freenas problem it's a problem with another computer on the network winning the election of master browser. The fix is pretty simple.

To get freenas set as master browser you need to figure out which computer is set to master browser and stop the computer browser service on that computer in the services menu. Once you have the browser service stopped go to the freenas web GUI and stop the CIFS service and restart it. Once it starts back up it will register itself in the workgroup and set itself to master browser.

To prevent it from happening again you need to add an entry to the registry on the fussy windows machine. Navigate to "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Browser\Parameters" and add a new string labled "IsDomainMaster" and give it a value of "No". Reboot and it will prevent that machine from setting itself as master browser without having to disable the computer browser service which in turn allows it to remain visible in the network locations on other computers in your network.

I kinda suck at explaining things, especially in written form, so if that doesn't make sense feel free to let me know and I'll try to explain it better.

 

[Jailer]

Ok one more update. Seems the registry fix didn't work and my desktop is still winning the election for master browser so I've had to disable the computer browser service on my desktop to prevent it from happening. That seems to finally have solved the problem.