mirror of
https://github.com/samba-team/samba.git
synced 2025-02-10 13:57:47 +03:00
Another update.
This commit is contained in:
John Terpstra
Gerald W. Carter
parent
92c45d0294
commit
ffbeafb849
@ -11,13 +11,18 @@
|
||||
<title>Features and Benefits</title>
|
||||
|
||||
<para>
|
||||
<indexterm><primary>network difficulty</primary></indexterm>
|
||||
<indexterm><primary>network client</primary></indexterm>
|
||||
<indexterm><primary>client client instructions</primary></indexterm>
|
||||
Occasionally network administrators report difficulty getting Microsoft Windows clients to interoperate
|
||||
correctly with Samba servers. It seems that some folks just cannot accept the fact that the right way
|
||||
to configure MS Windows network client is precisely as one would do when using MS Windows NT4 or 200x
|
||||
to configure an MS Windows network client is precisely as one would do when using MS Windows NT4 or 200x
|
||||
servers. Yet there is repetitious need to provide detailed Windows client configuration instructions.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
<indexterm><primary>graphically illustrated client configuration</primary></indexterm>
|
||||
<indexterm><primary>critical aspects of configuration</primary></indexterm>
|
||||
The purpose of this chapter is to graphically illustrate MS Windows client configuration for the most common
|
||||
critical aspects of such configuration. An experienced network administrator will not be interested in the
|
||||
details of this chapter.
|
||||
@ -29,6 +34,8 @@ details of this chapter.
|
||||
<title>Technical Details</title>
|
||||
|
||||
<para>
|
||||
<indexterm><primary>TCP/IP protocol configuration</primary></indexterm>
|
||||
<indexterm><primary>network membership</primary></indexterm>
|
||||
This chapter discusses TCP/IP protocol configuration as well as network membership for the platforms
|
||||
that are in common use today. These are:
|
||||
</para>
|
||||
@ -49,12 +56,16 @@ that are in common use today. These are:
|
||||
<title>TCP/IP Configuration</title>
|
||||
|
||||
<para>
|
||||
<indexterm><primary>network configuration problems</primary></indexterm>
|
||||
<indexterm><primary>plague network users</primary></indexterm>
|
||||
The builder of a house must ensure that all construction takes place on a firm foundation.
|
||||
The same is true for the builder of a TCP/IP-based networking system. Fundamental network configuration problems
|
||||
will plague all network users until they are resolved.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
<indexterm><primary>fixed IP addresses</primary></indexterm>
|
||||
<indexterm><primary>DHCP</primary></indexterm>
|
||||
MS Windows workstations and servers can be configured either with fixed
|
||||
IP addresses or via DHCP. The examples that follow demonstrate the use of DHCP
|
||||
and make only passing reference to those situations where fixed IP configuration
|
||||
@ -62,6 +73,8 @@ that are in common use today. These are:
|
||||
</para>
|
||||
|
||||
<para>
|
||||
<indexterm><primary>shortcuts</primary></indexterm>
|
||||
<indexterm><primary>abbreviated keystrokes</primary></indexterm>
|
||||
It is possible to use shortcuts or abbreviated keystrokes to arrive at a
|
||||
particular configuration screen. The decision was made to base all examples in this
|
||||
chapter on use of the <guibutton>Start</guibutton> button.
|
||||
@ -71,6 +84,7 @@ that are in common use today. These are:
|
||||
<title>MS Windows XP Professional</title>
|
||||
|
||||
<para>
|
||||
<indexterm><primary>Windows XP TCP/IP</primary></indexterm>
|
||||
There are two paths to the Windows XP TCP/IP configuration panel. Choose the access method that you prefer:
|
||||
</para>
|
||||
|
||||
@ -84,11 +98,15 @@ that are in common use today. These are:
|
||||
</para>
|
||||
|
||||
<para>
|
||||
<indexterm><primary>Windows XP Professional</primary></indexterm>
|
||||
The following procedure steps through the Windows XP Professional TCP/IP configuration process:
|
||||
</para>
|
||||
|
||||
<procedure>
|
||||
<step><para>
|
||||
<indexterm><primary>Local Area Connection</primary></indexterm>
|
||||
<indexterm><primary>Network Bridge</primary></indexterm>
|
||||
<indexterm><primary>interface</primary></indexterm>
|
||||
On some installations the interface will be called <guimenu>Local Area Connection</guimenu> and
|
||||
on others it will be called <guimenu>Network Bridge</guimenu>. On our system it is called <guimenu>Network Bridge</guimenu>.
|
||||
Right-click on <guimenu>Network Bridge -> Properties</guimenu>. See <link linkend="WXPP002"/>.
|
||||
@ -97,12 +115,16 @@ that are in common use today. These are:
|
||||
</step>
|
||||
|
||||
<step><para>
|
||||
<indexterm><primary>TCP/IP protocol settings</primary></indexterm>
|
||||
<indexterm><primary>Network Bridge Configuration</primary></indexterm>
|
||||
The Network Bridge Configuration, or Local Area Connection, panel is used to set TCP/IP protocol settings.
|
||||
In <guimenuitem>This connection uses the following items:</guimenuitem> box,
|
||||
click on <guimenu>Internet Protocol (TCP/IP)</guimenu>, then click on <guibutton>Properties</guibutton>.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
<indexterm><primary>DHCP-enabled operation</primary></indexterm>
|
||||
<indexterm><primary>IP address automatically</primary></indexterm>
|
||||
The default setting is DHCP-enabled operation
|
||||
(i.e., <quote>Obtain an IP address automatically</quote>). See <link linkend="WXPP003"/>.
|
||||
<figure id="WXPP003">
|
||||
@ -112,6 +134,10 @@ that are in common use today. These are:
|
||||
</para>
|
||||
|
||||
<para>
|
||||
<indexterm><primary>DHCP</primary></indexterm>
|
||||
<indexterm><primary>TCP/IP</primary></indexterm>
|
||||
<indexterm><primary>DNS</primary></indexterm>
|
||||
<indexterm><primary>ISC DHCP server</primary></indexterm>
|
||||
Many network administrators will want to use DHCP to configure all client TCP/IP
|
||||
protocol stack settings. (For information on how to configure the ISC DHCP server
|
||||
for Windows client support see <link linkend="DHCP">the DNS and DHCP Configuration Guide</link>,
|
||||
@ -119,11 +145,18 @@ that are in common use today. These are:
|
||||
</para>
|
||||
|
||||
<para>
|
||||
<indexterm><primary>fixed IP address</primary></indexterm>
|
||||
<indexterm><primary>subnet mask</primary></indexterm>
|
||||
<indexterm><primary>gateway address</primary></indexterm>
|
||||
If it is necessary to provide a fixed IP address, click on <quote>Use the following IP address</quote> and enter the
|
||||
IP Address, the subnet mask, and the default gateway address in the boxes provided.
|
||||
</para></step>
|
||||
|
||||
<step><para>
|
||||
<indexterm><primary>Advanced TCP/IP configuration</primary></indexterm>
|
||||
<indexterm><primary>TCP/IP configuration</primary></indexterm>
|
||||
<indexterm><primary>IP aliases</primary></indexterm>
|
||||
<indexterm><primary>default gateways</primary></indexterm>
|
||||
Click the <guibutton>Advanced</guibutton> button to proceed with TCP/IP configuration.
|
||||
This opens a panel in which it is possible to create additional IP addresses for this interface.
|
||||
The technical name for the additional addresses is <emphasis>IP aliases</emphasis>, and additionally this
|
||||
@ -133,22 +166,29 @@ that are in common use today. These are:
|
||||
</para>
|
||||
|
||||
<para>
|
||||
<indexterm><primary>DNS</primary></indexterm>
|
||||
<indexterm><primary>WINS</primary></indexterm>
|
||||
<indexterm><primary>DHCP</primary></indexterm>
|
||||
Fixed settings may be required for DNS and WINS if these settings are not provided automatically via DHCP.
|
||||
</para></step>
|
||||
|
||||
<step><para>
|
||||
<indexterm><primary>DNS server settings</primary></indexterm>
|
||||
<indexterm><primary>manually configured DNS settings</primary></indexterm>
|
||||
Click the <guimenu>DNS</guimenu> tab to add DNS server settings.
|
||||
The example system uses manually configured DNS settings. When finished making changes, click the <guibutton>OK</guibutton> to commit
|
||||
the settings. See <link linkend="WXPP014"/>.
|
||||
<figure id="WXPP014"><title>DNS Configuration.</title><imagefile>WXPP014</imagefile></figure>
|
||||
The example system uses manually configured DNS settings. When finished making changes, click the
|
||||
<guibutton>OK</guibutton> to commit the settings. See <link linkend="WXPP014"/>.
|
||||
<figure id="WXPP014"> <title>DNS Configuration.</title> <imagefile>WXPP014</imagefile> </figure>
|
||||
</para></step>
|
||||
|
||||
<step><para>
|
||||
<indexterm><primary>WINS</primary></indexterm>
|
||||
<indexterm><primary>manual WINS server entries</primary></indexterm>
|
||||
Click the <guibutton>WINS</guibutton> tab to add manual WINS server entries.
|
||||
This step demonstrates an example system that uses manually configured WINS settings.
|
||||
When finished making changes, click <guibutton>OK</guibutton> to commit
|
||||
the settings. See <link linkend="WXPP009"></link>.
|
||||
<figure id="WXPP009"><title>WINS Configuration</title><imagefile>WXPP009</imagefile></figure>
|
||||
<figure id="WXPP009"><title>WINS Configuration</title><imagefile>WXPP009</imagefile></figure>
|
||||
</para></step>
|
||||
</procedure>
|
||||
|
||||
@ -158,6 +198,8 @@ that are in common use today. These are:
|
||||
<title>MS Windows 2000</title>
|
||||
|
||||
<para>
|
||||
<indexterm><primary>Windows 2000 Professional TCP/IP</primary></indexterm>
|
||||
<indexterm><primary>TCP/IP configuration panel</primary></indexterm>
|
||||
There are two paths to the Windows 2000 Professional TCP/IP configuration panel. Choose the access method that you prefer:
|
||||
</para>
|
||||
|
||||
@ -171,6 +213,7 @@ that are in common use today. These are:
|
||||
</para>
|
||||
|
||||
<para>
|
||||
<indexterm><primary>Windows XP Professional TCP/IP</primary></indexterm>
|
||||
The following procedure steps through the Windows XP Professional TCP/IP configuration process:
|
||||
</para>
|
||||
|
||||
@ -182,23 +225,32 @@ that are in common use today. These are:
|
||||
</para></step>
|
||||
|
||||
<step><para>
|
||||
The Local Area Connection Properties is used to set TCP/IP protocol settings. Click on <guimenu>Internet Protocol (TCP/IP)</guimenu> in the
|
||||
<guimenuitem>Components checked are used by this connection:</guimenuitem> box, then click the <guibutton>Properties</guibutton> button.
|
||||
<indexterm><primary>Local Area Connection Properties</primary></indexterm>
|
||||
<indexterm><primary>TCP/IP protocol settings</primary></indexterm>
|
||||
The Local Area Connection Properties is used to set TCP/IP protocol settings. Click on
|
||||
<guimenu>Internet Protocol (TCP/IP)</guimenu> in the <guimenuitem>Components checked are used by this
|
||||
connection:</guimenuitem> box, then click the <guibutton>Properties</guibutton> button.
|
||||
</para></step>
|
||||
|
||||
<step><para>
|
||||
<indexterm><primary>DHCP-enabled</primary></indexterm>
|
||||
<indexterm><primary>IP address automatically</primary></indexterm>
|
||||
The default setting is DHCP-enabled operation
|
||||
(i.e., <quote>Obtain an IP address automatically</quote>). See <link linkend="w2kp002"/>.
|
||||
<figure id="w2kp002"><title>Internet Protocol (TCP/IP) Properties.</title><imagefile>w2kp002</imagefile></figure>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
<indexterm><primary>DHCP</primary></indexterm>
|
||||
<indexterm><primary>protocol stack settings</primary></indexterm>
|
||||
Many network administrators will want to use DHCP to configure all client TCP/IP
|
||||
protocol stack settings. (For information on how to configure the ISC DHCP server
|
||||
for Windows client support, see, <link linkend="DHCP"></link>.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
<indexterm><primary>fixed IP address</primary></indexterm>
|
||||
<indexterm><primary>network clients</primary></indexterm>
|
||||
If it is necessary to provide a fixed IP address, click on <quote>Use the following IP address</quote> and enter the
|
||||
IP Address, the subnet mask, and the default gateway address in the boxes provided.
|
||||
For this example we are assuming that all network clients will be configured using DHCP.
|
||||
@ -211,10 +263,15 @@ that are in common use today. These are:
|
||||
</para>
|
||||
|
||||
<para>
|
||||
<indexterm><primary>DNS</primary></indexterm>
|
||||
<indexterm><primary>WINS</primary></indexterm>
|
||||
<indexterm><primary>DHCP</primary></indexterm>
|
||||
Fixed settings may be required for DNS and WINS if these settings are not provided automatically via DHCP.
|
||||
</para></step>
|
||||
|
||||
<step><para>
|
||||
<indexterm><primary>DNS server settings</primary></indexterm>
|
||||
<indexterm><primary>commit the settings</primary></indexterm>
|
||||
Click the <guimenu>DNS</guimenu> tab to add DNS server settings.
|
||||
The example system uses manually configured DNS settings. When finished making changes,
|
||||
click <guibutton>OK</guibutton> to commit the settings. See <link linkend="w2kp004"></link>.
|
||||
@ -222,6 +279,8 @@ that are in common use today. These are:
|
||||
</para></step>
|
||||
|
||||
<step><para>
|
||||
<indexterm><primary>manual WINS server entries</primary></indexterm>
|
||||
<indexterm><primary>WINS</primary></indexterm>
|
||||
Click the <guibutton>WINS</guibutton> tab to add manual WINS server entries.
|
||||
This step demonstrates an example system that uses manually configured WINS settings.
|
||||
When finished making changes, click <guibutton>OK</guibutton> to commit the settings.
|
||||
@ -239,6 +298,9 @@ that are in common use today. These are:
|
||||
<title>MS Windows Me</title>
|
||||
|
||||
<para>
|
||||
<indexterm><primary>Windows Millennium edition (Me) TCP/IP</primary></indexterm>
|
||||
<indexterm><primary>Windows Millennium</primary></indexterm>
|
||||
<indexterm><primary>TCP/IP configuration</primary></indexterm>
|
||||
There are two paths to the Windows Millennium edition (Me) TCP/IP configuration panel. Choose the access method that you prefer:
|
||||
</para>
|
||||
|
||||
@ -247,16 +309,20 @@ that are in common use today. These are:
|
||||
</para>
|
||||
|
||||
<para>
|
||||
<indexterm><primary>My Network Places</primary></indexterm>
|
||||
<indexterm><primary>Properties</primary></indexterm>
|
||||
<emphasis>Alternatively,</emphasis> click on <guimenu>Start -></guimenu>, and right click on <guimenu>My Network Places</guimenu>
|
||||
then select <guimenuitem>Properties</guimenuitem>.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
<indexterm><primary>Windows Me TCP/IP</primary></indexterm>
|
||||
The following procedure steps through the Windows Me TCP/IP configuration process:
|
||||
</para>
|
||||
|
||||
<procedure>
|
||||
<step><para>
|
||||
<indexterm><primary>Internet Protocol TCP/IP</primary></indexterm>
|
||||
In the box labeled <guimenuitem>The following network components are installed:</guimenuitem>,
|
||||
click on <guimenu>Internet Protocol TCP/IP</guimenu>, then click on the <guibutton>Properties</guibutton> button.
|
||||
See <link linkend="WME001"></link>.
|
||||
@ -267,6 +333,9 @@ that are in common use today. These are:
|
||||
</para></step>
|
||||
|
||||
<step><para>
|
||||
<indexterm><primary>DHCP</primary></indexterm>
|
||||
<indexterm><primary>TCP/IP</primary></indexterm>
|
||||
<indexterm><primary>ISC DHCP server</primary></indexterm>
|
||||
Many network administrators will want to use DHCP to configure all client TCP/IP
|
||||
protocol stack settings. (For information on how to configure the ISC DHCP server
|
||||
for Windows client support see <link linkend="DHCP">the DNS and DHCP Configuration Guide</link>,
|
||||
@ -276,15 +345,22 @@ that are in common use today. These are:
|
||||
</para>
|
||||
|
||||
<para>
|
||||
<indexterm><primary>Specify an IP address</primary></indexterm>
|
||||
<indexterm><primary>subnet mask</primary></indexterm>
|
||||
<indexterm><primary>DHCP</primary></indexterm>
|
||||
If it is necessary to provide a fixed IP address, click on <guimenuitem>Specify an IP address</guimenuitem> and enter the
|
||||
IP Address and the subnet mask in the boxes provided. For this example we are assuming that all network clients will be configured using DHCP.
|
||||
IP Address and the subnet mask in the boxes provided. For this example we are assuming that all
|
||||
network clients will be configured using DHCP.
|
||||
</para></step>
|
||||
|
||||
<step><para>
|
||||
<indexterm><primary>DNS</primary></indexterm>
|
||||
<indexterm><primary>WINS</primary></indexterm>
|
||||
Fixed settings may be required for DNS and WINS if these settings are not provided automatically via DHCP.
|
||||
</para></step>
|
||||
|
||||
<step><para>
|
||||
<indexterm><primary>WINS server settings</primary></indexterm>
|
||||
If necessary, click the <guimenu>DNS Configuration</guimenu> tab to add DNS server settings.
|
||||
Click the <guibutton>WINS Configuration</guibutton> tab to add WINS server settings.
|
||||
The <guimenu>Gateway</guimenu> tab allows additional gateways (router addresses) to be added to the network
|
||||
@ -293,12 +369,16 @@ that are in common use today. These are:
|
||||
</para></step>
|
||||
|
||||
<step><para>
|
||||
<indexterm><primary>WINS</primary></indexterm>
|
||||
<indexterm><primary>manually configured</primary></indexterm>
|
||||
The following example uses manually configured WINS settings. See <link linkend="WME005"></link>.
|
||||
When finished making changes, click <guibutton>OK</guibutton> to commit the settings.
|
||||
<figure id="WME005"><title>DNS Configuration.</title><imagefile>WME005</imagefile></figure>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
<indexterm><primary>single DHCP server</primary></indexterm>
|
||||
<indexterm><primary>multiple Windows workgroups or domains</primary></indexterm>
|
||||
This is an example of a system that uses manually configured WINS settings. One situation where
|
||||
this might apply is on a network that has a single DHCP server that provides settings for multiple
|
||||
Windows workgroups or domains. See <link linkend="WME003"></link>.
|
||||
@ -315,6 +395,10 @@ that are in common use today. These are:
|
||||
<title>Joining a Domain: Windows 2000/XP Professional</title>
|
||||
|
||||
<para>
|
||||
<indexterm><primary>Windows NT/200x/XP Professional</primary></indexterm>
|
||||
<indexterm><primary>domain security</primary></indexterm>
|
||||
<indexterm><primary>domain member</primary></indexterm>
|
||||
<indexterm><primary>domain joining</primary></indexterm>
|
||||
Microsoft Windows NT/200x/XP Professional platforms can participate in domain security.
|
||||
This section steps through the process for making a Windows 200x/XP Professional machine a
|
||||
member of a domain security environment. It should be noted that this process is identical
|
||||
@ -331,57 +415,70 @@ that are in common use today. These are:
|
||||
</para></step>
|
||||
|
||||
<step><para>
|
||||
<indexterm><primary>Control Panel</primary></indexterm>
|
||||
The opening panel is the same one that can be reached by clicking <guimenu>System</guimenu> on the Control Panel.
|
||||
See <link linkend="wxpp001"></link>.
|
||||
<figure id="wxpp001"><title>The General Panel.</title><imagefile>wxpp001</imagefile></figure>
|
||||
</para></step>
|
||||
|
||||
<step><para>
|
||||
<indexterm><primary>Computer Name</primary></indexterm>
|
||||
Click the <guimenu>Computer Name</guimenu> tab.
|
||||
This panel shows the <guimenuitem>Computer Description</guimenuitem>, the <guimenuitem>Full computer name</guimenuitem>,
|
||||
and the <guimenuitem>Workgroup</guimenuitem> or <guimenuitem>Domain name</guimenuitem>.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
<indexterm><primary>Network ID</primary></indexterm>
|
||||
<indexterm><primary>configuration wizard</primary></indexterm>
|
||||
Clicking the <guimenu>Network ID</guimenu> button will launch the configuration wizard. Do not use this with
|
||||
Samba-3. If you wish to change the computer name or join or leave the domain, click the <guimenu>Change</guimenu> button.
|
||||
See <link linkend="wxpp004"></link>.
|
||||
<figure id="wxpp004"><title>The Computer Name Panel.</title><imagefile>wxpp004</imagefile></figure>
|
||||
</para></step>
|
||||
</para></step>
|
||||
|
||||
<step><para>
|
||||
Click on <guimenu>Change</guimenu>. This panel shows that our example machine (TEMPTATION) is in a workgroup called WORKGROUP.
|
||||
We will join the domain called MIDEARTH. See <link linkend="wxpp006"></link>.
|
||||
<figure id="wxpp006"><title>The Computer Name Changes Panel.</title><imagefile>wxpp006</imagefile></figure>
|
||||
</para></step>
|
||||
</para></step>
|
||||
|
||||
<step><para>
|
||||
<indexterm><primary>domain radio button</primary></indexterm>
|
||||
Enter the name <guimenu>MIDEARTH</guimenu> in the field below the domain radio button.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
<para>
|
||||
This panel shows that our example machine (TEMPTATION) is set to join the domain called MIDEARTH. See <link linkend="wxpp007"></link>.
|
||||
<figure id="wxpp007"><title>The Computer Name Changes Panel &smbmdash; Domain MIDEARTH.</title><imagefile>wxpp007</imagefile></figure>
|
||||
</para></step>
|
||||
</para></step>
|
||||
|
||||
<step><para>
|
||||
Now click the <guimenu>OK</guimenu> button. A dialog box should appear to allow you to provide the credentials (username and password)
|
||||
of a domain administrative account that has the rights to add machines to the domain.
|
||||
<indexterm><primary>credentials</primary></indexterm>
|
||||
<indexterm><primary>username and password</primary></indexterm>
|
||||
Now click the <guimenu>OK</guimenu> button. A dialog box should appear to allow you to provide the
|
||||
credentials (username and password) of a domain administrative account that has the rights to add machines to
|
||||
the domain.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
<para>
|
||||
<indexterm><primary>root</primary></indexterm>
|
||||
Enter the name <quote>root</quote> and the root password from your Samba-3 server. See <link linkend="wxpp008"></link>.
|
||||
<figure id="wxpp008"><title>Computer Name Changes &smbmdash; Username and Password Panel.</title><imagefile>wxpp008</imagefile></figure>
|
||||
</para></step>
|
||||
<figure id="wxpp008">
|
||||
<title>Computer Name Changes &smbmdash; Username and PasswordPanel.</title><imagefile>wxpp008</imagefile>
|
||||
</figure>
|
||||
</para></step>
|
||||
|
||||
<step><para>
|
||||
Click on <guimenu>OK</guimenu>.
|
||||
</para>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
<indexterm><primary>Welcome</primary></indexterm>
|
||||
<indexterm><primary>rebooted</primary></indexterm>
|
||||
The <quote>Welcome to the MIDEARTH domain.</quote> dialog box should appear. At this point the machine must be rebooted.
|
||||
Joining the domain is now complete.
|
||||
</para></step>
|
||||
</para></step>
|
||||
|
||||
</procedure>
|
||||
|
||||
@ -391,11 +488,17 @@ that are in common use today. These are:
|
||||
<title>Domain Logon Configuration: Windows 9x/Me</title>
|
||||
|
||||
<para>
|
||||
<indexterm><primary>Windows 9x/Me</primary></indexterm>
|
||||
<indexterm><primary>domain logon</primary></indexterm>
|
||||
<indexterm><primary>LanManager</primary></indexterm>
|
||||
We follow the convention used by most in saying that Windows 9x/Me machines can participate in domain logons. The truth is
|
||||
that these platforms can use only the LanManager network logon protocols.
|
||||
</para>
|
||||
|
||||
<note><para>
|
||||
<indexterm><primary>Windows XP Home edition</primary></indexterm>
|
||||
<indexterm><primary>LanManager</primary></indexterm>
|
||||
<indexterm><primary>network logon</primary></indexterm>
|
||||
Windows XP Home edition cannot participate in domain or LanManager network logons.
|
||||
</para></note>
|
||||
|
||||
@ -411,29 +514,42 @@ that are in common use today. These are:
|
||||
</para>
|
||||
|
||||
<para>
|
||||
<indexterm><primary>Client for Microsoft Networks</primary></indexterm>
|
||||
<indexterm><primary>Properties</primary></indexterm>
|
||||
Make sure that the <guimenu>Client for Microsoft Networks</guimenu> driver is installed as shown.
|
||||
Click on the <guimenu>Client for Microsoft Networks</guimenu> entry in <guimenu>The following network
|
||||
components are installed:</guimenu> box. Then click the <guibutton>Properties</guibutton> button.
|
||||
</para></step>
|
||||
|
||||
<step><para>
|
||||
<indexterm><primary>Networks Properties</primary></indexterm>
|
||||
<indexterm><primary>network logon</primary></indexterm>
|
||||
The Client for Microsoft Networks Properties panel is the correct location to configure network logon
|
||||
settings. See <link linkend="WME010"></link>.
|
||||
<figure id="WME010"><title>Client for Microsoft Networks Properties Panel.</title><imagefile>WME010</imagefile></figure>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
<indexterm><primary>Windows NT domain name</primary></indexterm>
|
||||
<indexterm><primary>domain name</primary></indexterm>
|
||||
Enter the Windows NT domain name, check the <guimenu>Log on to Windows NT domain</guimenu> box,
|
||||
and click <guimenu>OK</guimenu>.
|
||||
</para></step>
|
||||
|
||||
<step><para>
|
||||
<indexterm><primary>Identification</primary></indexterm>
|
||||
<indexterm><primary>workgroup</primary></indexterm>
|
||||
<indexterm><primary>computer name</primary></indexterm>
|
||||
Click on the <guimenu>Identification</guimenu> button. This is the location at which the workgroup
|
||||
(domain) name and the machine name (computer name) need to be set. See <link linkend="WME013"></link>.
|
||||
<figure id="WME013"><title>Identification Panel.</title><imagefile>WME013</imagefile></figure>
|
||||
</para></step>
|
||||
|
||||
<step><para>
|
||||
<indexterm><primary>Access Control</primary></indexterm>
|
||||
<indexterm><primary>group accounts</primary></indexterm>
|
||||
<indexterm><primary>domain user</primary></indexterm>
|
||||
<indexterm><primary>User-level access control</primary></indexterm>
|
||||
Now click the <guimenu>Access Control</guimenu> button. If you want to be able to assign share access
|
||||
permissions using domain user and group accounts, it is necessary to enable
|
||||
<guimenu>User-level access control</guimenu> as shown in this panel. See <link linkend="WME014"></link>.
|
||||
@ -450,6 +566,8 @@ that are in common use today. These are:
|
||||
<title>Common Errors</title>
|
||||
|
||||
<para>
|
||||
<indexterm><primary>networking systems</primary></indexterm>
|
||||
<indexterm><primary>errors that can afflict</primary></indexterm>
|
||||
The most common errors that can afflict Windows networking systems include:
|
||||
</para>
|
||||
|
||||
@ -463,6 +581,8 @@ The most common errors that can afflict Windows networking systems include:
|
||||
</itemizedlist>
|
||||
|
||||
<para>
|
||||
<indexterm><primary>Windows NT/200x/XP Professional</primary></indexterm>
|
||||
<indexterm><primary>cannot join domain</primary></indexterm>
|
||||
The most common reasons for which a Windows NT/200x/XP Professional client cannot join the Samba controlled domain are:
|
||||
</para>
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user