Multihome WINS Registration
jmd at aoe.vt.edu
Tue Jul 25 00:59:21 GMT 2000
Thanks for your help, Peter.
Let's see, three things to follow up, then my new problem(or the newest
iteration of my existing problem.)
I probably should have the password server like you mentioned, but I
don't think it matters right now, but thanks for pointing it out.
I did explicitly mention the interfaces like you commented, and
discovered the order you list them in does matter somewhat - it is the
order samba will do a broadcast lookup.
And I do plan on migrating to DHCP, but that's after I migrate everyone
from the old NFS/SMB server to this new one. That'll be next.
It looks like samba is behaving correctly, the problem in this case is how
Windows NT handles multihoming(which is not too well.) So, let me get into
specifics on how I have Pluto set up. I have only TCP/IP set up, and this
is how I have it set up(these are the real numbers, I've given up making
the fictitous ones up)
Interface 1: Interface 2:
IP Address: 220.127.116.11 192.168.1.5
Netmask: 255.255.252.0 255.255.255.0
Default GW: 18.104.22.168 (blank)
WINS Addr: 22.214.171.124 126.96.36.199
I have 'Enable IP Forwarding' turned off under Routing.
The WINS doubling may be an issue, but that way the WINS client registers
both addresses under WINS.
Doing a 'netstat -r' to view the NT Routing Table looks fine. I have the
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 188.8.131.52 184.108.40.206 1
220.127.116.11 255.255.252.0 18.104.22.168 22.214.171.124 1
126.96.36.199 255.255.255.255 127.0.0.1 127.0.0.1 1
188.8.131.52 255.255.255.255 184.108.40.206 220.127.116.11 1
192.168.1.0 255.255.255.0 192.168.1.5 192.168.1.5 1
192.168.1.5 255.255.255.255 127.0.0.1 127.0.0.1 1
192.168.1.255 255.255.255.255 192.168.1.5 192.168.1.5 1
255.255.255.255 255.255.255.255 192.168.1.5 192.168.1.5 1
So, I open a connection to the Samba server, which is also on both networks
at 18.104.22.168 and 192.168.1.2. Doing something simple like \\hermes\test
(which is just a temporary I shared I made for testing.)
netstat -n on WinNT shows two entries, both odd:
TCP 22.214.171.124:1147 192.168.1.2:139 ESTABLISHED
TCP 192.168.1.5:1148 192.168.1.2:139 TIME_WAIT
And the Samba server shows only 192.168.1.2:139->126.96.36.199:1147(It
doesn't show the TIME_WAIT connection.)
Odd because the first one is going out on the wrong address! I don't even
know how that works. And the second one looks right, but it is closed
immediately. I know other TCP/IP stuff routes fine, like ssh.
I've tried everything I can think of. In the \winnt\system32\drivers\etc\
lmhost file on NT, I have:
192.168.1.2 hermes #pre
The resolve order on the Samba server is 'lmhosts host wins bcast', though
I've tried 'wins bcast' as well.
Anyone have a clue what's going on?
I'm about to give up and try to set up a gateway, but that's a headache
given the current network environment.
Thanks alot, and sorry for the long message!
* Josh Durham | AOE at Virginia Tech | (540) 231-9061 jdurham at vt.edu *
On Mon, 24 Jul 2000, Peter Samuelson wrote:
> [Josh Durham <jmd at aoe.vt.edu>]
> > workgroup = AOE
> > security = DOMAIN
> > password server = PDCSERVER
> > local master = No
> > domain master = No
> > browse list = Yes
> > wins server = 188.8.131.52
> OK.... Except, don't you want `password server = pluto,pdcserver'?
> > 192.168.1.1 HERMES(00h)
> > 192.168.1.1 HERMES(03h)
> > 192.168.1.1 HERMES(20h)
> > I would like it to register 184.108.40.206 with the PDC, since
> > everyone can get to it with that address.
> It may help to specify `interfaces = 220.127.116.11,192.168.1.1'
> > Also, what is the best way to get the SMB traffic to use Subnet B if
> > it can? (IE, between Pluto and Hermes, for example.) I tried using
> > LMHOSTS on NT and UNIX, but to no avail.
> What is your `name resolve order' parameter? Make sure it lists
> LMHOSTS before WINS. (To look up the defaults on parameters you
> haven't specified, `testparm -s | grep' is your friend.)
> > I'd like to keep the WINS server on the NT Server, since that address
> > is statically entered on all the workstations.
> Migrate to DHCP! I say this only partly in jest. DHCP is pretty much
> essential for long-term management of a network of a decent size.
> Changing things like WINS servers becomes very easy, then.
More information about the samba