Sync browse list between multiple workgroups?

[Andre Albsmeier]

> 
> (Samba version 1.9.18p4)
> 
> I want to set up my environment thusly:
> 
> - 2 workgroups, each composed of multiple subnets.
> - Each workgroup has a DMB and a WINS server (Samba only - no NT)
> - The two workgroups should collate browse lists so that clients on
> either workgroup can browse and connect to hosts on the opposite workgroup.
> 
> I've read the documentation in BROWSING.txt and it does not appear to
> work in my test environment.  This is how I set it up:
> 
> - Subnet A has a Samba server and a WIN95 client
> - Subnet B has a Samba server and a WIN95 client
> - Both Samba servers are in different workgroups and each are configured
> as a WINS server and a DMB.
> - Both clients are configured to use the local Samba server as their WINS
> server.
> 
> The Samba servers have similar smb.conf files:
> 
>         domain logons = yes
>         security = user
>         password level = 16
>         wins support = yes
>         os level = 255
>         domain master = yes
>         local master = yes
>         preferred master = yes
>         workgroup = Dude
>         remote browse sync = <IP of the other Samba server>
> 
> 
> Now, the log files say that Samba is swapping browse lists with the
> other server, but it's just not happening.  From the nmbd log file:
> 
> sync_with_lmb: Initiating sync with local master browser ORBIT<0x20> at IP 142.5
> 5.200.99 for workgroup DUDE
> 05/06/1998 11:12:11: sync_browse_lists: Sync browse lists with server ORBIT<20> 
> at IP 142.55.200.99 for workgroup DUDE
> 
> I've also tried using "remote announce" and it still doesn't work.
> 
> However, on each client, the Network Neighborhood sees the two differnet
> workgroups.  When I try to view what's in the opposite workgroup, I
> get an error saying that the network name cannot be found.

Yes, that is the same behaviour as I observed here. I can see the
other Workgroup in the Network Neighborhood but it can't be openend;
the local Workgroup works okay.

Please, if someone could explain what we are doing wrong, or if you
get some hints concerning this, please drop me a note.

I have seen this kind of problem several times on the mailing-lists,
so it might be worth adding it to BROWSING.TXT if it is solvable.

Thanks,

	-Andre