System has 3 ethernet boards: eth0 (on private/backend net 192.168.x.x)
eth1 (on public net 141.x.x.x)
eth2 (on public net 141.x.x.x)
There is a common corporate WINS database on the public net.
The smb.conf file is configured to use only eth0 and eth1 and uses the following
directives to ensure this:
bind interfaces only=yes
interfaces=eth0 eth1 lo
The WINS server records BOTH the public and private net IP numbers. And for the
most part works ok for clients. There is an occasional client getting the
private IP number (from WINS?) and this seems to get fixed by restarting Samba.
1) Is this a problem? can it be fixed?
Ok....now if I change the order of the interfaces line to:
interfaces=eth1 eth0 lo
The log.nmbd cannot find the master domain master browser at all...but seems to
be able to become the local master browser.
2) This is a problem....changing the order of the interfaces line seems to
change the samba/nmdb behavior. I don't think that this should be happening.
"nbt client socket address" should do what you want. But these days, you will be using AD and DNS discovery anyway I assume