From f0e282ebf3e459c559bfc08f3e21fdebb2515621 Mon Sep 17 00:00:00 2001
From: Gerald Carter This document should be read in conjunction with Browsing and may
be taken as the fast track guide to implementing browsing across subnets
@@ -86,9 +85,7 @@ CLASS="SECT1"
> Firstly, all MS Windows networking is based on SMB (Server Message
Block) based messaging. SMB messaging is implemented using NetBIOS. Samba
@@ -132,9 +129,7 @@ CLASS="SECT1"
> The "remote announce" parameter of smb.conf can be used to forcibly ensure
that all the NetBIOS names on a network get announced to a remote network.
@@ -183,16 +178,14 @@ name resolution problems and should be avoided.Chapter 4. Quick Cross Subnet Browsing / Cross Workgroup Browsing guide
Chapter 3. Quick Cross Subnet Browsing / Cross Workgroup Browsing guide4.1. Discussion
3.1. Discussion4.2. Use of the "Remote Announce" parameter
3.2. Use of the "Remote Announce" parameter
The "remote browse sync" parameter of smb.conf is used to announce to another LMB that it must synchronise it's NetBIOS name list with our @@ -212,9 +205,7 @@ CLASS="SECT1" >
Use of WINS (either Samba WINS _or_ MS Windows NT Server WINS) is highly recommended. Every NetBIOS machine registers it's name together with a @@ -274,9 +265,7 @@ CLASS="SECT1" >
A very common cause of browsing problems results from installing more than one protocol on an MS Windows machine.
Resolution of NetBIOS names to IP addresses can take place using a number of methods. The only ones that can provide NetBIOS name_type information @@ -401,7 +388,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" >PrevOplocksImproved browsing in samba