Bug 2759 - Multi-Homed PDC Cause Problems
Summary: Multi-Homed PDC Cause Problems
Alias: None
Product: Samba 3.0
Classification: Unclassified
Component: nmbd (show other bugs)
Version: 3.0.14a
Hardware: All Linux
: P3 normal
Target Milestone: none
Assignee: Samba Bugzilla Account
QA Contact: Samba QA Contact
Depends on:
Reported: 2005-05-31 16:25 UTC by M. D. Parker (dead mail address)
Modified: 2021-01-04 15:29 UTC (History)
0 users

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description M. D. Parker (dead mail address) 2005-05-31 16:25:37 UTC
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.
Comment 1 Björn Jacke 2021-01-04 15:29:26 UTC
"nbt client socket address" should do what you want. But these days, you will be using AD and DNS discovery anyway I assume