What is Workgroup and how does FreeNAS handles it?

[katit]

I'm admitting I know very little about windows domain server and don't really understand how workgroup in terms of home user network works..

I have my old FreeNAS box and it belongs to SAMBA's (CIFS) "WORKGROUP" by default. It's address on .99

Now I'm burn-in testing and building new FreeNAS box (IP of .10) and see following messages in log:

Code:

Aug 22 17:10:57 HOME-NAS nmbd[2483]:   STATUS=daemon 'nmbd' finished starting up and ready to serve connectionsquery_name_response: Multiple (2) responses received for a query on subnet 192.168.99.10 for name WORKGROUP<1d>.
Aug 22 17:10:57 HOME-NAS nmbd[2483]:   This response was from IP 192.168.99.99, reporting an IP address of 192.168.99.99.
Aug 23 04:02:06 HOME-NAS nmbd[2483]: [2015/08/23 04:02:06.321073,  0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Aug 23 04:02:06 HOME-NAS nmbd[2483]:   query_name_response: Multiple (2) responses received for a query on subnet 192.168.99.10 for name WORKGROUP<1d>.
Aug 23 04:02:06 HOME-NAS nmbd[2483]:   This response was from IP 192.168.99.99, reporting an IP address of 192.168.99.99.
Aug 23 04:12:07 HOME-NAS nmbd[2483]: [2015/08/23 04:12:07.077255,  0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Aug 23 04:12:07 HOME-NAS nmbd[2483]:   query_name_response: Multiple (2) responses received for a query on subnet 192.168.99.10 for name WORKGROUP<1d>.
Aug 23 04:12:07 HOME-NAS nmbd[2483]:   This response was from IP 192.168.99.99, reporting an IP address of 192.168.99.99.

I see there is some kind of conflict but what do I do to fix it? In description it says "Workgroup server will appear in when queried..." which to me means it's OK to have 2 servers in same workgroup?

 

[SweetAndLow]

It's fine to have two servers in the same workgroup. I think this is just cifs complaing because there are two masters on the network. In the cifs settings does it make a difference if you uncheck the box called 'local master'?

 

[katit]

Tried to uncheck "Local Master" but still. In todays new update there was something "fixed" about Local Master. Maybe it will help. I checked it back, saved and unchecked again to make sure setting "resets" in SMB. Will monitor but looks like it is not affecting this warning I get

 

[Jailer]

Make sure you stop and then restart the CIFS service whenever you make a change for it to take effect.

 

[Darren Myers]

Make sure you stop and then restart the CIFS service whenever you make a change for it to take effect.

i've done this twice...where i forget to do that lol