Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[gunrunnerjohn]

Is there a way to prevent these boxes from assuming the role of the network master browser?  I just ran a little utility to see why my Windows 7 machine suddenly wasn't assuming that role and I found.

LANscanner v1.3 - ScottiesTech.Info

Scanning LAN...

DISKSTATION       192.168.0.144  00-00-00-00-00-00  WORKGROUP
DNS-321           192.168.0.143  00-00-00-00-00-00  WORKGROUP  MASTER
DNS-323           192.168.0.142  00-00-00-00-00-00  WORKGROUP  MASTER
MAIN              192.168.0.151  00-00-00-00-00-00  WORKGROUP

For some reason, these things seem hardwired to assume the master browser role.  I can confuse the issue having two master browsers as well, so I'd like to kill this option off!

[gunrunnerjohn]

Gee, nobody knows how to fix this?

[gunrunnerjohn]

Well, since nobody was able to come up with any idea, I had to do some serious trolling on the web and come up with a solution of how to kill off the capability.  I'm shocked that nobody has noticed their network has multiple master browsers and the issue that can cause.

[Rodent]

I guess its only an issue if you have multiple DNS's

LANscanner v1.3 - ScottiesTech.Info

Scanning LAN...

DNS323                10.0.0.250  00-00-00-00-00-00  WORKGROUP  MASTER
Computer1            10.0.0.94   00-00-00-00-00-00   WORKGROUP
Computer2            10.0.0.69   00-00-00-00-00-00   WORKGROUP
Computer3            10.0.0.70   00-00-00-00-00-00   WORKGROUP

But you are right, there should be an option to turn off master browser on these devices...

R.

[gunrunnerjohn]

I had three NAS units all trying to be the master browser, I think that was why sometimes it took a long time for the networks to be updated.  I turned off the capability on my DNS-321 and DNS-323 and now I just use the Synology DS209 as the master browser.

[Rodent]

How have you turned off the capability on my DNS-321 and DNS-323

[gunrunnerjohn]

It requires you to use ffp_plug and telnet (or SSH) into your box and do some modifications to the smb.conf file, basically inserting the following line in the [Global] section.

local master = no

The trick is doing that and getting it to take effect.


I created a directory under the /ffp/start directory named config.  In that directory, I placed the modified smb.conf file.

In the /ffp/start directory, I placed a file named rconfig.rc containing the following lines.

#!/ffp/bin/sh

/usr/bin/smb stop
config_dir="/ffp/start/config"
cp $config_dir/smb.conf /etc/samba/
/usr/bin/smb start

This stops SAMBA, copies my modified file over, then starts SAMBA again.  Since the file is not placed in the FLASH, it has to get replaced every boot, which is what the above script does.  Of course, you have to stop SAMBA to allow the new configuration to be read.

Result?  No master browser for either of the boxes.

[gunrunnerjohn]

HMM...  For some reason, after a total wipe and reconfiguration of my DNS-321, it refuses to relinquish the function of the master browser.  The same technique still works on the DNS-323, so I'm somewhat at a loss.

I even expanded the fix to include all the browsing options.

[global]
local master = no
domain master = no
preferred master = no


The DNS-321 still thinks it's the master browser after a restart.  Yes, the file is being copied to /etc/samba and is correct.  After verifying the file is currently there, I did the following commands.

smb stop
smb start

That should kill off the master browser capability, but it still presses on!    Any Linux experts here that can tell me what else I can do and still have SAMBA running?