1 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 8. MS Windows Network Configuration Guide</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.68.1"><link rel="start" href="index.html" title="The Official Samba-3 HOWTO and Reference Guide"><link rel="up" href="type.html" title="Part II. Server Configuration Basics"><link rel="prev" href="StandAloneServer.html" title="Chapter 7. Standalone Servers"><link rel="next" href="optional.html" title="Part III. Advanced Configuration"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 8. MS Windows Network Configuration Guide</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="StandAloneServer.html">Prev</a> </td><th width="60%" align="center">Part II. Server Configuration Basics</th><td width="20%" align="right"> <a accesskey="n" href="optional.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="ClientConfig"></a>Chapter 8. MS Windows Network Configuration Guide</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email"><<a href="mailto:jht@samba.org">jht@samba.org</a>></code></p></div></div></div></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="ClientConfig.html#id2543178">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="ClientConfig.html#id2543238">Technical Details</a></span></dt><dd><dl><dt><span class="sect2"><a href="ClientConfig.html#id2543282">TCP/IP Configuration</a></span></dt><dt><span class="sect2"><a href="ClientConfig.html#id2545052">Joining a Domain: Windows 2000/XP Professional</a></span></dt><dt><span class="sect2"><a href="ClientConfig.html#id2545579">Domain Logon Configuration: Windows 9x/Me</a></span></dt></dl></dd><dt><span class="sect1"><a href="ClientConfig.html#id2546024">Common Errors</a></span></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2543178"></a>Features and Benefits</h2></div></div></div><p>
2 <a class="indexterm" name="id2543186"></a>
3 <a class="indexterm" name="id2543193"></a>
4 <a class="indexterm" name="id2543200"></a>
5 Occasionally network administrators report difficulty getting Microsoft Windows clients to interoperate
6 correctly with Samba servers. It seems that some folks just cannot accept the fact that the right way
7 to configure an MS Windows network client is precisely as one would do when using MS Windows NT4 or 200x
8 servers. Yet there is repetitious need to provide detailed Windows client configuration instructions.
10 <a class="indexterm" name="id2543217"></a>
11 <a class="indexterm" name="id2543225"></a>
12 The purpose of this chapter is to graphically illustrate MS Windows client configuration for the most common
13 critical aspects of such configuration. An experienced network administrator will not be interested in the
14 details of this chapter.
15 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2543238"></a>Technical Details</h2></div></div></div><p>
16 <a class="indexterm" name="id2543246"></a>
17 <a class="indexterm" name="id2543253"></a>
18 This chapter discusses TCP/IP protocol configuration as well as network membership for the platforms
19 that are in common use today. These are:
20 </p><div class="itemizedlist"><ul type="disc"><li><p>
21 Microsoft Windows XP Professional
23 Windows 2000 Professional
25 Windows Millennium edition (Me)
26 </p></li></ul></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2543282"></a>TCP/IP Configuration</h3></div></div></div><p>
27 <a class="indexterm" name="id2543290"></a>
28 <a class="indexterm" name="id2543297"></a>
29 The builder of a house must ensure that all construction takes place on a firm foundation.
30 The same is true for the builder of a TCP/IP-based networking system. Fundamental network configuration problems
31 will plague all network users until they are resolved.
33 <a class="indexterm" name="id2543312"></a>
34 <a class="indexterm" name="id2543319"></a>
35 MS Windows workstations and servers can be configured either with fixed
36 IP addresses or via DHCP. The examples that follow demonstrate the use of DHCP
37 and make only passing reference to those situations where fixed IP configuration
38 settings can be effected.
40 <a class="indexterm" name="id2543333"></a>
41 <a class="indexterm" name="id2543340"></a>
42 It is possible to use shortcuts or abbreviated keystrokes to arrive at a
43 particular configuration screen. The decision was made to base all examples in this
44 chapter on use of the <span class="guibutton">Start</span> button.
45 </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2543357"></a>MS Windows XP Professional</h4></div></div></div><p>
46 <a class="indexterm" name="id2543365"></a>
47 There are two paths to the Windows XP TCP/IP configuration panel. Choose the access method that you prefer:
49 Click <span class="guimenu">Start -> Control Panel -> Network Connections</span>.
51 <span class="emphasis"><em>Alternately,</em></span> click <span class="guimenu">Start -></span>, and right-click <span class="guimenu">My Network Places</span>
52 then select <span class="guimenuitem">Properties</span>.
54 <a class="indexterm" name="id2543414"></a>
55 The following procedure steps through the Windows XP Professional TCP/IP configuration process:
56 </p><div class="procedure"><ol type="1"><li><p>
57 <a class="indexterm" name="id2543431"></a>
58 <a class="indexterm" name="id2543438"></a>
59 <a class="indexterm" name="id2543445"></a>
60 On some installations the interface will be called <span class="guimenu">Local Area Connection</span> and
61 on others it will be called <span class="guimenu">Network Bridge</span>. On our system it is called <span class="guimenu">Network Bridge</span>.
62 Right-click on <span class="guimenu">Network Bridge -> Properties</span>. See <a href="ClientConfig.html#WXPP002" title="Figure 8.1. Network Bridge Configuration.">???</a>.
63 </p><div class="figure"><a name="WXPP002"></a><p class="title"><b>Figure 8.1. Network Bridge Configuration.</b></p><div class="mediaobject"><img src="images/WXPP002.png" alt="Network Bridge Configuration."></div></div><p>
65 <a class="indexterm" name="id2543530"></a>
66 <a class="indexterm" name="id2543537"></a>
67 The Network Bridge Configuration, or Local Area Connection, panel is used to set TCP/IP protocol settings.
68 In <span class="guimenuitem">This connection uses the following items:</span> box,
69 click on <span class="guimenu">Internet Protocol (TCP/IP)</span>, then click on <span class="guibutton">Properties</span>.
71 <a class="indexterm" name="id2543569"></a>
72 <a class="indexterm" name="id2543576"></a>
73 The default setting is DHCP-enabled operation
74 (i.e., “<span class="quote">Obtain an IP address automatically</span>”). See <a href="ClientConfig.html#WXPP003" title="Figure 8.2. Internet Protocol (TCP/IP) Properties.">???</a>.
75 </p><div class="figure"><a name="WXPP003"></a><p class="title"><b>Figure 8.2. Internet Protocol (TCP/IP) Properties.</b></p><div class="mediaobject"><img src="images/WXPP003.png" alt="Internet Protocol (TCP/IP) Properties."></div></div><p>
77 <a class="indexterm" name="id2543639"></a>
78 <a class="indexterm" name="id2543646"></a>
79 <a class="indexterm" name="id2543652"></a>
80 <a class="indexterm" name="id2543659"></a>
81 Many network administrators will want to use DHCP to configure all client TCP/IP
82 protocol stack settings. (For information on how to configure the ISC DHCP server
83 for Windows client support see <a href="DNSDHCP.html#DHCP" title="DHCP Server">the DNS and DHCP Configuration Guide</a>,
84 <a href="DNSDHCP.html#DHCP" title="DHCP Server">DHCP Server</a>.
86 <a class="indexterm" name="id2543688"></a>
87 <a class="indexterm" name="id2543695"></a>
88 <a class="indexterm" name="id2543701"></a>
89 If it is necessary to provide a fixed IP address, click on “<span class="quote">Use the following IP address</span>” and enter the
90 IP Address, the subnet mask, and the default gateway address in the boxes provided.
92 <a class="indexterm" name="id2543722"></a>
93 <a class="indexterm" name="id2543729"></a>
94 <a class="indexterm" name="id2543736"></a>
95 <a class="indexterm" name="id2543743"></a>
96 Click the <span class="guibutton">Advanced</span> button to proceed with TCP/IP configuration.
97 This opens a panel in which it is possible to create additional IP addresses for this interface.
98 The technical name for the additional addresses is <span class="emphasis"><em>IP aliases</em></span>, and additionally this
99 panel permits the setting of more default gateways (routers). In most cases where DHCP is used, it will not be
100 necessary to create additional settings. See <a href="ClientConfig.html#WXPP005" title="Figure 8.3. Advanced Network Settings">???</a> to see the appearance of this panel.
101 </p><div class="figure"><a name="WXPP005"></a><p class="title"><b>Figure 8.3. Advanced Network Settings</b></p><div class="mediaobject"><img src="images/WXPP005.png" alt="Advanced Network Settings"></div></div><p>
103 <a class="indexterm" name="id2543813"></a>
104 <a class="indexterm" name="id2543820"></a>
105 <a class="indexterm" name="id2543826"></a>
106 Fixed settings may be required for DNS and WINS if these settings are not provided automatically via DHCP.
108 <a class="indexterm" name="id2543842"></a>
109 <a class="indexterm" name="id2543849"></a>
110 Click the <span class="guimenu">DNS</span> tab to add DNS server settings.
111 The example system uses manually configured DNS settings. When finished making changes, click the
112 <span class="guibutton">OK</span> to commit the settings. See <a href="ClientConfig.html#WXPP014" title="Figure 8.4. DNS Configuration.">???</a>.
113 </p><div class="figure"><a name="WXPP014"></a><p class="title"><b>Figure 8.4. DNS Configuration.</b></p><div class="mediaobject"><img src="images/WXPP014.png" alt="DNS Configuration."></div></div><p>
115 <a class="indexterm" name="id2543924"></a>
116 <a class="indexterm" name="id2543930"></a>
117 Click the <span class="guibutton">WINS</span> tab to add manual WINS server entries.
118 This step demonstrates an example system that uses manually configured WINS settings.
119 When finished making changes, click <span class="guibutton">OK</span> to commit
120 the settings. See <a href="ClientConfig.html#WXPP009" title="Figure 8.5. WINS Configuration">???</a>.
121 </p><div class="figure"><a name="WXPP009"></a><p class="title"><b>Figure 8.5. WINS Configuration</b></p><div class="mediaobject"><img src="images/WXPP009.png" alt="WINS Configuration"></div></div><p>
122 </p></li></ol></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2544000"></a>MS Windows 2000</h4></div></div></div><p>
123 <a class="indexterm" name="id2544007"></a>
124 <a class="indexterm" name="id2544015"></a>
125 There are two paths to the Windows 2000 Professional TCP/IP configuration panel. Choose the access method that you prefer:
127 Click <span class="guimenu">Start -> Control Panel -> Network and Dial-up Connections</span>.
129 <span class="emphasis"><em>Alternatively,</em></span> click <span class="guimenu">Start</span>, then right-click <span class="guimenu">My Network Places</span>, and
130 select <span class="guimenuitem">Properties</span>.
132 <a class="indexterm" name="id2544063"></a>
133 The following procedure steps through the Windows XP Professional TCP/IP configuration process:
134 </p><div class="procedure"><ol type="1"><li><p>
135 Right-click on <span class="guimenu">Local Area Connection</span>, then click
136 <span class="guimenuitem">Properties</span>. See <a href="ClientConfig.html#w2kp001" title="Figure 8.6. Local Area Connection Properties.">???</a>.
137 </p><div class="figure"><a name="w2kp001"></a><p class="title"><b>Figure 8.6. Local Area Connection Properties.</b></p><div class="mediaobject"><img src="images/w2kp001.png" alt="Local Area Connection Properties."></div></div><p>
139 <a class="indexterm" name="id2544144"></a>
140 <a class="indexterm" name="id2544151"></a>
141 The Local Area Connection Properties is used to set TCP/IP protocol settings. Click on
142 <span class="guimenu">Internet Protocol (TCP/IP)</span> in the <span class="guimenuitem">Components checked are used by this
143 connection:</span> box, then click the <span class="guibutton">Properties</span> button.
145 <a class="indexterm" name="id2544186"></a>
146 <a class="indexterm" name="id2544193"></a>
147 The default setting is DHCP-enabled operation
148 (i.e., “<span class="quote">Obtain an IP address automatically</span>”). See <a href="ClientConfig.html#w2kp002" title="Figure 8.7. Internet Protocol (TCP/IP) Properties.">???</a>.
149 </p><div class="figure"><a name="w2kp002"></a><p class="title"><b>Figure 8.7. Internet Protocol (TCP/IP) Properties.</b></p><div class="mediaobject"><img src="images/w2kp002.png" alt="Internet Protocol (TCP/IP) Properties."></div></div><p>
151 <a class="indexterm" name="id2544252"></a>
152 <a class="indexterm" name="id2544259"></a>
153 Many network administrators will want to use DHCP to configure all client TCP/IP
154 protocol stack settings. (For information on how to configure the ISC DHCP server
155 for Windows client support, see, <a href="DNSDHCP.html#DHCP" title="DHCP Server">???</a>.
157 <a class="indexterm" name="id2544279"></a>
158 <a class="indexterm" name="id2544286"></a>
159 If it is necessary to provide a fixed IP address, click on “<span class="quote">Use the following IP address</span>” and enter the
160 IP Address, the subnet mask, and the default gateway address in the boxes provided.
161 For this example we are assuming that all network clients will be configured using DHCP.
163 Click the <span class="guimenu">Advanced</span> button to proceed with TCP/IP configuration.
164 Refer to <a href="ClientConfig.html#w2kp003" title="Figure 8.8. Advanced Network Settings.">???</a>.
165 </p><div class="figure"><a name="w2kp003"></a><p class="title"><b>Figure 8.8. Advanced Network Settings.</b></p><div class="mediaobject"><img src="images/w2kp003.png" alt="Advanced Network Settings."></div></div><p>
167 <a class="indexterm" name="id2544362"></a>
168 <a class="indexterm" name="id2544368"></a>
169 <a class="indexterm" name="id2544375"></a>
170 Fixed settings may be required for DNS and WINS if these settings are not provided automatically via DHCP.
172 <a class="indexterm" name="id2544390"></a>
173 <a class="indexterm" name="id2544397"></a>
174 Click the <span class="guimenu">DNS</span> tab to add DNS server settings.
175 The example system uses manually configured DNS settings. When finished making changes,
176 click <span class="guibutton">OK</span> to commit the settings. See <a href="ClientConfig.html#w2kp004" title="Figure 8.9. DNS Configuration.">???</a>.
177 </p><div class="figure"><a name="w2kp004"></a><p class="title"><b>Figure 8.9. DNS Configuration.</b></p><div class="mediaobject"><img src="images/w2kp004.png" alt="DNS Configuration."></div></div><p>
179 <a class="indexterm" name="id2544469"></a>
180 <a class="indexterm" name="id2544476"></a>
181 Click the <span class="guibutton">WINS</span> tab to add manual WINS server entries.
182 This step demonstrates an example system that uses manually configured WINS settings.
183 When finished making changes, click <span class="guibutton">OK</span> to commit the settings.
184 See <a href="ClientConfig.html#w2kp005" title="Figure 8.10. WINS Configuration.">???</a>.
185 </p><div class="figure"><a name="w2kp005"></a><p class="title"><b>Figure 8.10. WINS Configuration.</b></p><div class="mediaobject"><img src="images/w2kp005.png" alt="WINS Configuration."></div></div><p>
186 </p></li></ol></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2544547"></a>MS Windows Me</h4></div></div></div><p>
187 <a class="indexterm" name="id2544555"></a>
188 <a class="indexterm" name="id2544562"></a>
189 <a class="indexterm" name="id2544569"></a>
190 There are two paths to the Windows Millennium edition (Me) TCP/IP configuration panel. Choose the access method that you prefer:
192 Click <span class="guimenu">Start -> Control Panel -> Network Connections</span>.
194 <a class="indexterm" name="id2544592"></a>
195 <a class="indexterm" name="id2544599"></a>
196 <span class="emphasis"><em>Alternatively,</em></span> click on <span class="guimenu">Start -></span>, and right click on <span class="guimenu">My Network Places</span>
197 then select <span class="guimenuitem">Properties</span>.
199 <a class="indexterm" name="id2544631"></a>
200 The following procedure steps through the Windows Me TCP/IP configuration process:
201 </p><div class="procedure"><ol type="1"><li><p>
202 <a class="indexterm" name="id2544649"></a>
203 In the box labeled <span class="guimenuitem">The following network components are installed:</span>,
204 click on <span class="guimenu">Internet Protocol TCP/IP</span>, then click on the <span class="guibutton">Properties</span> button.
205 See <a href="ClientConfig.html#WME001" title="Figure 8.11. The Windows Me Network Configuration Panel.">???</a>.
206 </p><div class="figure"><a name="WME001"></a><p class="title"><b>Figure 8.11. The Windows Me Network Configuration Panel.</b></p><div class="mediaobject"><img src="images/WME001.png" alt="The Windows Me Network Configuration Panel."></div></div><p>
208 <a class="indexterm" name="id2544730"></a>
209 <a class="indexterm" name="id2544736"></a>
210 <a class="indexterm" name="id2544743"></a>
211 Many network administrators will want to use DHCP to configure all client TCP/IP
212 protocol stack settings. (For information on how to configure the ISC DHCP server
213 for Windows client support see <a href="DNSDHCP.html#DHCP" title="DHCP Server">the DNS and DHCP Configuration Guide</a>,
214 <a href="DNSDHCP.html#DHCP" title="DHCP Server">DHCP Server</a>. The default setting on Windows Me workstations is for DHCP-enabled operation
215 (i.e., <span class="guimenu">Obtain IP address automatically</span> is enabled). See <a href="ClientConfig.html#WME002" title="Figure 8.12. IP Address.">???</a>.
216 </p><div class="figure"><a name="WME002"></a><p class="title"><b>Figure 8.12. IP Address.</b></p><div class="mediaobject"><img src="images/WME002.png" alt="IP Address."></div></div><p>
218 <a class="indexterm" name="id2544822"></a>
219 <a class="indexterm" name="id2544829"></a>
220 <a class="indexterm" name="id2544836"></a>
221 If it is necessary to provide a fixed IP address, click on <span class="guimenuitem">Specify an IP address</span> and enter the
222 IP Address and the subnet mask in the boxes provided. For this example we are assuming that all
223 network clients will be configured using DHCP.
225 <a class="indexterm" name="id2544860"></a>
226 <a class="indexterm" name="id2544866"></a>
227 Fixed settings may be required for DNS and WINS if these settings are not provided automatically via DHCP.
229 <a class="indexterm" name="id2544881"></a>
230 If necessary, click the <span class="guimenu">DNS Configuration</span> tab to add DNS server settings.
231 Click the <span class="guibutton">WINS Configuration</span> tab to add WINS server settings.
232 The <span class="guimenu">Gateway</span> tab allows additional gateways (router addresses) to be added to the network
233 interface settings. In most cases where DHCP is used, it will not be necessary to
234 create these manual settings.
236 <a class="indexterm" name="id2544918"></a>
237 <a class="indexterm" name="id2544925"></a>
238 The following example uses manually configured WINS settings. See <a href="ClientConfig.html#WME005" title="Figure 8.13. DNS Configuration.">???</a>.
239 When finished making changes, click <span class="guibutton">OK</span> to commit the settings.
240 </p><div class="figure"><a name="WME005"></a><p class="title"><b>Figure 8.13. DNS Configuration.</b></p><div class="mediaobject"><img src="images/WME005.png" alt="DNS Configuration."></div></div><p>
242 <a class="indexterm" name="id2544986"></a>
243 <a class="indexterm" name="id2544993"></a>
244 This is an example of a system that uses manually configured WINS settings. One situation where
245 this might apply is on a network that has a single DHCP server that provides settings for multiple
246 Windows workgroups or domains. See <a href="ClientConfig.html#WME003" title="Figure 8.14. WINS Configuration.">???</a>.
247 </p><div class="figure"><a name="WME003"></a><p class="title"><b>Figure 8.14. WINS Configuration.</b></p><div class="mediaobject"><img src="images/WME003.png" alt="WINS Configuration."></div></div><p>
248 </p></li></ol></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2545052"></a>Joining a Domain: Windows 2000/XP Professional</h3></div></div></div><p>
249 <a class="indexterm" name="id2545061"></a>
250 <a class="indexterm" name="id2545068"></a>
251 <a class="indexterm" name="id2545075"></a>
252 <a class="indexterm" name="id2545082"></a>
253 Microsoft Windows NT/200x/XP Professional platforms can participate in domain security.
254 This section steps through the process for making a Windows 200x/XP Professional machine a
255 member of a domain security environment. It should be noted that this process is identical
256 when joining a domain that is controlled by Windows NT4/200x as well as a Samba PDC.
257 </p><div class="procedure"><ol type="1"><li><p>
258 Click <span class="guimenu">Start</span>.
260 Right-click <span class="guimenu">My Computer</span>, then select <span class="guimenuitem">Properties</span>.
262 <a class="indexterm" name="id2545135"></a>
263 The opening panel is the same one that can be reached by clicking <span class="guimenu">System</span> on the Control Panel.
264 See <a href="ClientConfig.html#wxpp001" title="Figure 8.15. The General Panel.">???</a>.
265 </p><div class="figure"><a name="wxpp001"></a><p class="title"><b>Figure 8.15. The General Panel.</b></p><div class="mediaobject"><img src="images/wxpp001.png" alt="The General Panel."></div></div><p>
267 <a class="indexterm" name="id2545201"></a>
268 Click the <span class="guimenu">Computer Name</span> tab.
269 This panel shows the <span class="guimenuitem">Computer Description</span>, the <span class="guimenuitem">Full computer name</span>,
270 and the <span class="guimenuitem">Workgroup</span> or <span class="guimenuitem">Domain name</span>.
272 <a class="indexterm" name="id2545243"></a>
273 <a class="indexterm" name="id2545250"></a>
274 Clicking the <span class="guimenu">Network ID</span> button will launch the configuration wizard. Do not use this with
275 Samba-3. If you wish to change the computer name or join or leave the domain, click the <span class="guimenu">Change</span> button.
276 See <a href="ClientConfig.html#wxpp004" title="Figure 8.16. The Computer Name Panel.">???</a>.
277 </p><div class="figure"><a name="wxpp004"></a><p class="title"><b>Figure 8.16. The Computer Name Panel.</b></p><div class="mediaobject"><img src="images/wxpp004.png" alt="The Computer Name Panel."></div></div><p>
279 Click on <span class="guimenu">Change</span>. This panel shows that our example machine (TEMPTATION) is in a workgroup called WORKGROUP.
280 We will join the domain called MIDEARTH. See <a href="ClientConfig.html#wxpp006" title="Figure 8.17. The Computer Name Changes Panel.">???</a>.
281 </p><div class="figure"><a name="wxpp006"></a><p class="title"><b>Figure 8.17. The Computer Name Changes Panel.</b></p><div class="mediaobject"><img src="images/wxpp006.png" alt="The Computer Name Changes Panel."></div></div><p>
283 <a class="indexterm" name="id2545381"></a>
284 Enter the name <span class="guimenu">MIDEARTH</span> in the field below the domain radio button.
286 This panel shows that our example machine (TEMPTATION) is set to join the domain called MIDEARTH. See <a href="ClientConfig.html#wxpp007" title="Figure 8.18. The Computer Name Changes Panel Domain MIDEARTH.">???</a>.
287 </p><div class="figure"><a name="wxpp007"></a><p class="title"><b>Figure 8.18. The Computer Name Changes Panel Domain MIDEARTH.</b></p><div class="mediaobject"><img src="images/wxpp007.png" alt="The Computer Name Changes Panel Domain MIDEARTH."></div></div><p>
289 <a class="indexterm" name="id2545453"></a>
290 <a class="indexterm" name="id2545460"></a>
291 Now click the <span class="guimenu">OK</span> button. A dialog box should appear to allow you to provide the
292 credentials (username and password) of a domain administrative account that has the rights to add machines to
295 <a class="indexterm" name="id2545480"></a>
296 Enter the name “<span class="quote">root</span>” and the root password from your Samba-3 server. See <a href="ClientConfig.html#wxpp008" title="Figure 8.19. Computer Name Changes Username and Password Panel.">???</a>.
297 </p><div class="figure"><a name="wxpp008"></a><p class="title"><b>Figure 8.19. Computer Name Changes Username and Password Panel.</b></p><div class="mediaobject"><img src="images/wxpp008.png" alt="Computer Name Changes Username and Password Panel."></div></div><p>
299 Click on <span class="guimenu">OK</span>.
301 <a class="indexterm" name="id2545556"></a>
302 <a class="indexterm" name="id2545563"></a>
303 The “<span class="quote">Welcome to the MIDEARTH domain.</span>” dialog box should appear. At this point the machine must be rebooted.
304 Joining the domain is now complete.
305 </p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2545579"></a>Domain Logon Configuration: Windows 9x/Me</h3></div></div></div><p>
306 <a class="indexterm" name="id2545588"></a>
307 <a class="indexterm" name="id2545594"></a>
308 <a class="indexterm" name="id2545601"></a>
309 We follow the convention used by most in saying that Windows 9x/Me machines can participate in domain logons. The truth is
310 that these platforms can use only the LanManager network logon protocols.
311 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
312 <a class="indexterm" name="id2545616"></a>
313 <a class="indexterm" name="id2545623"></a>
314 <a class="indexterm" name="id2545630"></a>
315 Windows XP Home edition cannot participate in domain or LanManager network logons.
316 </p></div><div class="procedure"><ol type="1"><li><p>
317 Right-click on the <span class="guimenu">Network Neighborhood</span> icon.
319 The Network Configuration Panel allows all common network settings to be changed.
320 See <a href="ClientConfig.html#WME009" title="Figure 8.20. The Network Panel.">???</a>.
321 </p><div class="figure"><a name="WME009"></a><p class="title"><b>Figure 8.20. The Network Panel.</b></p><div class="mediaobject"><img src="images/WME009.png" alt="The Network Panel."></div></div><p>
323 <a class="indexterm" name="id2545709"></a>
324 <a class="indexterm" name="id2545716"></a>
325 Make sure that the <span class="guimenu">Client for Microsoft Networks</span> driver is installed as shown.
326 Click on the <span class="guimenu">Client for Microsoft Networks</span> entry in <span class="guimenu">The following network
327 components are installed:</span> box. Then click the <span class="guibutton">Properties</span> button.
329 <a class="indexterm" name="id2545756"></a>
330 <a class="indexterm" name="id2545763"></a>
331 The Client for Microsoft Networks Properties panel is the correct location to configure network logon
332 settings. See <a href="ClientConfig.html#WME010" title="Figure 8.21. Client for Microsoft Networks Properties Panel.">???</a>.
333 </p><div class="figure"><a name="WME010"></a><p class="title"><b>Figure 8.21. Client for Microsoft Networks Properties Panel.</b></p><div class="mediaobject"><img src="images/WME010.png" alt="Client for Microsoft Networks Properties Panel."></div></div><p>
335 <a class="indexterm" name="id2545820"></a>
336 <a class="indexterm" name="id2545827"></a>
337 Enter the Windows NT domain name, check the <span class="guimenu">Log on to Windows NT domain</span> box,
338 and click <span class="guimenu">OK</span>.
340 <a class="indexterm" name="id2545853"></a>
341 <a class="indexterm" name="id2545860"></a>
342 <a class="indexterm" name="id2545867"></a>
343 Click on the <span class="guimenu">Identification</span> button. This is the location at which the workgroup
344 (domain) name and the machine name (computer name) need to be set. See <a href="ClientConfig.html#WME013" title="Figure 8.22. Identification Panel.">???</a>.
345 </p><div class="figure"><a name="WME013"></a><p class="title"><b>Figure 8.22. Identification Panel.</b></p><div class="mediaobject"><img src="images/WME013.png" alt="Identification Panel."></div></div><p>
347 <a class="indexterm" name="id2545932"></a>
348 <a class="indexterm" name="id2545939"></a>
349 <a class="indexterm" name="id2545946"></a>
350 <a class="indexterm" name="id2545953"></a>
351 Now click the <span class="guimenu">Access Control</span> button. If you want to be able to assign share access
352 permissions using domain user and group accounts, it is necessary to enable
353 <span class="guimenu">User-level access control</span> as shown in this panel. See <a href="ClientConfig.html#WME014" title="Figure 8.23. Access Control Panel.">???</a>.
354 </p><div class="figure"><a name="WME014"></a><p class="title"><b>Figure 8.23. Access Control Panel.</b></p><div class="mediaobject"><img src="images/WME014.png" alt="Access Control Panel."></div></div><p>
355 </p></li></ol></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2546024"></a>Common Errors</h2></div></div></div><p>
356 <a class="indexterm" name="id2546031"></a>
357 <a class="indexterm" name="id2546038"></a>
358 The most common errors that can afflict Windows networking systems include:
359 </p><div class="itemizedlist"><ul type="disc"><li><p>Incorrect IP address.</p></li><li><p>Incorrect or inconsistent netmasks.</p></li><li><p>Incorrect router address.</p></li><li><p>Incorrect DNS server address.</p></li><li><p>Incorrect WINS server address.</p></li><li><p>Use of a Network Scope setting watch out for this one!</p></li></ul></div><p>
360 <a class="indexterm" name="id2546086"></a>
361 <a class="indexterm" name="id2546093"></a>
362 The most common reasons for which a Windows NT/200x/XP Professional client cannot join the Samba controlled domain are:
363 </p><div class="itemizedlist"><ul type="disc"><li><p><code class="filename">smb.conf</code> does not have correct <a class="indexterm" name="id2546114"></a>add machine script settings.</p></li><li><p>“<span class="quote">root</span>” account is not in password backend database.</p></li><li><p>Attempt to use a user account instead of the “<span class="quote">root</span>” account to join a machine to the domain.</p></li><li><p>Open connections from the workstation to the server.</p></li><li><p>Firewall or filter configurations in place on either the client or the Samba server.</p></li></ul></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="StandAloneServer.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="type.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="optional.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 7. Standalone Servers </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Part III. Advanced Configuration</td></tr></table></div></body></html>
projects / samba / blob