1 <?xml version="1.0" encoding="iso-8859-1"?>
2 <!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
3 <chapter id="ClientConfig">
8 <title>MS Windows Network Configuration Guide</title>
11 <title>Features and Benefits</title>
14 Occasionally network administrators will report difficulty getting Microsoft Windows clients to interoperate
15 correctly with Samba servers. It would appear that some folks just can not accept the fact that the right way
16 to configure MS Windows network client is precisely as one would do when using Microsoft Windows NT4 or 200x
17 servers. Yet there is repetitious need to provide detailed Windows client configuration instructions.
21 The purpose of this chapter is to graphically illustrate MS Windows client configuration for the most common
22 critical aspects of such configuration. An experienced network administrator will not be interested in the
23 details of this chapter.
29 <title>Technical Details</title>
32 This chapter discusses TCP/IP protocol configuration as well as network membership for the platforms
33 that are in common use today. These are:
38 Microsoft Windows XP Professional.
41 Windows 2000 Professional.
44 Windows Millennium edition (Me).
49 <title>TCP/IP Configuration</title>
52 The builder of a house must ensure that all construction takes place on a firm foundation.
53 The same is true of TCP/IP-based networking. Fundamental network configuration problems
54 will plague all network users until they are resolved.
58 Microsoft Windows workstations and servers can be configured either with fixed
59 IP addresses or via DHCP. The examples that follow demonstrate the use of DHCP
60 and make only passing reference to those situations where fixed IP configuration
61 settings can be effected.
65 It is possible to use shortcuts or abbreviated keystrokes to arrive at a
66 particular configuration screen. The decision was made to base all examples in this
67 chapter on use of the <guibutton>Start</guibutton> button.
71 <title>MS Windows XP Professional</title>
74 There are two paths to the Windows XP TCP/IP configuration panel. Choose the access method that you prefer:
78 Click <guimenu>Start -> Control Panel -> Network Connections</guimenu>
82 <emphasis>Alternately,</emphasis> click <guimenu>Start -></guimenu>, and right click <guimenu>My Network Places</guimenu>
83 then select <guimenuitem>Properties</guimenuitem>
87 The following procedure steps through the Windows XP Professional TCP/IP configuration process:
92 On some installations the interface will be called <guimenu>Local Area Connection</guimenu> and
93 on others it will be called <guimenu>Network Bridge</guimenu>. On our system it is called <guimenu>Network Bridge</guimenu>.
94 Right click on <guimenu>Network Bridge -> Properties</guimenu>. See <link linkend="WXPP002"/>.
95 <figure id="WXPP002"><title>Network Bridge Configuration.</title><imagefile>WXPP002</imagefile></figure>
100 The Network Bridge Configuration, or Local Area Connection, panel is used to set TCP/IP protocol settings.
101 In <guimenuitem>This connection uses the following items:</guimenuitem> box,
102 click on <guimenu>Internet Protocol (TCP/IP)</guimenu>, then click the on <guibutton>Properties</guibutton>.
106 The default setting is DHCP enabled operation.
107 (i.e., <quote>Obtain an IP address automatically</quote>). See <link linkend="WXPP003"/>.
108 <figure id="WXPP003">
109 <title>Internet Protocol (TCP/IP) Properties.</title>
110 <imagefile>WXPP003</imagefile>
115 Many network administrators will want to use DHCP to configure all client TCP/IP
116 protocol stack settings. (For information on how to configure the ISC DHCP server
117 for Microsoft Windows client support see, <link linkend="DHCP"></link>.
121 If it is necessary to provide a fixed IP address, click on <quote>Use the following IP address</quote> and proceed to enter the
122 IP Address, the subnet mask, and the default gateway address in the boxes provided.
126 Click the <guibutton>Advanced</guibutton> button to proceed with TCP/IP configuration.
127 This opens a panel in which it is possible to create additional IP Addresses for this interface.
128 The technical name for the additional addresses is <emphasis>IP Aliases</emphasis>, and additionally this
129 panel permits the setting of more default gateways (routers). In most cases where DHCP is used, it will not be
130 necessary to create additional settings. See <link linkend="WXPP005"></link> to see the appearance of this panel.
131 <figure id="WXPP005"><title>Advanced Network Settings</title><imagefile>WXPP005</imagefile></figure>
135 Fixed settings may be required for DNS and WINS if these settings are not provided automatically via DHCP.
139 Click the <guimenu>DNS</guimenu> tab to add DNS server settings.
140 The example system uses manually configured DNS settings. When finished making changes, click the <guibutton>OK</guibutton> to commit
141 the settings. See <link linkend="WXPP014"/>.
142 <figure id="WXPP014"><title>DNS Configuration.</title><imagefile>WXPP014</imagefile></figure>
146 Click the <guibutton>WINS</guibutton> tab to add manual WINS server entries.
147 This step demonstrates an example system that uses manually configured WINS settings.
148 When finished making, changes click the <guibutton>OK</guibutton> to commit
149 the settings. See <link linkend="WXPP009"></link>.
150 <figure id="WXPP009"><title>WINS Configuration</title><imagefile>WXPP009</imagefile></figure>
157 <title>MS Windows 2000</title>
160 There are two paths to the Windows 2000 Professional TCP/IP configuration panel. Choose the access method that you prefer:
164 Click <guimenu>Start -> Control Panel -> Network and Dial-up Connections</guimenu>
168 <emphasis>Alternately,</emphasis> click on <guimenu>Start</guimenu>, then right click <guimenu>My Network Places</guimenu> and
169 select <guimenuitem>Properties</guimenuitem>.
173 The following procedure steps through the Windows XP Professional TCP/IP configuration process:
178 Right click on <guimenu>Local Area Connection</guimenu>, now click the
179 <guimenuitem>Properties</guimenuitem>. See <link linkend="w2kp001"></link>.
180 <figure id="w2kp001"><title>Local Area Connection Properties.</title><imagefile>w2kp001</imagefile></figure>
184 The Local Area Connection Properties is used to set TCP/IP protocol settings. Click on <guimenu>Internet Protocol (TCP/IP)</guimenu> in the
185 <guimenuitem>Components checked are used by this connection:</guimenuitem> box, then click the <guibutton>Properties</guibutton> button.
189 The default setting is DHCP enabled operation.
190 (i.e., <quote>Obtain an IP address automatically</quote>). See <link linkend="w2kp002"/>.
191 <figure id="w2kp002"><title>Internet Protocol (TCP/IP) Properties.</title><imagefile>w2kp002</imagefile></figure>
195 Many network administrators will want to use DHCP to configure all client TCP/IP
196 protocol stack settings. (For information on how to configure the ISC DHCP server
197 for Microsoft Windows client support, see <link linkend="DHCP"></link>.
201 If it is necessary to provide a fixed IP address, click on <quote>Use the following IP address</quote> and proceed to enter the
202 IP Address, the subnet mask, and the default gateway address in the boxes provided.
203 For this example we are assuming that all network clients will be configured using DHCP.
207 Click the <guimenu>Advanced</guimenu> button to proceed with TCP/IP configuration.
208 Refer to <link linkend="w2kp003"></link>.
209 <figure id="w2kp003"><title>Advanced Network Settings.</title><imagefile>w2kp003</imagefile></figure>
213 Fixed settings may be required for DNS and WINS if these settings are not provided automatically via DHCP.
217 Click the <guimenu>DNS</guimenu> tab to add DNS server settings.
218 The example system uses manually configured DNS settings. When finished making changes,
219 click on <guibutton>OK</guibutton> to commit the settings. See <link linkend="w2kp004"></link>.
220 <figure id="w2kp004"><title>DNS Configuration.</title><imagefile>w2kp004</imagefile></figure>
224 Click the <guibutton>WINS</guibutton> tab to add manual WINS server entries.
225 This step demonstrates an example system that uses manually configured WINS settings.
226 When finished making changes, click on <guibutton>OK</guibutton> to commit the settings.
227 See <link linkend="w2kp005"/>.
228 <figure id="w2kp005"><title>WINS Configuration.</title><imagefile>w2kp005</imagefile></figure>
236 <title>MS Windows Me</title>
239 There are two paths to the Windows Millennium edition (Me) TCP/IP configuration panel. Choose the access method that you prefer:
243 Click <guimenu>Start -> Control Panel -> Network Connections</guimenu>
247 <emphasis>Alternately,</emphasis> click on <guimenu>Start -></guimenu>, and right click on <guimenu>My Network Places</guimenu>
248 then select <guimenuitem>Properties</guimenuitem>.
252 The following procedure steps through the Windows Me TCP/IP configuration process:
257 In the box labeled <guimenuitem>The following network components are installed:</guimenuitem>,
258 click on <guimenu>Internet Protocol TCP/IP</guimenu>, now click on the <guibutton>Properties</guibutton> button. See <link linkend="WME001"/>.
259 <figure id="WME001"><title>The Windows Me Network Configuration Panel.</title><imagefile>WME001</imagefile></figure>
263 Many network administrators will want to use DHCP to configure all client TCP/IP
264 protocol stack settings. (For information on how to configure the ISC DHCP server
265 for Microsoft Windows client support see, <link linkend="DHCP"/>.
266 The default setting on Microsoft Windows Me workstations is for DHCP enabled operation,
267 i.e., <guimenu>Obtain IP address automatically</guimenu> is enabled. See <link linkend="WME002"/>.
268 <figure id="WME002"><title>IP Address.</title><imagefile>WME002</imagefile></figure>
272 If it is necessary to provide a fixed IP address, click on <guimenuitem>Specify an IP address</guimenuitem> and proceed to enter the
273 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.
277 Fixed settings may be required for DNS and WINS if these settings are not provided automatically via DHCP.
281 If necessary, click the <guimenu>DNS Configuration</guimenu> tab to add DNS server settings.
282 Click the <guibutton>WINS Configuration</guibutton> tab to add WINS server settings.
283 The <guimenu>Gateway</guimenu> tab allows additional gateways (router addresses) to be added to the network
284 interface settings. In most cases where DHCP is used, it will not be necessary to
285 create these manual settings.
289 The following example uses manually configured WINS settings. See <link linkend="WME005"/>.
290 When finished making changes, click on <guibutton>OK</guibutton> to commit the settings.
291 <figure id="WME005"><title>DNS Configuration.</title><imagefile>WME005</imagefile></figure>
295 This is an example of a system that uses manually configured WINS settings. One situation where
296 this might apply is on a network that has a single DHCP server that provides settings for multiple
297 Windows workgroups or domains. See <link linkend="WME003"></link>.
298 <figure id="WME003"><title>WINS Configuration.</title><imagefile>WME003</imagefile></figure>
308 <title>Joining a Domain: Windows 2000/XP Professional</title>
311 Microsoft Windows NT/200x/XP Professional platforms can participate in Domain Security.
312 This section steps through the process for making a Windows 200x/XP Professional machine a
313 member of a Domain Security environment. It should be noted that this process is identical
314 when joining a domain that is controlled by Windows NT4/200x as well as a Samba PDC.
319 Click <guimenu>Start</guimenu>.
323 Right click <guimenu>My Computer</guimenu>, then select <guimenuitem>Properties</guimenuitem>.
327 The opening panel is the same one that can be reached by clicking <guimenu>System</guimenu> on the Control Panel.
328 See <link linkend="wxpp001"></link>.
329 <figure id="wxpp001"><title>The General Panel.</title><imagefile>wxpp001</imagefile></figure>
333 Click the <guimenu>Computer Name</guimenu> tab.
334 This panel shows the <guimenuitem>Computer Description</guimenuitem>, the <guimenuitem>Full computer name</guimenuitem>,
335 and the <guimenuitem>Workgroup</guimenuitem> or <guimenuitem>Domain name</guimenuitem>.
339 Clicking the <guimenu>Network ID</guimenu> button will launch the configuration wizard. Do not use this with
340 Samba-3. If you wish to change the computer name, join or leave the domain, click the <guimenu>Change</guimenu> button.
341 See <link linkend="wxpp004"></link>.
342 <figure id="wxpp004"><title>The Computer Name Panel.</title><imagefile>wxpp004</imagefile></figure>
346 Click on <guimenu>Change</guimenu>. This panel shows that our example machine (TEMPTATION) is in a workgroup called WORKGROUP.
347 We will join the domain called MIDEARTH. See <link linkend="wxpp006"></link>.
348 <figure id="wxpp006"><title>The Computer Name Changes Panel.</title><imagefile>wxpp006</imagefile></figure>
352 Enter the name <guimenu>MIDEARTH</guimenu> in the field below the Domain radio button.
356 This panel shows that our example machine (TEMPTATION) is set to join the domain called MIDEARTH. See <link linkend="wxpp007"></link>.
357 <figure id="wxpp007"><title>The Computer Name Changes Panel &smbmdash; Domain MIDEARTH.</title><imagefile>wxpp007</imagefile></figure>
361 Now click the <guimenu>OK</guimenu> button. A dialog box should appear to allow you to provide the credentials (username and password)
362 of a Domain administrative account that has the rights to add machines to the Domain.
366 Enter the name <quote>root</quote> and the root password from your Samba-3 server. See <link linkend="wxpp008"></link>.
367 <figure id="wxpp008"><title>Computer Name Changes &smbmdash; User name and Password Panel.</title><imagefile>wxpp008</imagefile></figure>
371 Click on <guimenu>OK</guimenu>.
375 The <quote>Welcome to the MIDEARTH domain.</quote> dialog box should appear. At this point the machine must be rebooted.
376 Joining the domain is now complete.
384 <title>Domain Logon Configuration: Windows 9x/Me</title>
387 We follow the convention used by most in saying that Windows 9x/Me machines can participate in Domain logons. The truth is
388 that these platforms can use only the LanManager network logon protocols.
392 Windows XP Home edition cannot participate in Domain or LanManager network logons.
397 Right click on the <guimenu>Network Neighborhood</guimenu> icon.
401 The Network Configuration Panel allows all common network settings to be changed.
402 See <link linkend="WME009"></link>.
403 <figure id="WME009"><title>The Network Panel.</title><imagefile>WME009</imagefile></figure>
407 Make sure that the <guimenu>Client for Microsoft Networks</guimenu> driver is installed as shown.
408 Click on the <guimenu>Client for Microsoft Networks</guimenu> entry in <guimenu>The following network
409 components are installed:</guimenu> box. Then click the <guibutton>Properties</guibutton> button.
413 The Client for Microsoft Networks Properties panel is the correct location to configure network logon
414 settings. See <link linkend="WME010"></link>.
415 <figure id="WME010"><title>Client for Microsoft Networks Properties Panel.</title><imagefile>WME010</imagefile></figure>
419 Enter the Windows NT domain name, check the <guimenu>Log on to Windows NT domain</guimenu> box,
420 click <guimenu>OK</guimenu>.
424 Click on the <guimenu>Identification</guimenu> button. This is the location at which the workgroup
425 (domain) name and the machine name (computer name) need to be set. See <link linkend="WME013"></link>.
426 <figure id="WME013"><title>Identification Panel.</title><imagefile>WME013</imagefile></figure>
430 Now click the <guimenu>Access Control</guimenu> button. If you want to be able to assign share access
431 permissions using domain user and group accounts, it is necessary to enable
432 <guimenu>User-level access control</guimenu> as shown in this panel. See <link linkend="WME014"></link>.
433 <figure id="WME014"><title>Identification Panel.</title><imagefile>WME014</imagefile></figure>
443 <title>Common Errors</title>
446 The most common errors that can afflict Windows networking systems include:
450 <listitem><para>Incorrect IP address.</para></listitem>
451 <listitem><para>Incorrect or inconsistent netmasks.</para></listitem>
452 <listitem><para>Incorrect router address.</para></listitem>
453 <listitem><para>Incorrect DNS server address.</para></listitem>
454 <listitem><para>Incorrect WINS server address.</para></listitem>
455 <listitem><para>Use of a Network Scope setting &smbmdash; watch out for this one!</para></listitem>
459 The most common reasons for which a Windows NT/200x/XP Professional client cannot join the Samba controlled domain are:
463 <listitem><para>&smb.conf; does not have correct <smbconfoption name="add machine script"/> settings.</para></listitem>
464 <listitem><para><quote>root</quote> account is not in password backend database.</para></listitem>
465 <listitem><para>Attempt to use a user account instead of the <quote>root</quote> account to join a machine to the domain.</para></listitem>
466 <listitem><para>Open connections from the workstation to the server.</para></listitem>
467 <listitem><para>Firewall or filter configurations in place on either the client or on the Samba server.</para></listitem>