I've seen this happen several times, and, short of rebooting
the NT PDC, I can't seem to fix it.
Background: We have two numbered networks in the building.
We have an NT domain that has members on both numbered networks.
To keep browse lists straight, I've designated Samba as the
browse master on one of the networks. It's declared to be
in the same workgroup as the NT primary domain controller.
For about a week after the PDC is rebooted, everything is fine.
Clients on both networks can see all the machines in the domain,
indicating that Samba and the PDC are synchronizing browse
lists. Eventually, in the nmbd log, errors like this one
begin:
[1999/03/30 11:39:57, 0]
nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(362)
find_domain_master_name_query_fail:
Unable to find the Domain Master Browser name TIOGA<1b> for the
workgroup TIOGA.
Unable to sync browse lists in this workgroup.
If I use nmblookup to find the IP address associated with
"tioga#1b", the PDC is found:
>nmblookup tioga#1b
Sending queries to 192.52.153.255
192.52.153.225 tioga<1b>
So how is it that nmblookup can find "tioga#1b" and nmbd can't???
I'm running Samba 2.0.3 on a BSDi 3.0 box. The machine has IP
addresses on both networks. Here are some tidbits from its
smb.conf:
interfaces = 192.52.153.11/24 167.116.93.5/24
local master = yes
preferred master = yes
domain master = no
os level = 17
announce as = NT Server
wins support = yes
wins proxy = yes
netbios aliases = LAX
workgroup = TIOGA
name resolve order = lmhosts wins host bcast
This has happened too often for me to ignore it. The fact
that rebooting the PDC "fixes" the problem for a week just
means I don't understand what the symptom means.
Can anyone shed some light on this one?
Thanks,
Jim
--
Jim Watt jimw@PE-Informatics.COM
PE Corporation Voice (desk): +1 408 577 2228
PE Informatics Division Fax: +1 408 894 9307
3833 North First Street Voice (main): +1 408 577 2200
San Jose CA 95134-1701
This one isn't by any means resolved. But I know a little
more about name resolution than I did Monday.
A quick synopsis: I have an NT PDC acting as the domain
master browser on one network, and a Samba machine acting
as the browse master for the same domain on the other
network. Both networks are local, and the router passes
everything between the networks.
About a week after the NT PDC has been rebooted,
Samba (nmbd) can no longer contact the domain master browser to
synchronize browse lists:
[1999/03/31 17:21:33, 0]
nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(362)
find_domain_master_name_query_fail:
Unable to find the Domain Master Browser name TIOGA<1b> for
the workgroup TIOGA.
Unable to sync browse lists in this workgroup.
I've been able to reproduce nmbd's behavior using nmblookup
by sending a UNICAST request to the WINS server to resolve
the the "#1b" name for the PDC:
nmblookup -d 10 -U 192.52.153.11 tioga#1b
"192.52.153.11" is the address of the WINS server. The name
was not resolved. The name _is_ resolved if broadcast
resolution is used:
nmblookup -d 10 tioga#1b
So apparently the record has expired from the WINS server,
and it's not honoring the name resolution list it's been
given (from smb.conf):
name resolve order = lmhosts wins host bcast
Rebooting the PDC refreshes that record. But why doesn't
the Samba WINS server resort to broadcast resolution as it's
been told to? I've even tried putting the <domain>#1b name
in Samba's lmhosts file, and that doesn't work either!
(See Message-ID: <3672460627.922795461@wattjg.PE-Nelson.COM> dated
Date: Tue, 30 Mar 1999 12:04:21 -0800) for my original posting to
the samba mailing list.)
I think I'll Cc: samba-bugs on this one...
Jim
--
Jim Watt jimw@PE-Informatics.COM
PE Corporation Voice (desk): +1 408 577 2228
PE Informatics Division Fax: +1 408 894 9307
3833 North First Street Voice (main): +1 408 577 2200
San Jose CA 95134-1701
Synopsis so far... We have two IP networks in the building. One of our NT PDCs is on one network, and is the browse master for its domain. Our Samba system is declared in the same "workgroup" as the NT PDC, and is also our WINS server. It's on both networks. After the PDC has been rebooted, cross-subnet browsing works fine. Eventually, the Samba machine cannot locate the domain master browser, so browse list synchronization stops happening. I've tried a number of configuration changes to Samba, mainly relating to election parameters and declaration of the missing "1b" entry for the domain in Samba's lmhosts file. I then discovered that broadcast lookups of the <domain>#1b entry worked, but unicast lookups didn't, even though the <domain>#1b entry was in Samba's lmhosts file. I know that rebooting the PDC will make the browse lists synchronize...for a while. I was getting desperate for some other way to at least convince myself that it was the fact that there was no "1b" entry in the WINS file for the PDC's domain. So I decided to put one in last night. There were nine "1b" entries in wins.dat. I stopped both smbd and nmbd, made a new "1b" entry for the missing domain, and restarted everything. That worked! So the question now is why is that one domain's "1b" record expiring? It looks like all the others get renewed. None of them has a TTL of zero, which, according to the code, is what a non-expiring wins entry's time_t field looks like. Reminder - it's the PDC for the domain that Samba is declared to be part of. I didn't find any special code about the 1b entry anywhere in the relevant source files for nmbd. So my surmise is that the PDC itself isn't sending update records, although the other nine are. So why is that? :-) Jim -- Jim Watt jimw@PE-Informatics.COM PE Corporation Voice (desk): +1 408 577 2228 PE Informatics Division Fax: +1 408 894 9307 3833 North First Street Voice (main): +1 408 577 2200 San Jose CA 95134-1701
Jim Watt <jimw@pe-nelson.com> wrote:>A quick synopsis: I have an NT PDC acting as the domain >master browser on one network, and a Samba machine acting >as the browse master for the same domain on the other >network. Both networks are local, and the router passes >everything between the networks. > >About a week after the NT PDC has been rebooted, >Samba (nmbd) can no longer contact the domain master browser to >synchronize browse lists:We had exactly the same problem - it turned out that someone had been fiddling with the PDC and had changed the WINS entry to point to itself (and it isn't a WINS server) instead of the Samba WINS server. When the PDC is booted, it broadcasts that it is the PDC, and the samba box picks this up. However, when it becomes time to refresh it's entry with the WINS server, it was pointing to the wrong box. It's entry then expires from the WINS server, and everything which isn't on the same subnet starts having all kinds of trouble. It took us a long time to track this down, as we knew that the networking info had been set up correctly, and none of us had changed it. The perils of a PDC in a location with lots of developers who fiddle!! Cheers, Joel Joel Smith First Software Queens Ct, Wilmslow Rd +44 (0)1625 587111 +44 (0)468 803758 (mobile) Alderley Edge SK9 7RR Fax +44 (0)870 1617192 (direct)