Do we really need "local master" with Windows 7 ?

[Black Ninja]

I read about "local master" CIFS option in freenas shares on internet, this forum and the freenas documentation as well which states if using Windows 7 is not needed.

I still can't understand the actual purpose of it and if it's needed. Can someone explain it ?

 

[Mirfster]

Just me going off memory (old memories at that)... I think you are talking about the "elections" where Windows machines would try to decide who would be the network browser master. These "elections" would occur often and would even switch to different systems. When a Windows machine is part of a domain; then that is not needed (if I recall correctly). Although I haven't looked; it may not be needed any longer with Windows 7 and above and may have been an antiquated feature from older systems.

 

[Black Ninja]

Your memory is very good. That is exactly what I am talking about.:)
The problem is I don't understand what purpose this servers in freenas. I don't have active directory , just Windows 7 machines as "workgroup", do I need this ? Do I need local master , do I need freenas to be local master ?!

What's up with this local master ?!

 

[nightshade00013]

If I remember right the "Local Master" caches the ip's and names of all the local computers in a workgroup and keeps track of which ones are active. It makes lookups slightly faster if you don't check it on the FreeNAS one of the other windows systems in the workgroup will pick it up so it's not needed but since the FreeNAS will likely be on 24/7 365 it's easier for it to handle things rather than to let it bounce around.

 

[Black Ninja]

Thank you guys very much. I am not sure why you both have to dig soo deep in your memory to remember such a valid present feature, but I am glad your memory is still intact and want to use the opportunity to ask another question::)

Is "hostnames lookup" option related to that too. Some in the forum said if you uncheck one you have to uncheck the other too. ? Why freenas needs to look the hostanmes, an who's hostnames is looking up , the clients when try to connect to freenas perhaps ?

 

[Mirfster]

Some in the forum said if you uncheck one you have to uncheck the other too. ?

Can you provide the link so I/we can see what all was being suggested/spoken about?

 

[Black Ninja]

Let me find it and get the link. Here are the setting in my freenas by the way. on the picture

 

[Black Ninja]

Can you provide the link so I/we can see what all was being suggested/spoken about?

Here is the link where the guy who look like a cat was refering to:
https://forums.freenas.org/index.ph...onnectionscreate_connection_session_in.27556/

This is on page 2 secont post from the top:

"If you unchecked "hostname lookups", you should also uncheck "local master browser". Restart CIFS service.

From documentation"

 

[Mirfster]

Mine has both enabled and I have no issues. I would prefer leaving the host name lookups enabled so that I could restrict hosts by names instead of IP addresses. That makes it a little simpler from an administrative perspective (at least for me); since I run DHCP for the other clients.

 

[Black Ninja]

What about if you have another freenas in the network , do you ? Will having "local master" enable on both kind of fight with each other who will take local master position ?

 

[Mirfster]

Don't think so. For me, I have statics assigned on my router which also handles name resolution, etc. YMMV, but I don't think you should have any real issues. Could always WireShark and see what traffic is going on if you're really interested. ;)

 

[Black Ninja]

Honestly , the whole problem is that I got these messages:


Mar 22 12:51:01 FREENASBACKUP smbd[50981]: STATUS=daemon 'smbd' finished starting up and ready to serve connectionname: host name/name mismatch: 192.168.1.30 != (NULL)

Mar 22 12:51:01 FREENASBACKUP smbd[50981]: [2016/03/22 12:51:01.201030, 0] ../source3/lib/util_sock.c:1199(get_remote_hostname)

This messages comes the moment I access CIFS share from windows client and that's the reason why I am investigating hostnames lookups and local master options to find solution myselft. I did ask for this specific issue in the forum but , all I got was "Fix your DNS then" or nothing.

I assume you don't have any messages when you access your CIFS share ?

 

[Mirfster]

Nope, easy test may be to do a "nslookup" from the FreeNas shell (or putty). FreeNas should then check with your Router/DNS and get a response to the computer name. That is what I think everyone is talking about when they are saying you should fix your DNS. Either that or you don't have "Name Server" anything entered/configured in [Network] - [Global Configuration].

Example:

Code:

[root@ASC-FREENAS01] ~# nslookup ALIAS-MIRFLT
Server:         10.20.10.1
Address:        10.20.10.1#53

Name:   ALIAS-MIRFLT.[Redacted].com
Address: 10.20.10.215

 

[Black Ninja]

Nope, easy test may be to do a "nslookup" from the FreeNas shell (or putty). FreeNas should then check with your Router/DNS and get a response to the computer name. That is what I think everyone is talking about when they are saying you should fix your DNS. Either that or you don't have "Name Server" anything entered/configured in [Network] - [Global Configuration].

Example:

Code:

[root@ASC-FREENAS01] ~# nslookup ALIAS-MIRFLT
Server:         10.20.10.1
Address:        10.20.10.1#53

Name:   ALIAS-MIRFLT.[Redacted].com
Address: 10.20.10.215

Is this "ALIAS-MIRFLT" just a machine hostname ?

 

[Black Ninja]

This is what I got when I do the test you suggest:

[root@freenastestr]~# nslookup freenastestr
Server: 192.168.1.1
Address: 192.168.1.1#53

** server can't find freenastestr: NXDOMAIN

 

[Mirfster]

Is this "ALIAS-MIRFLT" just a machine hostname ?

Yes, that is just a machine on my network... A laptop of mine to be precise.

[root@freenastestr]~# nslookup freenastestr
Server: 192.168.1.1
Address: 192.168.1.1#53

** server can't find freenastestr: NXDOMAIN

Looks like you used the actual name of your FreeNas server? That should also provide a response as well. It does show that it tried to use 192.168.1.1 to resolve the hostname; but did not get a response... So with that being said, you need to check your switch/router (whatever 192.168.1.1) is and ensure it is properly resolving hostnames to ip addresses.

 

[Black Ninja]

My router is pfsense box , which is pretty much set by default. I know it uses DNS Resolver. When I tried in freenas to use nslookup on any outside adres like www.google.com it resolves them , but not the local ones ?!

The only local hostname that nslookup command in freenas is able to resolve properly is the pfsense host name, which it resolves properly. Can you tell what needs to be change or add in router then. I thought that DNS resolver will resolve local hosnames ?!

 

[Black Ninja]

Oh my got I have this feeling the I am getting very close to solve this old problem !):)
Celebration will be knocking at my door very soon.

 

[Mirfster]

In PfSense under [Services] - [DNS Resolver]; do you have "Register DHCP leases in the DNS Resolver" Enabled/Checked?

 

[Black Ninja]

In PfSense under [Services] - [DNS Resolver]; do you have "Register DHCP leases in the DNS Resolver" Enabled/Checked?

Is not checked. I can check that , but will it help with the machines that have static IP's setup outside the DHCP range ? Will it register them ?