From a84f1e7535b64dcfb1f274097cf947d0ad6fd1ec Mon Sep 17 00:00:00 2001 From: Gerald Carter Date: Thu, 16 Jan 2003 02:21:51 +0000 Subject: regenerate docs (This used to be commit 2215dc37e26bec17eb971e7b54818622a9bb5b97) --- docs/htmldocs/browsing-quick.html | 43 ++++++++++++++------------------------- 1 file changed, 15 insertions(+), 28 deletions(-) (limited to 'docs/htmldocs/browsing-quick.html') diff --git a/docs/htmldocs/browsing-quick.html b/docs/htmldocs/browsing-quick.html index cc703d217f..8c597e001f 100644 --- a/docs/htmldocs/browsing-quick.html +++ b/docs/htmldocs/browsing-quick.html @@ -5,7 +5,8 @@ >Quick Cross Subnet Browsing / Cross Workgroup Browsing guidePrev

Chapter 4. Quick Cross Subnet Browsing / Cross Workgroup Browsing guide

Chapter 3. Quick Cross Subnet Browsing / Cross Workgroup Browsing guide

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" >

4.1. Discussion

3.1. Discussion

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" >

4.2. Use of the "Remote Announce" parameter

3.2. Use of the "Remote Announce" parameter

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.

4.3. Use of the "Remote Browse Sync" parameter

3.3. Use of the "Remote Browse Sync" 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" >

4.4. Use of WINS

3.4. Use of WINS

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" >

4.5. Do NOT use more than one (1) protocol on MS Windows machines

3.5. Do NOT use more than one (1) protocol on MS Windows machines

A very common cause of browsing problems results from installing more than one protocol on an MS Windows machine.

4.6. Name Resolution Order

3.6. Name Resolution Order

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