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">
|
---|
4 | <chapterinfo>
|
---|
5 | &author.jht;
|
---|
6 | </chapterinfo>
|
---|
7 |
|
---|
8 | <title>MS Windows Network Configuration Guide</title>
|
---|
9 |
|
---|
10 | <sect1>
|
---|
11 | <title>Features and Benefits</title>
|
---|
12 |
|
---|
13 | <para>
|
---|
14 | <indexterm><primary>network difficulty</primary></indexterm>
|
---|
15 | <indexterm><primary>network client</primary></indexterm>
|
---|
16 | <indexterm><primary>client instructions</primary></indexterm>
|
---|
17 | Occasionally network administrators report difficulty getting Microsoft Windows clients to interoperate
|
---|
18 | correctly with Samba servers. It seems that some folks just cannot accept the fact that the right way
|
---|
19 | to configure an MS Windows network client is precisely as one would do when using MS Windows NT4 or 200x
|
---|
20 | servers. Yet there is repetitious need to provide detailed Windows client configuration instructions.
|
---|
21 | </para>
|
---|
22 |
|
---|
23 | <para>
|
---|
24 | <indexterm><primary>graphically illustrated client configuration</primary></indexterm>
|
---|
25 | <indexterm><primary>critical aspects of configuration</primary></indexterm>
|
---|
26 | The purpose of this chapter is to graphically illustrate MS Windows client configuration for the most common
|
---|
27 | critical aspects of such configuration. An experienced network administrator will not be interested in the
|
---|
28 | details of this chapter.
|
---|
29 | </para>
|
---|
30 |
|
---|
31 | </sect1>
|
---|
32 |
|
---|
33 | <sect1>
|
---|
34 | <title>Technical Details</title>
|
---|
35 |
|
---|
36 | <para>
|
---|
37 | <indexterm><primary>TCP/IP protocol configuration</primary></indexterm>
|
---|
38 | <indexterm><primary>network membership</primary></indexterm>
|
---|
39 | This chapter discusses TCP/IP protocol configuration as well as network membership for the platforms
|
---|
40 | that are in common use today. These are:
|
---|
41 | </para>
|
---|
42 |
|
---|
43 | <itemizedlist>
|
---|
44 | <listitem><para>
|
---|
45 | Microsoft Windows XP Professional
|
---|
46 | </para></listitem>
|
---|
47 | <listitem><para>
|
---|
48 | Windows 2000 Professional
|
---|
49 | </para></listitem>
|
---|
50 | <listitem><para>
|
---|
51 | Windows Millennium edition (Me)
|
---|
52 | </para></listitem>
|
---|
53 | </itemizedlist>
|
---|
54 |
|
---|
55 | <sect2>
|
---|
56 | <title>TCP/IP Configuration</title>
|
---|
57 |
|
---|
58 | <para>
|
---|
59 | <indexterm><primary>network configuration problems</primary></indexterm>
|
---|
60 | <indexterm><primary>plague network users</primary></indexterm>
|
---|
61 | The builder of a house must ensure that all construction takes place on a firm foundation.
|
---|
62 | The same is true for the builder of a TCP/IP-based networking system. Fundamental network configuration problems
|
---|
63 | will plague all network users until they are resolved.
|
---|
64 | </para>
|
---|
65 |
|
---|
66 | <para>
|
---|
67 | <indexterm><primary>fixed IP addresses</primary></indexterm>
|
---|
68 | <indexterm><primary>DHCP</primary></indexterm>
|
---|
69 | MS Windows workstations and servers can be configured either with fixed
|
---|
70 | IP addresses or via DHCP. The examples that follow demonstrate the use of DHCP
|
---|
71 | and make only passing reference to those situations where fixed IP configuration
|
---|
72 | settings can be effected.
|
---|
73 | </para>
|
---|
74 |
|
---|
75 | <para>
|
---|
76 | <indexterm><primary>shortcuts</primary></indexterm>
|
---|
77 | <indexterm><primary>abbreviated keystrokes</primary></indexterm>
|
---|
78 | It is possible to use shortcuts or abbreviated keystrokes to arrive at a
|
---|
79 | particular configuration screen. The decision was made to base all examples in this
|
---|
80 | chapter on use of the <guibutton>Start</guibutton> button.
|
---|
81 | </para>
|
---|
82 |
|
---|
83 | <sect3>
|
---|
84 | <title>MS Windows XP Professional</title>
|
---|
85 |
|
---|
86 | <para>
|
---|
87 | <indexterm><primary>Windows XP TCP/IP</primary></indexterm>
|
---|
88 | There are two paths to the Windows XP TCP/IP configuration panel. Choose the access method that you prefer:
|
---|
89 | </para>
|
---|
90 |
|
---|
91 | <para>
|
---|
92 | Click <guimenu>Start -> Control Panel -> Network Connections</guimenu>.
|
---|
93 | </para>
|
---|
94 |
|
---|
95 | <para>
|
---|
96 | <emphasis>Alternately,</emphasis> click <guimenu>Start -></guimenu>, and right-click <guimenu>My Network Places</guimenu>
|
---|
97 | then select <guimenuitem>Properties</guimenuitem>.
|
---|
98 | </para>
|
---|
99 |
|
---|
100 | <para>
|
---|
101 | <indexterm><primary>Windows XP Professional</primary></indexterm>
|
---|
102 | The following procedure steps through the Windows XP Professional TCP/IP configuration process:
|
---|
103 | </para>
|
---|
104 |
|
---|
105 | <procedure>
|
---|
106 | <step><para>
|
---|
107 | <indexterm><primary>Local Area Connection</primary></indexterm>
|
---|
108 | <indexterm><primary>Network Bridge</primary></indexterm>
|
---|
109 | <indexterm><primary>interface</primary></indexterm>
|
---|
110 | On some installations the interface will be called <guimenu>Local Area Connection</guimenu> and
|
---|
111 | on others it will be called <guimenu>Network Bridge</guimenu>. On our system it is called <guimenu>Network Bridge</guimenu>.
|
---|
112 | Right-click on <guimenu>Network Bridge -> Properties</guimenu>. See <link linkend="WXPP002"/>.
|
---|
113 | <figure id="WXPP002"><title>Network Bridge Configuration.</title><imagefile>WXPP002</imagefile></figure>
|
---|
114 | </para>
|
---|
115 | </step>
|
---|
116 |
|
---|
117 | <step><para>
|
---|
118 | <indexterm><primary>TCP/IP protocol settings</primary></indexterm>
|
---|
119 | <indexterm><primary>Network Bridge Configuration</primary></indexterm>
|
---|
120 | The Network Bridge Configuration, or Local Area Connection, panel is used to set TCP/IP protocol settings.
|
---|
121 | In <guimenuitem>This connection uses the following items:</guimenuitem> box,
|
---|
122 | click on <guimenu>Internet Protocol (TCP/IP)</guimenu>, then click on <guibutton>Properties</guibutton>.
|
---|
123 | </para>
|
---|
124 |
|
---|
125 | <para>
|
---|
126 | <indexterm><primary>DHCP-enabled operation</primary></indexterm>
|
---|
127 | <indexterm><primary>IP address automatically</primary></indexterm>
|
---|
128 | The default setting is DHCP-enabled operation
|
---|
129 | (i.e., <quote>Obtain an IP address automatically</quote>). See <link linkend="WXPP003"/>.
|
---|
130 | <figure id="WXPP003">
|
---|
131 | <title>Internet Protocol (TCP/IP) Properties.</title>
|
---|
132 | <imagefile>WXPP003</imagefile>
|
---|
133 | </figure>
|
---|
134 | </para>
|
---|
135 |
|
---|
136 | <para>
|
---|
137 | <indexterm><primary>DHCP</primary></indexterm>
|
---|
138 | <indexterm><primary>TCP/IP</primary></indexterm>
|
---|
139 | <indexterm><primary>DNS</primary></indexterm>
|
---|
140 | <indexterm><primary>ISC DHCP server</primary></indexterm>
|
---|
141 | Many network administrators will want to use DHCP to configure all client TCP/IP
|
---|
142 | protocol stack settings. (For information on how to configure the ISC DHCP server
|
---|
143 | for Windows client support see <link linkend="DHCP">the DNS and DHCP Configuration Guide</link>,
|
---|
144 | <link linkend="DHCP">DHCP Server</link>).
|
---|
145 | </para>
|
---|
146 |
|
---|
147 | <para>
|
---|
148 | <indexterm><primary>fixed IP address</primary></indexterm>
|
---|
149 | <indexterm><primary>subnet mask</primary></indexterm>
|
---|
150 | <indexterm><primary>gateway address</primary></indexterm>
|
---|
151 | If it is necessary to provide a fixed IP address, click on <quote>Use the following IP address</quote> and enter the
|
---|
152 | IP Address, the subnet mask, and the default gateway address in the boxes provided.
|
---|
153 | </para></step>
|
---|
154 |
|
---|
155 | <step><para>
|
---|
156 | <indexterm><primary>Advanced TCP/IP configuration</primary></indexterm>
|
---|
157 | <indexterm><primary>TCP/IP configuration</primary></indexterm>
|
---|
158 | <indexterm><primary>IP aliases</primary></indexterm>
|
---|
159 | <indexterm><primary>default gateways</primary></indexterm>
|
---|
160 | Click the <guibutton>Advanced</guibutton> button to proceed with TCP/IP configuration.
|
---|
161 | This opens a panel in which it is possible to create additional IP addresses for this interface.
|
---|
162 | The technical name for the additional addresses is <emphasis>IP aliases</emphasis>, and additionally this
|
---|
163 | panel permits the setting of more default gateways (routers). In most cases where DHCP is used, it will not be
|
---|
164 | necessary to create additional settings. See <link linkend="WXPP005"></link> to see the appearance of this panel.
|
---|
165 | <figure id="WXPP005"><title>Advanced Network Settings</title><imagefile>WXPP005</imagefile></figure>
|
---|
166 | </para>
|
---|
167 |
|
---|
168 | <para>
|
---|
169 | <indexterm><primary>DNS</primary></indexterm>
|
---|
170 | <indexterm><primary>WINS</primary></indexterm>
|
---|
171 | <indexterm><primary>DHCP</primary></indexterm>
|
---|
172 | Fixed settings may be required for DNS and WINS if these settings are not provided automatically via DHCP.
|
---|
173 | </para></step>
|
---|
174 |
|
---|
175 | <step><para>
|
---|
176 | <indexterm><primary>DNS server settings</primary></indexterm>
|
---|
177 | <indexterm><primary>manually configured DNS settings</primary></indexterm>
|
---|
178 | Click the <guimenu>DNS</guimenu> tab to add DNS server settings.
|
---|
179 | The example system uses manually configured DNS settings. When finished making changes, click the
|
---|
180 | <guibutton>OK</guibutton> to commit the settings. See <link linkend="WXPP014"/>.
|
---|
181 | <figure id="WXPP014"> <title>DNS Configuration.</title> <imagefile>WXPP014</imagefile> </figure>
|
---|
182 | </para></step>
|
---|
183 |
|
---|
184 | <step><para>
|
---|
185 | <indexterm><primary>WINS</primary></indexterm>
|
---|
186 | <indexterm><primary>manual WINS server entries</primary></indexterm>
|
---|
187 | Click the <guibutton>WINS</guibutton> tab to add manual WINS server entries.
|
---|
188 | This step demonstrates an example system that uses manually configured WINS settings.
|
---|
189 | When finished making changes, click <guibutton>OK</guibutton> to commit
|
---|
190 | the settings. See <link linkend="WXPP009"></link>.
|
---|
191 | <figure id="WXPP009"><title>WINS Configuration</title><imagefile>WXPP009</imagefile></figure>
|
---|
192 | </para></step>
|
---|
193 | </procedure>
|
---|
194 |
|
---|
195 | </sect3>
|
---|
196 |
|
---|
197 | <sect3>
|
---|
198 | <title>MS Windows 2000</title>
|
---|
199 |
|
---|
200 | <para>
|
---|
201 | <indexterm><primary>Windows 2000 Professional TCP/IP</primary></indexterm>
|
---|
202 | <indexterm><primary>TCP/IP configuration panel</primary></indexterm>
|
---|
203 | There are two paths to the Windows 2000 Professional TCP/IP configuration panel. Choose the access method that you prefer:
|
---|
204 | </para>
|
---|
205 |
|
---|
206 | <para>
|
---|
207 | Click <guimenu>Start -> Control Panel -> Network and Dial-up Connections</guimenu>.
|
---|
208 | </para>
|
---|
209 |
|
---|
210 | <para>
|
---|
211 | <emphasis>Alternatively,</emphasis> click <guimenu>Start</guimenu>, then right-click <guimenu>My Network Places</guimenu>, and
|
---|
212 | select <guimenuitem>Properties</guimenuitem>.
|
---|
213 | </para>
|
---|
214 |
|
---|
215 | <para>
|
---|
216 | <indexterm><primary>Windows XP Professional TCP/IP</primary></indexterm>
|
---|
217 | The following procedure steps through the Windows XP Professional TCP/IP configuration process:
|
---|
218 | </para>
|
---|
219 |
|
---|
220 | <procedure>
|
---|
221 | <step><para>
|
---|
222 | Right-click on <guimenu>Local Area Connection</guimenu>, then click
|
---|
223 | <guimenuitem>Properties</guimenuitem>. See <link linkend="w2kp001"></link>.
|
---|
224 | <figure id="w2kp001"><title>Local Area Connection Properties.</title><imagefile>w2kp001</imagefile></figure>
|
---|
225 | </para></step>
|
---|
226 |
|
---|
227 | <step><para>
|
---|
228 | <indexterm><primary>Local Area Connection Properties</primary></indexterm>
|
---|
229 | <indexterm><primary>TCP/IP protocol settings</primary></indexterm>
|
---|
230 | The Local Area Connection Properties is used to set TCP/IP protocol settings. Click on
|
---|
231 | <guimenu>Internet Protocol (TCP/IP)</guimenu> in the <guimenuitem>Components checked are used by this
|
---|
232 | connection:</guimenuitem> box, then click the <guibutton>Properties</guibutton> button.
|
---|
233 | </para></step>
|
---|
234 |
|
---|
235 | <step><para>
|
---|
236 | <indexterm><primary>DHCP-enabled</primary></indexterm>
|
---|
237 | <indexterm><primary>IP address automatically</primary></indexterm>
|
---|
238 | The default setting is DHCP-enabled operation
|
---|
239 | (i.e., <quote>Obtain an IP address automatically</quote>). See <link linkend="w2kp002"/>.
|
---|
240 | <figure id="w2kp002"><title>Internet Protocol (TCP/IP) Properties.</title><imagefile>w2kp002</imagefile></figure>
|
---|
241 | </para>
|
---|
242 |
|
---|
243 | <para>
|
---|
244 | <indexterm><primary>DHCP</primary></indexterm>
|
---|
245 | <indexterm><primary>protocol stack settings</primary></indexterm>
|
---|
246 | Many network administrators will want to use DHCP to configure all client TCP/IP
|
---|
247 | protocol stack settings. (For information on how to configure the ISC DHCP server
|
---|
248 | for Windows client support, see, <link linkend="DHCP"></link>).
|
---|
249 | </para>
|
---|
250 |
|
---|
251 | <para>
|
---|
252 | <indexterm><primary>fixed IP address</primary></indexterm>
|
---|
253 | <indexterm><primary>network clients</primary></indexterm>
|
---|
254 | If it is necessary to provide a fixed IP address, click on <quote>Use the following IP address</quote> and enter the
|
---|
255 | IP Address, the subnet mask, and the default gateway address in the boxes provided.
|
---|
256 | For this example we are assuming that all network clients will be configured using DHCP.
|
---|
257 | </para></step>
|
---|
258 |
|
---|
259 | <step><para>
|
---|
260 | Click the <guimenu>Advanced</guimenu> button to proceed with TCP/IP configuration.
|
---|
261 | Refer to <link linkend="w2kp003"></link>.
|
---|
262 | <figure id="w2kp003"><title>Advanced Network Settings.</title><imagefile>w2kp003</imagefile></figure>
|
---|
263 | </para>
|
---|
264 |
|
---|
265 | <para>
|
---|
266 | <indexterm><primary>DNS</primary></indexterm>
|
---|
267 | <indexterm><primary>WINS</primary></indexterm>
|
---|
268 | <indexterm><primary>DHCP</primary></indexterm>
|
---|
269 | Fixed settings may be required for DNS and WINS if these settings are not provided automatically via DHCP.
|
---|
270 | </para></step>
|
---|
271 |
|
---|
272 | <step><para>
|
---|
273 | <indexterm><primary>DNS server settings</primary></indexterm>
|
---|
274 | <indexterm><primary>commit the settings</primary></indexterm>
|
---|
275 | Click the <guimenu>DNS</guimenu> tab to add DNS server settings.
|
---|
276 | The example system uses manually configured DNS settings. When finished making changes,
|
---|
277 | click <guibutton>OK</guibutton> to commit the settings. See <link linkend="w2kp004"></link>.
|
---|
278 | <figure id="w2kp004"><title>DNS Configuration.</title><imagefile>w2kp004</imagefile></figure>
|
---|
279 | </para></step>
|
---|
280 |
|
---|
281 | <step><para>
|
---|
282 | <indexterm><primary>manual WINS server entries</primary></indexterm>
|
---|
283 | <indexterm><primary>WINS</primary></indexterm>
|
---|
284 | Click the <guibutton>WINS</guibutton> tab to add manual WINS server entries.
|
---|
285 | This step demonstrates an example system that uses manually configured WINS settings.
|
---|
286 | When finished making changes, click <guibutton>OK</guibutton> to commit the settings.
|
---|
287 | See <link linkend="w2kp005"></link>.
|
---|
288 | <figure id="w2kp005">
|
---|
289 | <title>WINS Configuration.</title><imagefile>w2kp005</imagefile>
|
---|
290 | </figure>
|
---|
291 | </para></step>
|
---|
292 |
|
---|
293 | </procedure>
|
---|
294 |
|
---|
295 | </sect3>
|
---|
296 |
|
---|
297 | <sect3>
|
---|
298 | <title>MS Windows Me</title>
|
---|
299 |
|
---|
300 | <para>
|
---|
301 | <indexterm><primary>Windows Millennium edition (Me) TCP/IP</primary></indexterm>
|
---|
302 | <indexterm><primary>Windows Millennium</primary></indexterm>
|
---|
303 | <indexterm><primary>TCP/IP configuration</primary></indexterm>
|
---|
304 | There are two paths to the Windows Millennium edition (Me) TCP/IP configuration panel. Choose the access method that you prefer:
|
---|
305 | </para>
|
---|
306 |
|
---|
307 | <para>
|
---|
308 | Click <guimenu>Start -> Control Panel -> Network Connections</guimenu>.
|
---|
309 | </para>
|
---|
310 |
|
---|
311 | <para>
|
---|
312 | <indexterm><primary>My Network Places</primary></indexterm>
|
---|
313 | <indexterm><primary>Properties</primary></indexterm>
|
---|
314 | <emphasis>Alternatively,</emphasis> click on <guimenu>Start -></guimenu>, and right click on <guimenu>My Network Places</guimenu>
|
---|
315 | then select <guimenuitem>Properties</guimenuitem>.
|
---|
316 | </para>
|
---|
317 |
|
---|
318 | <para>
|
---|
319 | <indexterm><primary>Windows Me TCP/IP</primary></indexterm>
|
---|
320 | The following procedure steps through the Windows Me TCP/IP configuration process:
|
---|
321 | </para>
|
---|
322 |
|
---|
323 | <procedure>
|
---|
324 | <step><para>
|
---|
325 | <indexterm><primary>Internet Protocol TCP/IP</primary></indexterm>
|
---|
326 | In the box labeled <guimenuitem>The following network components are installed:</guimenuitem>,
|
---|
327 | click on <guimenu>Internet Protocol TCP/IP</guimenu>, then click on the <guibutton>Properties</guibutton> button.
|
---|
328 | See <link linkend="WME001"></link>.
|
---|
329 | <figure id="WME001">
|
---|
330 | <title>The Windows Me Network Configuration Panel.</title>
|
---|
331 | <imagefile>WME001</imagefile>
|
---|
332 | </figure>
|
---|
333 | </para></step>
|
---|
334 |
|
---|
335 | <step><para>
|
---|
336 | <indexterm><primary>DHCP</primary></indexterm>
|
---|
337 | <indexterm><primary>TCP/IP</primary></indexterm>
|
---|
338 | <indexterm><primary>ISC DHCP server</primary></indexterm>
|
---|
339 | Many network administrators will want to use DHCP to configure all client TCP/IP
|
---|
340 | protocol stack settings. (For information on how to configure the ISC DHCP server
|
---|
341 | for Windows client support see <link linkend="DHCP">the DNS and DHCP Configuration Guide</link>,
|
---|
342 | <link linkend="DHCP">DHCP Server</link>). The default setting on Windows Me workstations is for DHCP-enabled operation
|
---|
343 | (i.e., <guimenu>Obtain IP address automatically</guimenu> is enabled). See <link linkend="WME002"></link>.
|
---|
344 | <figure id="WME002"><title>IP Address.</title><imagefile>WME002</imagefile></figure>
|
---|
345 | </para>
|
---|
346 |
|
---|
347 | <para>
|
---|
348 | <indexterm><primary>Specify an IP address</primary></indexterm>
|
---|
349 | <indexterm><primary>subnet mask</primary></indexterm>
|
---|
350 | <indexterm><primary>DHCP</primary></indexterm>
|
---|
351 | If it is necessary to provide a fixed IP address, click on <guimenuitem>Specify an IP address</guimenuitem> and enter the
|
---|
352 | IP Address and the subnet mask in the boxes provided. For this example we are assuming that all
|
---|
353 | network clients will be configured using DHCP.
|
---|
354 | </para></step>
|
---|
355 |
|
---|
356 | <step><para>
|
---|
357 | <indexterm><primary>DNS</primary></indexterm>
|
---|
358 | <indexterm><primary>WINS</primary></indexterm>
|
---|
359 | Fixed settings may be required for DNS and WINS if these settings are not provided automatically via DHCP.
|
---|
360 | </para></step>
|
---|
361 |
|
---|
362 | <step><para>
|
---|
363 | <indexterm><primary>WINS server settings</primary></indexterm>
|
---|
364 | If necessary, click the <guimenu>DNS Configuration</guimenu> tab to add DNS server settings.
|
---|
365 | Click the <guibutton>WINS Configuration</guibutton> tab to add WINS server settings.
|
---|
366 | The <guimenu>Gateway</guimenu> tab allows additional gateways (router addresses) to be added to the network
|
---|
367 | interface settings. In most cases where DHCP is used, it will not be necessary to
|
---|
368 | create these manual settings.
|
---|
369 | </para></step>
|
---|
370 |
|
---|
371 | <step><para>
|
---|
372 | <indexterm><primary>WINS</primary></indexterm>
|
---|
373 | <indexterm><primary>manually configured</primary></indexterm>
|
---|
374 | The following example uses manually configured WINS settings. See <link linkend="WME005"></link>.
|
---|
375 | When finished making changes, click <guibutton>OK</guibutton> to commit the settings.
|
---|
376 | <figure id="WME005"><title>DNS Configuration.</title><imagefile>WME005</imagefile></figure>
|
---|
377 | </para>
|
---|
378 |
|
---|
379 | <para>
|
---|
380 | <indexterm><primary>single DHCP server</primary></indexterm>
|
---|
381 | <indexterm><primary>multiple Windows workgroups or domains</primary></indexterm>
|
---|
382 | This is an example of a system that uses manually configured WINS settings. One situation where
|
---|
383 | this might apply is on a network that has a single DHCP server that provides settings for multiple
|
---|
384 | Windows workgroups or domains. See <link linkend="WME003"></link>.
|
---|
385 | <figure id="WME003"><title>WINS Configuration.</title><imagefile>WME003</imagefile></figure>
|
---|
386 | </para></step>
|
---|
387 | </procedure>
|
---|
388 |
|
---|
389 |
|
---|
390 | </sect3>
|
---|
391 |
|
---|
392 | </sect2>
|
---|
393 |
|
---|
394 | <sect2>
|
---|
395 | <title>Joining a Domain: Windows 2000/XP Professional</title>
|
---|
396 |
|
---|
397 | <para>
|
---|
398 | <indexterm><primary>Windows NT/200x/XP Professional</primary></indexterm>
|
---|
399 | <indexterm><primary>domain security</primary></indexterm>
|
---|
400 | <indexterm><primary>domain member</primary></indexterm>
|
---|
401 | <indexterm><primary>domain joining</primary></indexterm>
|
---|
402 | Microsoft Windows NT/200x/XP Professional platforms can participate in domain security.
|
---|
403 | This section steps through the process for making a Windows 200x/XP Professional machine a
|
---|
404 | member of a domain security environment. It should be noted that this process is identical
|
---|
405 | when joining a domain that is controlled by Windows NT4/200x as well as a Samba PDC.
|
---|
406 | </para>
|
---|
407 |
|
---|
408 | <procedure>
|
---|
409 | <step><para>
|
---|
410 | Click <guimenu>Start</guimenu>.
|
---|
411 | </para></step>
|
---|
412 |
|
---|
413 | <step><para>
|
---|
414 | Right-click <guimenu>My Computer</guimenu>, then select <guimenuitem>Properties</guimenuitem>.
|
---|
415 | </para></step>
|
---|
416 |
|
---|
417 | <step><para>
|
---|
418 | <indexterm><primary>Control Panel</primary></indexterm>
|
---|
419 | The opening panel is the same one that can be reached by clicking <guimenu>System</guimenu> on the Control Panel.
|
---|
420 | See <link linkend="wxpp001"></link>.
|
---|
421 | <figure id="wxpp001"><title>The General Panel.</title><imagefile>wxpp001</imagefile></figure>
|
---|
422 | </para></step>
|
---|
423 |
|
---|
424 | <step><para>
|
---|
425 | <indexterm><primary>Computer Name</primary></indexterm>
|
---|
426 | Click the <guimenu>Computer Name</guimenu> tab.
|
---|
427 | This panel shows the <guimenuitem>Computer Description</guimenuitem>, the <guimenuitem>Full computer name</guimenuitem>,
|
---|
428 | and the <guimenuitem>Workgroup</guimenuitem> or <guimenuitem>Domain name</guimenuitem>.
|
---|
429 | </para>
|
---|
430 |
|
---|
431 | <para>
|
---|
432 | <indexterm><primary>Network ID</primary></indexterm>
|
---|
433 | <indexterm><primary>configuration wizard</primary></indexterm>
|
---|
434 | Clicking the <guimenu>Network ID</guimenu> button will launch the configuration wizard. Do not use this with
|
---|
435 | Samba-3. If you wish to change the computer name or join or leave the domain, click the <guimenu>Change</guimenu> button.
|
---|
436 | See <link linkend="wxpp004"></link>.
|
---|
437 | <figure id="wxpp004"><title>The Computer Name Panel.</title><imagefile>wxpp004</imagefile></figure>
|
---|
438 | </para></step>
|
---|
439 |
|
---|
440 | <step><para>
|
---|
441 | Click on <guimenu>Change</guimenu>. This panel shows that our example machine (TEMPTATION) is in a workgroup called WORKGROUP.
|
---|
442 | We will join the domain called MIDEARTH. See <link linkend="wxpp006"></link>.
|
---|
443 | <figure id="wxpp006"><title>The Computer Name Changes Panel.</title><imagefile>wxpp006</imagefile></figure>
|
---|
444 | </para></step>
|
---|
445 |
|
---|
446 | <step><para>
|
---|
447 | <indexterm><primary>domain radio button</primary></indexterm>
|
---|
448 | Enter the name <guimenu>MIDEARTH</guimenu> in the field below the domain radio button.
|
---|
449 | </para>
|
---|
450 |
|
---|
451 | <para>
|
---|
452 | This panel shows that our example machine (TEMPTATION) is set to join the domain called MIDEARTH. See <link linkend="wxpp007"></link>.
|
---|
453 | <figure id="wxpp007"><title>The Computer Name Changes Panel &smbmdash; Domain MIDEARTH.</title><imagefile>wxpp007</imagefile></figure>
|
---|
454 | </para></step>
|
---|
455 |
|
---|
456 | <step><para>
|
---|
457 | <indexterm><primary>credentials</primary></indexterm>
|
---|
458 | <indexterm><primary>username and password</primary></indexterm>
|
---|
459 | Now click the <guimenu>OK</guimenu> button. A dialog box should appear to allow you to provide the
|
---|
460 | credentials (username and password) of a domain administrative account that has the rights to add machines to
|
---|
461 | the domain.
|
---|
462 | </para>
|
---|
463 |
|
---|
464 | <para>
|
---|
465 | <indexterm><primary>root</primary></indexterm>
|
---|
466 | Enter the name <quote>root</quote> and the root password from your Samba-3 server. See <link linkend="wxpp008"></link>.
|
---|
467 | <figure id="wxpp008">
|
---|
468 | <title>Computer Name Changes &smbmdash; Username and Password Panel.</title><imagefile>wxpp008</imagefile>
|
---|
469 | </figure>
|
---|
470 | </para></step>
|
---|
471 |
|
---|
472 | <step><para>
|
---|
473 | Click on <guimenu>OK</guimenu>.
|
---|
474 | </para>
|
---|
475 |
|
---|
476 | <para>
|
---|
477 | <indexterm><primary>Welcome</primary></indexterm>
|
---|
478 | <indexterm><primary>rebooted</primary></indexterm>
|
---|
479 | The <quote>Welcome to the MIDEARTH domain.</quote> dialog box should appear. At this point the machine must be rebooted.
|
---|
480 | Joining the domain is now complete.
|
---|
481 | </para></step>
|
---|
482 |
|
---|
483 | </procedure>
|
---|
484 |
|
---|
485 | </sect2>
|
---|
486 |
|
---|
487 | <sect2>
|
---|
488 | <title>Domain Logon Configuration: Windows 9x/Me</title>
|
---|
489 |
|
---|
490 | <para>
|
---|
491 | <indexterm><primary>Windows 9x/Me</primary></indexterm>
|
---|
492 | <indexterm><primary>domain logon</primary></indexterm>
|
---|
493 | <indexterm><primary>LanManager</primary></indexterm>
|
---|
494 | We follow the convention used by most in saying that Windows 9x/Me machines can participate in domain logons. The truth is
|
---|
495 | that these platforms can use only the LanManager network logon protocols.
|
---|
496 | </para>
|
---|
497 |
|
---|
498 | <note><para>
|
---|
499 | <indexterm><primary>Windows XP Home edition</primary></indexterm>
|
---|
500 | <indexterm><primary>LanManager</primary></indexterm>
|
---|
501 | <indexterm><primary>network logon</primary></indexterm>
|
---|
502 | Windows XP Home edition cannot participate in domain or LanManager network logons.
|
---|
503 | </para></note>
|
---|
504 |
|
---|
505 | <procedure>
|
---|
506 | <step><para>
|
---|
507 | Right-click on the <guimenu>Network Neighborhood</guimenu> icon.
|
---|
508 | </para></step>
|
---|
509 |
|
---|
510 | <step><para>
|
---|
511 | The Network Configuration Panel allows all common network settings to be changed.
|
---|
512 | See <link linkend="WME009"></link>.
|
---|
513 | <figure id="WME009"><title>The Network Panel.</title><imagefile>WME009</imagefile></figure>
|
---|
514 | </para>
|
---|
515 |
|
---|
516 | <para>
|
---|
517 | <indexterm><primary>Client for Microsoft Networks</primary></indexterm>
|
---|
518 | <indexterm><primary>Properties</primary></indexterm>
|
---|
519 | Make sure that the <guimenu>Client for Microsoft Networks</guimenu> driver is installed as shown.
|
---|
520 | Click on the <guimenu>Client for Microsoft Networks</guimenu> entry in <guimenu>The following network
|
---|
521 | components are installed:</guimenu> box. Then click the <guibutton>Properties</guibutton> button.
|
---|
522 | </para></step>
|
---|
523 |
|
---|
524 | <step><para>
|
---|
525 | <indexterm><primary>Networks Properties</primary></indexterm>
|
---|
526 | <indexterm><primary>network logon</primary></indexterm>
|
---|
527 | The Client for Microsoft Networks Properties panel is the correct location to configure network logon
|
---|
528 | settings. See <link linkend="WME010"></link>.
|
---|
529 | <figure id="WME010"><title>Client for Microsoft Networks Properties Panel.</title><imagefile>WME010</imagefile></figure>
|
---|
530 | </para>
|
---|
531 |
|
---|
532 | <para>
|
---|
533 | <indexterm><primary>Windows NT domain name</primary></indexterm>
|
---|
534 | <indexterm><primary>domain name</primary></indexterm>
|
---|
535 | Enter the Windows NT domain name, check the <guimenu>Log on to Windows NT domain</guimenu> box,
|
---|
536 | and click <guimenu>OK</guimenu>.
|
---|
537 | </para></step>
|
---|
538 |
|
---|
539 | <step><para>
|
---|
540 | <indexterm><primary>Identification</primary></indexterm>
|
---|
541 | <indexterm><primary>workgroup</primary></indexterm>
|
---|
542 | <indexterm><primary>computer name</primary></indexterm>
|
---|
543 | Click on the <guimenu>Identification</guimenu> button. This is the location at which the workgroup
|
---|
544 | (domain) name and the machine name (computer name) need to be set. See <link linkend="WME013"></link>.
|
---|
545 | <figure id="WME013"><title>Identification Panel.</title><imagefile>WME013</imagefile></figure>
|
---|
546 | </para></step>
|
---|
547 |
|
---|
548 | <step><para>
|
---|
549 | <indexterm><primary>Access Control</primary></indexterm>
|
---|
550 | <indexterm><primary>group accounts</primary></indexterm>
|
---|
551 | <indexterm><primary>domain user</primary></indexterm>
|
---|
552 | <indexterm><primary>User-level access control</primary></indexterm>
|
---|
553 | Now click the <guimenu>Access Control</guimenu> button. If you want to be able to assign share access
|
---|
554 | permissions using domain user and group accounts, it is necessary to enable
|
---|
555 | <guimenu>User-level access control</guimenu> as shown in this panel. See <link linkend="WME014"></link>.
|
---|
556 | <figure id="WME014"><title>Access Control Panel.</title><imagefile>WME014</imagefile></figure>
|
---|
557 | </para></step>
|
---|
558 |
|
---|
559 | </procedure>
|
---|
560 |
|
---|
561 | </sect2>
|
---|
562 |
|
---|
563 | </sect1>
|
---|
564 |
|
---|
565 | <sect1>
|
---|
566 | <title>Common Errors</title>
|
---|
567 |
|
---|
568 | <para>
|
---|
569 | <indexterm><primary>networking systems</primary></indexterm>
|
---|
570 | <indexterm><primary>errors that can afflict</primary></indexterm>
|
---|
571 | The most common errors that can afflict Windows networking systems include:
|
---|
572 | </para>
|
---|
573 |
|
---|
574 | <itemizedlist>
|
---|
575 | <listitem><para>Incorrect IP address.</para></listitem>
|
---|
576 | <listitem><para>Incorrect or inconsistent netmasks.</para></listitem>
|
---|
577 | <listitem><para>Incorrect router address.</para></listitem>
|
---|
578 | <listitem><para>Incorrect DNS server address.</para></listitem>
|
---|
579 | <listitem><para>Incorrect WINS server address.</para></listitem>
|
---|
580 | <listitem><para>Use of a Network Scope setting &smbmdash; watch out for this one!</para></listitem>
|
---|
581 | </itemizedlist>
|
---|
582 |
|
---|
583 | <para>
|
---|
584 | <indexterm><primary>Windows NT/200x/XP Professional</primary></indexterm>
|
---|
585 | <indexterm><primary>cannot join domain</primary></indexterm>
|
---|
586 | The most common reasons for which a Windows NT/200x/XP Professional client cannot join the Samba controlled domain are:
|
---|
587 | </para>
|
---|
588 |
|
---|
589 | <itemizedlist>
|
---|
590 | <listitem><para>&smb.conf; does not have correct <smbconfoption name="add machine script"/> settings.</para></listitem>
|
---|
591 | <listitem><para><quote>root</quote> account is not in password backend database.</para></listitem>
|
---|
592 | <listitem><para>Attempt to use a user account instead of the <quote>root</quote> account to join a machine to the domain.</para></listitem>
|
---|
593 | <listitem><para>Open connections from the workstation to the server.</para></listitem>
|
---|
594 | <listitem><para>Firewall or filter configurations in place on either the client or the Samba server.</para></listitem>
|
---|
595 | </itemizedlist>
|
---|
596 |
|
---|
597 | </sect1>
|
---|
598 |
|
---|
599 | </chapter>
|
---|