|Main Archive Page > Month Archives > samba-users archives|
I am trying to join a SAMBA client to a SAMBA domain. The
SAMBA PDC is on a different network from the SAMBA client.
I have a SAMBA server on the client network acting as a
local browse master. The "net join" command fails because
the PDC is multi-homed, it gives out a list of addresses,
the address at the head of the list can't be reached by
the client and the command does not iterate through the
list of PDCs. Is there a way to specify the order of IP
addresses handed out by the SAMBA server when it is asked
for the PDC address(es)?
The PDC is multi-homed with these addresses:
10.142.36.94 (a /25 net)
10.142.36.125 (a /27 net)
10.142.36.254 (a /25 net)
The client can connect to the PDC's 10.142.36.94 address (ping,
ssh, etc.) via an IPsec tunnel.
I can successfully run many commands against the PDC:
nmblookup -B server __SAMBA__
nmblookup -M -- -
smbclient -L server -U%
and so on.
However, the "net lookup dc" command gives me a list of PDC
addresses in this order:
The file wins.dat has these entries for the PDC:
"SERVER#00" 1275257441 10.142.36.94 10.142.36.254 10.142.36.125 66R
"SERVER#03" 1275257441 10.142.36.94 10.142.36.254 10.142.36.125 66R
"SERVER#20" 1275257441 10.142.36.94 10.142.36.254 10.142.36.125 66R
A "net join" command fails. It tries to use this address for
There is no route to that address. The "net join" command does
not iterate through the list of PDC addresses, though. It just
Is there a way to specify the order in which the SAMBA PDC hands
out its addresses (when multi-homed) such that the IP address at
the top of the list is the one on which the request arrived? That
is, if a request for the PDC list arrives on the 10.142.36.94
interface can the response put the address 10.142.36.94 at the
head of the list of PDC addresses?
-- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba