From ff78c3bf5c3a73cf90f6517d9b2d6b8c12d22d68 Mon Sep 17 00:00:00 2001 From: Jelmer Vernooij Date: Tue, 18 Feb 2003 22:14:04 +0000 Subject: Regenerate (This used to be commit 1ab5a3b17feb677425bb1071357c3dbabcc46c7e) --- docs/htmldocs/integrate-ms-networks.html | 105 +++++++++++++++++++++---------- 1 file changed, 73 insertions(+), 32 deletions(-) (limited to 'docs/htmldocs/integrate-ms-networks.html') diff --git a/docs/htmldocs/integrate-ms-networks.html b/docs/htmldocs/integrate-ms-networks.html index ad6aa9e225..8299a456bb 100644 --- a/docs/htmldocs/integrate-ms-networks.html +++ b/docs/htmldocs/integrate-ms-networks.html @@ -5,8 +5,7 @@ >Integrating MS Windows networks with Samba

Chapter 10. Integrating MS Windows networks with Samba

Chapter 9. Integrating MS Windows networks with Samba

10.1. Agenda

9.1. Agenda

To identify the key functional mechanisms of MS Windows networking to enable the deployment of Samba as a means of extending and/or @@ -144,7 +147,9 @@ CLASS="SECT1" >

10.2. Name Resolution in a pure Unix/Linux world

9.2. Name Resolution in a pure Unix/Linux world

The key configuration files covered in this section are:

10.2.1. 9.2.1. /etc/hosts

10.2.2. 9.2.2. /etc/resolv.conf

10.2.3. 9.2.3. /etc/host.conf

10.2.4. 9.2.4. /etc/nsswitch.conf

10.3. Name resolution as used within MS Windows networking

9.3. Name resolution as used within MS Windows networking

MS Windows networking is predicated about the name each machine is given. This name is known variously (and inconsistently) as @@ -413,16 +428,16 @@ the client/server.

	Unique NetBIOS Names:
-		MACHINENAME<00>	= Server Service is running on MACHINENAME
-		MACHINENAME<03> = Generic Machine Name (NetBIOS name)
-		MACHINENAME<20> = LanMan Server service is running on MACHINENAME
-		WORKGROUP<1b> = Domain Master Browser
+		MACHINENAME<00>	= Server Service is running on MACHINENAME
+		MACHINENAME<03> = Generic Machine Name (NetBIOS name)
+		MACHINENAME<20> = LanMan Server service is running on MACHINENAME
+		WORKGROUP<1b> = Domain Master Browser
 
 	Group Names:
-		WORKGROUP<03> = Generic Name registered by all members of WORKGROUP
-		WORKGROUP<1c> = Domain Controllers / Netlogon Servers
-		WORKGROUP<1d> = Local Master Browsers
-		WORKGROUP<1e> = Internet Name Resolvers

It should be noted that all NetBIOS machines register their own @@ -441,7 +456,7 @@ be needed. An example of this is what happens when an MS Windows client wants to locate a domain logon server. It find this service and the IP address of a server that provides it by performing a lookup (via a NetBIOS broadcast) for enumeration of all machines that have -registered the name type *<1c>. A logon request is then sent to each +registered the name type *<1c>. A logon request is then sent to each IP address that is returned in the enumerated list of IP addresses. Which ever machine first replies then ends up providing the logon services.

10.3.1. The NetBIOS Name Cache

9.3.1. The NetBIOS Name Cache

All MS Windows machines employ an in memory buffer in which is stored the NetBIOS names and IP addresses for all external @@ -501,7 +518,9 @@ CLASS="SECT2" >

10.3.2. The LMHOSTS file

9.3.2. The LMHOSTS file

This file is usually located in MS Windows NT 4.0 or 2000 in

10.3.3. HOSTS file

9.3.3. HOSTS file

This file is usually located in MS Windows NT 4.0 or 2000 in

10.3.4. DNS Lookup

9.3.4. DNS Lookup

This capability is configured in the TCP/IP setup area in the network configuration facility. If enabled an elaborate name resolution sequence @@ -640,7 +663,9 @@ CLASS="SECT2" >

10.3.5. WINS Lookup

9.3.5. WINS Lookup

A WINS (Windows Internet Name Server) service is the equivaent of the rfc1001/1002 specified NBNS (NetBIOS Name Server). A WINS server stores @@ -681,7 +706,9 @@ CLASS="SECT1" >

10.4. How browsing functions and how to deploy stable and +NAME="AEN1643" +>9.4. How browsing functions and how to deploy stable and dependable browsing using Samba

As stated above, MS Windows machines register their NetBIOS names @@ -746,7 +773,9 @@ CLASS="SECT1" >

10.5. MS Windows security options and how to configure +NAME="AEN1653" +>9.5. MS Windows security options and how to configure Samba for seemless integration

MS Windows clients may use encrypted passwords as part of a @@ -881,7 +910,9 @@ CLASS="SECT2" >

10.5.1. Use MS Windows NT as an authentication server

9.5.1. Use MS Windows NT as an authentication server

This method involves the additions of the following parameters in the smb.conf file:

10.5.2. Make Samba a member of an MS Windows NT security domain

9.5.2. Make Samba a member of an MS Windows NT security domain

This method involves additon of the following paramters in the smb.conf file:

10.5.3. Configure Samba as an authentication server

9.5.3. Configure Samba as an authentication server

This mode of authentication demands that there be on the Unix/Linux system both a Unix style account as well as an @@ -1011,7 +1046,9 @@ CLASS="SECT3" >

10.5.3.1. Users

9.5.3.1. Users

A user account that may provide a home directory should be created. The following Linux system commands are typical of @@ -1032,7 +1069,9 @@ CLASS="SECT3" >

10.5.3.2. MS Windows NT Machine Accounts

9.5.3.2. MS Windows NT Machine Accounts

These are required only when Samba is used as a domain controller. Refer to the Samba-PDC-HOWTO for more details.

10.6. Conclusions

9.6. Conclusions

Samba provides a flexible means to operate as...