samba - Apr 2000 - SAMBA Browse Lists Sync DMB and LMB

Hello !

  I have a problem of syncing browse lists between 
DMB and LMB.

  The topology of ours network is as follows:

        Linux Network

 comma(Linux, DMB, WINS)  vol(Linux)     door(Linux, LMB)
 | | |                     |               |         | |
 | | --------------(195.226.226.16/28)------         | |
 | |                                                 | |
 | --(local net 192.168.100.0/24 only Win95 clients) | |
 |                                                   | |
 ----(local net 192.168.1.0/24   only Win95 clients) | |
                                                     | |
     (local net 192.168.2.0/24   only Win95 clients)-- |
                                                       |
     (local net 192.168.3.0/24   only Win95 clients)----

  Comma - Network Server:
1. Samba ver 1.9.18p4 as : WINS, DMB, LMB
2. DNS
3. DHCPD (for all clients Primary and Secondary WINS Servers are Comma)
4. Others Services and Daemons.

  Vol - Linux WorkStation
1. Others Services and Daemons.

  Door - Second Network Server:
1. Samba ver 2.0.6 as : LMB
2. resover -> comma
3. DHCPD
4. Others Services and Daemons.

Problem:

1.  After bootting on a Win95 on one of Comma's local networks
(say it on 192.168.100. with ip .1 and name 'Cad1') it becomes
visible in the Comma's browse list. After some time it becomes
visible in the Door's browse list. And everything goes good.
After a 'gracefull' shut down of Cad1 it is deleted from Comma's
browse list. But from Door's browse list it would never be
deleted, except restart of Samba on Door.

2.  After bootting on a Win95 on one of Door's local networks
(say it on 192.168.2. with ip .1 and name 'Dis1') it becomes
visible in the Door's browse list. After some time it become
visible in the Comma's browse list. And everything goes good.
After a 'gracefull' shut down of Dis1 it is not deleted from
Door's browse list and thus from Comma's too. Browse list's of
both servers (Comma and Door) will contain Dis1 until restart
of Samba on them or may be for a great amount of time (such as
for some hours).

   
  What can You advise in how to make browse lists more valid ?

  I'm already thinking on adding a ping function on to a 
sync_lists() function and delete those computers from list
that are not responding.

  Thank You in advance.

  Sorry, for my not good English.

        Good-Luck.

  
------
Sasha.

I have been working on a similar and related problem (details below).  The cause
of this behaviour is simply the way the SMB protocol was designed - it's
part of
NetBIOS and samba just copies that behaviour.  Here's what happens;

When a new host boots on the LAN, it sends an announcement to the Local Master
Browser (LMB) .  The announcement is repeated, frequently at first, but settles
down to once every 12 minutes.  If the host is then turned off, the LMB waits
for 3 announcement cycles (36 minutes) before removing the host from the browse
list.

When a host becomes an LMB, it sends out an announcement to the domain master
browser every minute for 5 minutes and then repeats the announcement every 15
minutes.  If those announcements stop, a LMB or DMB will wait for 3 cycles (45
minutes) before removing the host from the browse list.  

You can see that in some cases, (when the browse lists have to be
synchronised between LMB/DMB on different subnets) it could take as long as
(almost) 1.5 hours between the time that a host is removed and the time that
all the browse lists are updated.   

The consequence to this behaviour is that browsing the host will fail
with a message from Windows saying that the computer is not available.  

If you would like to see some other "strange" behaviour, go to one of
the
windows PCs, edit network properties and change the workgroup name to something
different.  Reboot and wait for the change to propagate through the browse
lists.  Note that the only correct browse list is on the PC that you changed. 
Every other browse list will be wrong.  Now go back and change the workgroup
name back to the correct name.  Let me know if you figure out how long it takes
for that change to disappear from the browse lists.

For some details, look at nmbd_winsserver.c lines 727-744 (2.0.6).  Does anyone
know why samba does NOT register the IP address of the LMB when recording the
workgroup in the wins database?  It's causing problems for our network.


Alex Vandenham
Avantel Systems

==========================On April 21, You wrote;

Hello !

  I have a problem of syncing browse lists between 
DMB and LMB.

  The topology of ours network is as follows: