source: branches/samba-3.3.x/docs/htmldocs/using_samba/ch03.html

Last change on this file was 218, checked in by Herwig Bauernfeind, 16 years ago

Import Samba 3.3 branch at 3.3.0 level docs htmldocs (psmedley's port)
File size: 90.7 KB
Line 
1<html>
2<body bgcolor="#ffffff">
3
4<img src="samba2_xs.gif" border="0" alt=" " height="100" width="76"
5hspace="10" align="left" />
6
7<h1 class="head0">Chapter 3. Configuring Windows Clients</h1>
8
9
10<p><a name="INDEX-1"/><a name="INDEX-2"/>Configuring Windows to use
11your new Samba server is really quite simple. SMB is
12Microsoft's native language for resource sharing on
13a local area network, so much of the installation and setup on the
14Windows client side have been taken care of already.</p>
15
16
17<div class="sect1"><a name="samba2-CHP-3-SECT-1"/>
18
19<h2 class="head1">Windows Networking Concepts</h2>
20
21<p><a name="INDEX-3"/><a name="INDEX-4"/>Windows is different from Unix in
22many ways, including how it supports networking. Before we get into
23the hands-on task of clicking our way through the dialog boxes to
24configure each version of Windows, we need to provide you with a
25common foundation of networking technologies and concepts that apply
26to the entire family of Windows operating systems.</p>
27
28<p>For each Windows version, these are the main issues we will be
29dealing with:</p>
30
31<ul><li>
32<p>Making sure required networking components are installed and bound to
33the network adapter</p>
34</li><li>
35<p>Configuring networking with a valid IP address, netmask and gateway,
36and WINS and DNS name servers</p>
37</li><li>
38<p>Assigning workgroup and computer names</p>
39</li><li>
40<p>Setting the username(s) and password(s)</p>
41</li></ul>
42<p>In addition, some minor issues involving communication and
43coordination between Windows and Unix are different among Windows
44versions.</p>
45
46<p>One can go crazy thinking about the ways in which Unix is different
47from Windows, or the ways in which members of the Windows family are
48different from each other in underlying technology, behavior, or
49appearance. For now let's just focus on their
50similarities and see if we can find some common ground.</p>
51
52
53<div class="sect2"><a name="samba2-CHP-3-SECT-1.1"/>
54
55<h3 class="head2">Components</h3>
56
57<p><a name="INDEX-5"/><a name="INDEX-6"/>Unix
58systems historically have been monolithic in nature, requiring
59recompilation or relinking to create a kernel with a customized
60feature set. However, modern versions have the ability to load or
61unload device drivers or various other operating-system features as
62modules while the system is running, without even needing to reboot.</p>
63
64<p>Windows allows for configuration by installing or uninstalling
65<em class="firstterm">components</em>. As far as networking goes,
66components can be one of three things:<a name="FNPTR-1"/><a href="#FOOTNOTE-1">[1]</a></p>
67
68<ul><li>
69<p>Protocols</p>
70</li><li>
71<p>Clients</p>
72</li><li>
73<p>Services</p>
74</li></ul>
75<p>Since Samba works using the TCP/IP protocol, of course
76we'll want to have that installed. In some cases, we
77also will want to find protocols to <em class="emphasis">uninstall</em>.
78For example, if Netware protocol (IPX/SPX) is not required on the
79network, it might as well be removed.</p>
80
81<p><a name="INDEX-7"/><a name="INDEX-8"/>NetBEUI protocol should be removed if
82possible. Having NetBEUI running at the same time as NetBIOS over
83TCP/IP causes the system to look for services under two different
84protocols, only one of which is likely to be in use. When Windows is
85configured with one or more unused protocols, 30-second delays will
86result when Windows tries to communicate with the unused protocol.
87Eventually, it times out and tries another one, until it finds one
88that works. This fruitless searching results in terrible performance.</p>
89
90<p>The other two items in the list, client and service components, are
91pretty much what you'd expect. Client components
92perform tasks related to connecting with network servers, and service
93components are for making the local system into a server of resources
94on the network. In <a href="ch01.html">Chapter 1</a> we told you that SMB
95systems can act as both clients and servers, offering resources on
96the network at the same time they request resources. In accordance
97with that, it is possible to install a component for SMB client
98services and, separately, a service component that allows file and
99printer shares on the local system to be accessible from other
100systems on the network.</p>
101
102
103<div class="sect3"><a name="samba2-CHP-3-SECT-1.1.1"/>
104
105<h3 class="head3">Bindings</h3>
106
107<p><a name="INDEX-9"/><a name="INDEX-10"/><a name="INDEX-11"/>Once
108a networking component is installed, it must be
109<em class="firstterm">bound</em> to a hardware interface, or
110<em class="firstterm">adapter</em>, to be used on the network. At first
111this might seem like an odd complication; however, it is a conceptual
112model that allows the associations between hardware and software to
113be clearly displayed and easily modified through a graphical
114interface.</p>
115
116<p>We will want to make sure that your Windows client has both TCP/IP
117and the client component for SMB networking installed and also that
118it is bound to the network adapter that connects to our Samba
119network, which in most cases will be an Ethernet adapter.</p>
120
121
122</div>
123
124
125</div>
126
127
128<div class="sect2"><a name="samba2-CHP-3-SECT-1.2"/>
129
130<h3 class="head2">IP Address</h3>
131
132<p>Just like any Unix system (or any other system that is using TCP/IP),
133your Windows systems will need an <a name="INDEX-12"/>IP address. If you are using
134<a name="INDEX-13"/>DHCP
135on your network, you can configure Windows to obtain its IP address
136automatically by using a DHCP server. Otherwise, you will need to
137assign a static IP address manually along with a netmask.<a name="FNPTR-2"/><a href="#FOOTNOTE-2">[2]</a></p>
138
139<p>If you are on a private network where you have the authority to
140assign your own IP addresses, you can select from addresses in one of
141three ranges:<a name="FNPTR-3"/><a href="#FOOTNOTE-3">[3]</a></p>
142
143<ul><li>
144<p>10.0.0.1 through 10.255.255.254</p>
145</li><li>
146<p>172.16.0.1 through 172.31.255.254</p>
147</li><li>
148<p>192.168.0.1 through 192.168.255.254</p>
149</li></ul>
150<p>These address ranges are reserved for private networks not directly
151connected to the Internet. For more information on using these
152private network addresses, see RFC 1918.</p>
153
154<p>If you're not maintaining your own separate network,
155see your system administrator for some available addresses on your
156network, as well as for the proper netmask to use.</p>
157
158<p>You should also be prepared to enter the IP address of the default
159gateway for the network. In some networks, the default gateway is the
160system or router that connects the LAN to the Internet. In other
161cases, the default gateway connects a subnet into a larger
162departmental or enterprise network.</p>
163
164
165</div>
166
167
168<div class="sect2"><a name="samba2-CHP-3-SECT-1.3"/>
169
170<h3 class="head2">Name Resolution</h3>
171
172<p><a name="INDEX-14"/><a name="INDEX-15"/>Name resolution is the function of
173translating human-friendly hostnames, such as
174<em class="emphasis">hopi</em>, or fully qualified domain names (FQDNs),
175such as <tt class="literal">mixtec.metran.cx</tt>, into IP addresses, such
176as 172.16.1.11 or 172.16.1.7.</p>
177
178<p>Unix systems can perform name resolution using an
179<em class="filename">/etc/hosts</em><a name="INDEX-16"/><a name="INDEX-17"/> file at the minimum, and more commonly can
180also incorporate services such as
181<a name="INDEX-18"/>DNS (Domain Name System)
182and <a name="INDEX-19"/>NIS (Network Information Service).
183Thus, name resolution is not necessarily performed by one isolated
184part of the operating system or one daemon, but is a system that can
185have a number of dispersed parts (although the
186<a name="INDEX-20"/>name
187service switch, with its
188<em class="filename">/etc/nsswitch.conf</em><a name="INDEX-21"/><a name="INDEX-22"/> configuration file, helps to tie them
189together).</p>
190
191<p>Although the specific implementation is different, name resolution in
192Windows is also performed by querying a number of resources, some of
193which are similar (or even identical) to their Unix counterparts.</p>
194
195
196<div class="sect3"><a name="samba2-CHP-3-SECT-1.3.1"/>
197
198<h3 class="head3">Broadcast name resolution</h3>
199
200<p>On the other hand, there is one way in which Windows is not at all
201similar to Unix. If a Windows workstation is set up with no WINS name
202server, it will use the broadcast method of
203<a name="INDEX-23"/><a name="INDEX-24"/>name resolution, as described in <a href="ch01.html">Chapter 1</a>,<a name="FNPTR-4"/><a href="#FOOTNOTE-4">[4]</a> probably resulting in a
204very busy network. And even if you provide name servers for your
205Windows system to use, it might still resort to broadcast name
206resolution if it is unsuccessful at querying the name servers. For
207this reason, we recommend that you provide multiple reliable name
208servers for your Windows computers on the network.</p>
209
210<p>If that weren't enough to get you interested in
211setting up WINS and DNS servers, broadcast name resolution is usually
212limited to working on the local subnet because routers are usually
213configured not to forward broadcast packets to other networks.</p>
214
215
216</div>
217
218
219
220<div class="sect3"><a name="samba2-CHP-3-SECT-1.3.2"/>
221
222<h3 class="head3">WINS</h3>
223
224<p>We've already told you about WINS in <a href="ch01.html">Chapter 1</a>, and we don't have much more
225to say about it here. WINS can translate simple NetBIOS computer
226names such as <em class="emphasis">huastec</em> or
227<em class="emphasis">navajo</em> into IP addresses, as required on an SMB
228network. Of course, the interesting thing here is that Samba can act
229as a WINS server if you include the line:</p>
230
231<blockquote><pre class="code">wins support = yes</pre></blockquote>
232
233<p>in your Samba server's
234<em class="filename">smb.conf</em><a name="INDEX-25"/><a name="INDEX-26"/> file.
235This can be a good thing, to be sure, and we highly recommend it. Not
236only will you have a reliable WINS server to reduce the number of
237broadcast packets, but you won't need to run Windows
238NT/2000/XP to get it.</p>
239<a name="samba2-CHP-3-NOTE-91"/><blockquote class="note"><h4 class="objtitle">WARNING</h4>
240<p>One caveat about using Samba as a <a name="INDEX-27"/><a name="INDEX-28"/>WINS server is that Samba (up to Version
2412.2, at least) cannot synchronize with other WINS servers. So if you
242specify a Samba server as your Windows system's WINS
243server, you must be careful not to specify any additional (i.e.,
244secondary) WINS servers. If you do, you are likely to run into
245problems because the servers will not be able to synchronize their
246databases with each other. In Samba's defense, if
247you are using a Samba WINS server (running on a typically reliable
248Unix host), you will probably have little need for a secondary WINS
249server anyway.</p>
250</blockquote>
251
252
253</div>
254
255
256
257<div class="sect3"><a name="samba2-CHP-3-SECT-1.3.3"/>
258
259<h3 class="head3">LMHOSTS</h3>
260
261<p>All Windows versions support a backup method of name resolution, in
262the form of a file called
263<em class="filename">LMHOSTS</em><a name="INDEX-29"/> <em class="emphasis"><a name="FNPTR-5"/><a href="#FOOTNOTE-5">[5]</a></em>
264that contains a lookup table of computer names and IP addresses. This
265exists for &quot;historical purposes,&quot;
266and is a rather awkward method of name resolution because it requires
267the administrator (i.e., you!) to keep copies of
268<em class="filename">LMHOSTS</em> up to date on every single Windows
269system on the network. To be fully effective,
270<em class="filename">LMHOSTS</em> would have to be updated every time a
271new system were added to (or removed from) the network. Of course,
272there might be ways to automate that process, but a better option
273would be simply to run a WINS name server that is intentionally
274designed to solve that specific problem.</p>
275
276<p>There are perhaps a couple of reasons why you might want to bother
277with <em class="filename">LMHOSTS</em> files. In rare situations, there
278might be no WINS server on the network. Or maybe a WINS server
279exists, but it's unreliable. In both cases, if the
280Windows system has a valid <em class="filename">LMHOSTS</em> file, it can
281help to avoid your network bogging down from those dreaded broadcast
282name queries.</p>
283
284<p>The format of the <em class="filename">LMHOSTS</em> file is simple and
285similar to the <em class="filename">/etc/hosts</em> file with which you
286might be familiar from running Unix systems. Here are the contents of
287a sample <em class="filename">LMHOSTS</em> file:</p>
288
289<blockquote><pre class="code">172.16.1.1 toltec
290172.16.1.2 aztec
291172.16.1.3 mixtec
292172.16.1.4 zapotec
293172.16.1.5 huastec
294172.16.1.6 maya
295172.16.1.7 olmec
296172.16.1.8 chichimec
297172.16.1.11 hopi
298172.16.1.12 zuni
299172.16.1.13 dine
300172.16.1.14 pima
301172.16.1.15 apache
302172.16.1.21 inca
303172.16.1.22 qero</pre></blockquote>
304
305<p>As you can see, the format is like that of
306<em class="filename">/etc/hosts</em>, except that instead of an FQDN
307(e.g., <tt class="literal">toltec.metran.cx</tt>), only a NetBIOS computer
308name (<tt class="literal">toltec</tt>) is given. One way to create an
309<em class="filename">LMHOSTS</em> file for your Windows systems is to copy
310a <em class="filename">/etc/hosts</em> file and edit out the parts you
311don't need. This will work great if your network
312doesn't have a DNS (or NIS) name server and the Unix
313system is dependent on <em class="filename">/etc/hosts</em> for its own
314name service. But if your Unix system is querying a DNS server (which
315is the most frequent case on anything larger than the very smallest
316networks), you would be better advised to look in the DNS
317server's configuration files for your source of
318computer names and IP addresses.</p>
319
320<p>If you do not have administrative access to your
321network's DNS server, you might be able to use tools
322such as <em class="emphasis">nslookup</em><a name="INDEX-30"/>,
323<em class="emphasis">nmap</em><a name="INDEX-31"/>, and
324<em class="emphasis">dig</em><a name="INDEX-32"/> to query the server and obtain the
325information you need.</p>
326
327
328</div>
329
330
331
332<div class="sect3"><a name="samba2-CHP-3-SECT-1.3.4"/>
333
334<h3 class="head3">DNS</h3>
335
336<p>The <a name="INDEX-33"/><a name="INDEX-34"/>DNS
337is responsible for translating human-readable, Internet-style
338hostnames such as <tt class="literal">pima.metran.cx</tt> or
339<tt class="literal">sales.oreilly.com</tt> into IP addresses.</p>
340
341<p>On your first reading of this section, you might be wondering what a
342section on DNS is doing in a book about NetBIOS and SMB networking.
343Remember, we told you that Windows can use more than WINS (NetBIOS
344Name Service) in its strategy for performing name resolution. Because
345DNS is also able to supply IP addresses for simple hostnames (which
346are usually the same as NetBIOS computer names), it can be helpful to
347configure Windows to know about a DNS server on your network. This is
348slightly more important for newer Windows versions than older ones,
349and more so for Windows NT/2000/XP than for Windows 95/98/Me, because
350nowadays Microsoft is focusing more on TCP/IP as the standard
351protocol and DNS as the primary name service.</p>
352
353<p>To find the address of your DNS server, look at the file
354<em class="emphasis">/etc/resolv.conf</em><a name="INDEX-35"/><a name="INDEX-36"/> on your Samba server or any other Unix
355system on the local network that is using DNS. It looks like the
356following:</p>
357
358<blockquote><pre class="code">#resolv.conf
359domain metran.cx
360nameserver 127.0.0.1
361nameserver 172.16.1.53</pre></blockquote>
362
363<p>In this example, the first name server in the list is 127.0.0.1,
364which indicates that the Samba server is also a DNS server for this
365LAN.<a name="FNPTR-6"/><a href="#FOOTNOTE-6">[6]</a> In that case, you would use its network IP
366address (not <a name="INDEX-37"/><a name="INDEX-38"/>127.0.0.1, its localhost address)
367for your DNS server when configuring Windows. Otherwise, use the
368other addresses you find in the lines beginning with
369<tt class="literal">nameserver</tt>. Try to select ones on your own
370network. Any name servers listed in
371<em class="emphasis">/etc/resolv.conf</em> should work, but
372you'll get better performance by using a server
373nearby.</p>
374
375<p>All versions of Windows can be configured to know of multiple domain
376name servers, and you might wish to take advantage of this for
377increased reliability. If the first domain name server does not
378respond, Windows can try others in its list.</p>
379
380
381</div>
382
383
384
385<div class="sect3"><a name="samba2-CHP-3-SECT-1.3.5"/>
386
387<h3 class="head3"><em class="filename">HOSTS</em></h3>
388
389<p>Similar to how the <em class="filename">LMHOSTS</em> file can be added to
390supplement WINS, the
391<em class="filename">HOSTS</em><a name="INDEX-39"/> file on a Windows system can be optionally
392added to supplement DNS name resolution. Most of our comments
393regarding <em class="filename">LMHOSTS</em> also apply here.</p>
394
395<p>This time the format of the file is not just similar to that of
396<em class="filename">/etc/hosts</em> found on Unix&mdash;the format is
397<em class="emphasis">exactly</em> the same. You can simply copy
398<em class="filename">/etc/hosts</em> from your Samba server or other Unix
399system to the proper directory on your Windows system.</p>
400
401<p>On Windows 95/98/Me, the <em class="filename">HOSTS</em> file goes in the
402Windows installation directory, which is usually
403<em class="filename">C:\Windows</em>. Note that a file called
404<em class="filename">hosts.sam</em><a name="INDEX-40"/> is already there, which is a sample
405<em class="filename">HOSTS</em> file provided by Microsoft.</p>
406
407<p>On Windows NT/2000/XP, the <em class="filename">HOSTS</em> file goes in
408the <em class="filename">\system32\drivers\etc</em> directory under the
409Windows installation directory, which is usually
410<em class="filename">C:\WINNT</em>.</p>
411
412
413</div>
414
415
416</div>
417
418
419<div class="sect2"><a name="samba2-CHP-3-SECT-1.4"/>
420
421<h3 class="head2">Passwords</h3>
422
423<p><a name="INDEX-41"/><a name="INDEX-42"/><a name="INDEX-43"/>Unix systems use
424username and password pairs to authenticate users either on a local
425system or in an NIS domain. Windows NT/2000/XP are very similar; a
426user supplies his username and password to log on to the local system
427or to a Windows domain.</p>
428
429<p>When the SMB network is set up as a workgroup, things are different.
430There is no domain to log on to, although shares on the network can
431be password-protected. In this case, one password is associated with
432each password-protected share, rather than with individual users.</p>
433
434<p>Samba's default user-level
435<a name="INDEX-44"/>authentication in a workgroup is
436different from that of Windows. To access shares on the Samba host,
437users are required to supply a valid username and password for an
438account on the Samba host. This will be discussed in more detail in
439<a href="ch09.html">Chapter 9</a>.</p>
440
441<p><a name="INDEX-45"/>An unfortunate
442complication arises with passwords. In the first release of Windows
44395 and in Windows NT 4.0 with Service Pack 2 (SP2) or less, as well
444as in all previous versions of Windows, passwords are allowed to be
445sent over the network in plain text. But in Windows 95 with the
446network redirector update,<a name="FNPTR-7"/><a href="#FOOTNOTE-7">[7]</a></p>
447
448<p>Windows NT 4.0 SP3 or later, and all subsequent releases of Windows,
449a registry setting must be <a name="INDEX-46"/><a name="INDEX-47"/><a name="INDEX-48"/>modified to enable plain-text
450passwords. These more modern versions of Windows prefer to send
451encrypted passwords, and if you are working with one of them (and
452don't want to have to modify the registry), you must
453have the line:</p>
454
455<blockquote><pre class="code">encrypt passwords = yes</pre></blockquote>
456
457<p>in the <tt class="literal">[global]</tt> section of your
458<em class="filename">smb.conf</em><a name="INDEX-49"/><a name="INDEX-50"/> file. In addition, you must run the
459command:</p>
460
461<blockquote><pre class="code"># <tt class="userinput"><b>smbpasswd -a <em class="replaceable">username</em></b></tt></pre></blockquote>
462
463<p>for each user on the Samba host to add their passwords to
464Samba's collection of encrypted passwords. We showed
465you how to do this in <a href="ch02.html">Chapter 2</a>.</p>
466
467<p>If your first attempt to access a Samba share results in a dialog box
468asking for a password for
469<tt class="literal">IPC$</tt><a name="INDEX-51"/><a name="INDEX-52"/>, as shown in <a href="ch03.html#samba2-CHP-3-FIG-1">Figure 3-1</a>, it is probably because you neglected either
470or both of these two steps, and the Samba server did not recognize
471the encrypted password that the Windows system sent to it. Another
472possible dialog box that might come up is the one shown in <a href="ch03.html#samba2-CHP-3-FIG-2">Figure 3-2</a>, which was presented by a Windows 2000 client.</p>
473
474<div class="figure"><a name="samba2-CHP-3-FIG-1"/><img src="figs/sam2_0301.gif"/></div><h4 class="head4">Figure 3-1. Windows 98 asking for IPC$ password</h4>
475
476<div class="figure"><a name="samba2-CHP-3-FIG-2"/><img src="figs/sam2_0302.gif"/></div><h4 class="head4">Figure 3-2. Windows 2000 logon error dialog</h4>
477
478<p>The rest of this chapter is divided into four sections. The first
479section covers setting up Windows 95/98/Me computers, and the rest of
480the sections cover Windows NT 4.0, Windows 2000, and Windows XP
481individually. Each section roughly parallels the order in which
482we've introduced networking concepts in this
483section. You need to read only the section that applies to the
484Windows version with which you are working, and once you have
485finished reading it, you can continue at the beginning of the next
486chapter where we will start covering more advanced Samba features and
487networking issues.</p>
488
489<a name="samba2-CHP-3-NOTE-92"/><blockquote class="note"><h4 class="objtitle">TIP</h4>
490<p>Keep in mind that we are continuing our example from <a href="ch02.html">Chapter 2</a>, in which we are setting up a very simple
491prototype network using a workgroup that has very lax security. After
492you have the basics working, we recommend you continue with later
493chapters to learn how to implement both better security and a Samba
494domain. <a name="INDEX-53"/></p>
495</blockquote>
496
497
498</div>
499
500
501</div>
502
503
504
505<div class="sect1"><a name="samba2-CHP-3-SECT-2"/>
506
507<h2 class="head1">Setting Up Windows 95/98/Me Computers</h2>
508
509<p>The <a name="INDEX-54"/>Windows 95/98/Me operating systems are very
510similar to each other, and as far as this chapter is concerned, it is
511possible to treat them with a common set of directions.</p>
512
513
514<div class="sect2"><a name="samba2-CHP-3-SECT-2.1"/>
515
516<h3 class="head2">Setting Up the Network</h3>
517
518<p>Samba uses TCP/IP to communicate with clients on the network, so you
519will need to make sure there is support for TCP/IP on each Windows
520client. Unlike Unix operating systems, Windows does not necessarily
521have support for TCP/IP installed. However, when Windows is installed
522on a computer with a network card or a network card is added to a
523system already running Windows, TCP/IP support is installed by
524default, along with the Client for Microsoft Networks, which supports
525SMB file and printer sharing.</p>
526
527<p>To make sure both services are installed on your Windows system,
528double-click the Network icon in the Control Panel to open the
529Network dialog box, as shown in <a href="ch03.html#samba2-CHP-3-FIG-3">Figure 3-3</a>.</p>
530
531<div class="figure"><a name="samba2-CHP-3-FIG-3"/><img src="figs/sam2_0303.gif"/></div><h4 class="head4">Figure 3-3. The Windows 95/98/Me Network dialog</h4>
532
533<p>You should see at least the Client for Microsoft Networks component
534installed on the system, and hopefully a networking device
535(preferably an Ethernet card) bound to the TCP/IP protocol. If there
536is only one networking hardware device, you'll see
537the TCP/IP protocol listed below the device to which it is bound, as
538shown in <a href="ch03.html#samba2-CHP-3-FIG-1">Figure 3-1</a>.</p>
539
540<p>You might also see &quot;File and printer sharing for
541Microsoft Networks,&quot; which is used to make the
542system into a server. In addition, you might see NetBEUI or Novell
543Networking. Definitely remove NetBEUI unless you are sure you need
544it, and if you don't have any Novell servers on your
545network, you can remove Novell (IPX/SPX) as well. To remove a
546service, simply click its name and then click the Remove button.</p>
547
548
549<div class="sect3"><a name="samba2-CHP-3-SECT-2.1.1"/>
550
551<h3 class="head3">Adding TCP/IP</h3>
552
553<p><a name="INDEX-55"/><a name="INDEX-56"/>If
554you don't see TCP/IP listed, you'll
555need to install the protocol.</p>
556
557<p>You can add the protocol by inserting the Windows distribution CD-ROM
558in your CD-ROM drive and clicking the Add button below the component
559window. Indicate that you wish to add a protocol by selecting
560Protocol and clicking &quot;Add...&quot; on
561the following dialog box, which should look similar to <a href="ch03.html#samba2-CHP-3-FIG-4">Figure 3-4</a>.</p>
562
563<div class="figure"><a name="samba2-CHP-3-FIG-4"/><img src="figs/sam2_0304.gif"/></div><h4 class="head4">Figure 3-4. Selecting a component type</h4>
564
565<p>After that, select manufacturer Microsoft, then protocol TCP/IP, as
566shown in <a href="ch03.html#samba2-CHP-3-FIG-3">Figure 3-3</a>, then click OK. After doing so,
567you will be returned to the network dialog. Click OK to close the
568dialog box, and Windows will install the necessary components from
569the CD-ROM and request that the system be rebooted. Go ahead and
570reboot the system, and you're set.</p>
571
572<p>If Client for Microsoft Networks is not in the list, you can add it
573similarly. The only significant difference is that you are adding a
574client instead of a protocol, so make sure to select
575&quot;Client&quot; rather than
576&quot;Protocol&quot; when asked.</p>
577
578
579</div>
580
581
582
583<div class="sect3"><a name="samba2-CHP-3-SECT-2.1.2"/>
584
585<h3 class="head3">Configuring TCP/IP</h3>
586
587<p><a name="INDEX-57"/><a name="INDEX-58"/>If you have more than one networking
588device (for example, both an Ethernet card and a modem for dial-up
589networking), the protocol to hardware bindings will be indicated by
590arrows, as shown in <a href="ch03.html#samba2-CHP-3-FIG-5">Figure 3-5</a>.</p>
591
592<div class="figure"><a name="samba2-CHP-3-FIG-5"/><img src="figs/sam2_0305.gif"/></div><h4 class="head4">Figure 3-5. Selecting a protocol to install</h4>
593
594<p>Select the TCP/IP protocol linked to the networking device that will
595be accessing the Samba network. If you have only one networking
596device, simply click the TCP/IP item. Now click the Properties button
597to open the TCP/IP Properties dialog. You should see something
598similar to <a href="ch03.html#samba2-CHP-3-FIG-6">Figure 3-6</a>.</p>
599
600<div class="figure"><a name="samba2-CHP-3-FIG-6"/><img src="figs/sam2_0306.gif"/></div><h4 class="head4">Figure 3-6. Selecting the correct TCP/IP protocol</h4>
601
602
603</div>
604
605
606
607<div class="sect3"><a name="samba2-CHP-3-SECT-2.1.3"/>
608
609<h3 class="head3">IP Address tab</h3>
610
611<p><a name="INDEX-59"/><a name="INDEX-60"/>The
612IP Address tab is shown in <a href="ch03.html#samba2-CHP-3-FIG-7">Figure 3-7</a>.</p>
613
614<div class="figure"><a name="samba2-CHP-3-FIG-7"/><img src="figs/sam2_0307.gif"/></div><h4 class="head4">Figure 3-7. The IP Address tab</h4>
615
616<p>If you use DHCP on your network to provide IP addresses automatically
617to Windows systems, select the &quot;Obtain an IP address
618automatically&quot; radio button. Otherwise, click the
619&quot;Specify an IP address&quot; radio
620button and enter the client's address and subnet
621mask in the space provided. You or your network manager should have
622selected an address for the client on the same subnet (LAN) as the
623Samba server.</p>
624
625
626</div>
627
628
629
630<div class="sect3"><a name="samba2-CHP-3-SECT-2.1.4"/>
631
632<h3 class="head3">WINS Configuration tab</h3>
633
634<p><a name="INDEX-61"/><a name="INDEX-62"/>If you've
635enabled WINS on Samba or are choosing to make use of another WINS
636server on your network, you must tell Windows the
637server's address. After selecting the WINS
638Configuration tab, you will see the dialog box shown in <a href="ch03.html#samba2-CHP-3-FIG-8">Figure 3-8</a>.</p>
639
640<div class="figure"><a name="samba2-CHP-3-FIG-8"/><img src="figs/sam2_0308.gif"/></div><h4 class="head4">Figure 3-8. The WINS Configuration tab</h4>
641
642<p>This is for Windows 98/Me; Windows 95 is just a little different,
643having separate spaces for the primary and backup WINS server IP
644addresses.</p>
645
646<p>Select the &quot;Enable WINS Resolution&quot;
647radio button, and enter the WINS server's address in
648the space provided, then click the Add button. Do not enter anything
649in the Scope ID field.</p>
650<a name="samba2-CHP-3-NOTE-93"/><blockquote class="note"><h4 class="objtitle">WARNING</h4>
651<p>A bug in Windows 95/98 sometimes causes the IP address of the WINS
652server to disappear after the OK button is clicked. This happens only
653when only a primary WINS server has been specified. The workaround is
654to fill in the fields for both primary and secondary WINS servers,
655using the same IP address for each.</p>
656</blockquote>
657
658
659</div>
660
661
662
663<div class="sect3"><a name="samba2-CHP-3-SECT-2.1.5"/>
664
665<h3 class="head3">DNS Configuration tab</h3>
666
667<p><a name="INDEX-63"/><a name="INDEX-64"/>Unless you are using DHCP, you
668will need to provide the IP address of one or more DNS servers. Click
669the DNS tab, then click the &quot;Enable
670DNS&quot; radio button, and type the IP address of one or
671more DNS servers into the appropriate field, shown in <a href="ch03.html#samba2-CHP-3-FIG-9">Figure 3-9</a>, to add the server's address
672to the top DNS Server Search Order field.</p>
673
674<div class="figure"><a name="samba2-CHP-3-FIG-9"/><img src="figs/sam2_0309.gif"/></div><h4 class="head4">Figure 3-9. The DNS Configuration tab</h4>
675
676<p>Also, provide the hostname (which is the same as the NetBIOS computer
677name) of the Windows 95/98/Me computer and your Internet domain. (You
678will need to enter the computer name again later, along with the
679workgroup. Make sure to enter the same name each time.) You can
680safely ignore the Domain Suffix Search Order field for anything
681related to Samba.</p>
682
683
684</div>
685
686
687
688<div class="sect3"><a name="samba2-CHP-3-SECT-2.1.6"/>
689
690<h3 class="head3">LMHOSTS file</h3>
691
692<p><a name="INDEX-65"/><a name="INDEX-66"/>If
693you want to install an <em class="filename">LMHOSTS</em> file, it must be
694placed in your Windows installation directory (usually
695<em class="filename">C:\Windows</em>). In the same directory, Microsoft
696has provided a sample <em class="filename">LMHOSTS</em> file named
697<em class="filename">lmhosts.sam</em>, which you might want to look at for
698further information on the file's format.</p>
699
700
701</div>
702
703
704
705<div class="sect3"><a name="samba2-CHP-3-SECT-2.1.7"/>
706
707<h3 class="head3">NetBIOS tab</h3>
708
709<p><a name="INDEX-67"/><a name="INDEX-68"/>This tab
710appears in Windows 98/Me, but not in Windows 95. All you need to do
711here is make sure the checkbox is checked, enabling NetBIOS over
712TCP/IP. If TCP/IP is your only protocol installed (as we recommended
713earlier), the selection will be grayed out, with the box checked so
714that you couldn't uncheck it even if you wanted to.</p>
715
716
717</div>
718
719
720
721<div class="sect3"><a name="samba2-CHP-3-SECT-2.1.8"/>
722
723<h3 class="head3">Bindings tab</h3>
724
725<p><a name="INDEX-69"/><a name="INDEX-70"/>The
726final tab to look at is Bindings, as shown in <a href="ch03.html#samba2-CHP-3-FIG-10">Figure 3-10</a>.</p>
727
728<div class="figure"><a name="samba2-CHP-3-FIG-10"/><img src="figs/sam2_0310.gif"/></div><h4 class="head4">Figure 3-10. The Bindings tab</h4>
729
730<p>You should have a check beside Client for Microsoft Networks,
731indicating that it's using TCP/IP. If you have
732&quot;File and printer sharing for Microsoft
733Networks&quot; in the dialog, it should also be checked,
734as shown in <a href="ch03.html#samba2-CHP-3-FIG-10">Figure 3-10</a>.</p>
735
736
737</div>
738
739
740</div>
741
742
743<div class="sect2"><a name="samba2-CHP-3-SECT-2.2"/>
744
745<h3 class="head2">Setting the Computer Name and Workgroup</h3>
746
747<p><a name="INDEX-71"/><a name="INDEX-72"/><a name="INDEX-73"/><a name="INDEX-74"/>Finally, click the OK button in the
748TCP/IP configuration dialog, and you'll be taken
749back to the Network Configuration dialog. Then select the
750Identification tab, which will take you to the dialog box shown in
751<a href="ch03.html#samba2-CHP-3-FIG-11">Figure 3-11</a>.</p>
752
753<div class="figure"><a name="samba2-CHP-3-FIG-11"/><img src="figs/sam2_0311.gif"/></div><h4 class="head4">Figure 3-11. The Identification tab</h4>
754
755<p>This is where you set your system's NetBIOS name
756(which Microsoft likes to call &quot;computer
757name&quot;). Usually, it is best to make this the same as
758your DNS hostname, if you are going to have one for this system. For
759example, if the system's DNS name is
760<tt class="literal">huastec.metran.cx</tt>, give the computer a NetBIOS
761name of <tt class="literal">huastec</tt> on this tab.</p>
762
763<p>You also set your workgroup name here. In our case,
764it's METRAN, but if you used a different one in
765<a href="ch02.html">Chapter 2</a>, when creating the Samba configuration
766file, use that instead. Just don't call it WORKGROUP
767(the default workgroup name) or you'll be in the
768same workgroup as every misconfigured Windows computer on the planet!</p>
769
770<p>You can also enter a comment string for this computer. See if you can
771come up with some way of describing it that will remind you of what
772and where it is when you see the comment in a list displayed on
773another computer. Everyone on the network will be able to see your
774comment, so be careful not to include any information that might be
775useful to crackers.</p>
776
777<p>Finally, click the OK button and follow whatever instructions Windows
778provides. (You might have to insert your Windows distribution CD-ROM
779and/or reboot.)</p>
780
781
782</div>
783
784
785<div class="sect2"><a name="samba2-CHP-3-SECT-2.3"/>
786
787<h3 class="head2">Username and Password</h3>
788
789<p><a name="INDEX-75"/><a name="INDEX-76"/><a name="INDEX-77"/>You have probably already given
790Windows a username and password by now. However, to authenticate with
791the Samba server, your Windows username and password must match with
792a valid account on the Samba server.</p>
793
794<p>It is simple to add a new user and password to a Windows 95/98/Me
795system. Just reboot or log out, and when you are prompted for a
796username and password, enter your Unix username and password. (If you
797are using encrypted passwords, you must run
798<em class="emphasis">smbpasswd</em> on the Unix host to enter them into
799Samba's password database, if you have not already
800done so.) You can use this method to add as many users as you want,
801so as to allow more than one user to use the Windows system to gain
802access to the Samba shares.</p>
803
804<p>If you mistakenly entered the wrong password or your Unix password
805changes, you can change your password on the Windows system by going
806to the Control Panel and double-clicking the Passwords icon. This
807will bring up the Passwords Properties dialog. Click the Change
808Passwords tab, and you will see the dialog shown in <a href="ch03.html#samba2-CHP-3-FIG-12">Figure 3-12</a>. Now click the &quot;Change
809Windows Password...&quot; button, which will bring up the
810Change Windows Password dialog box, shown in <a href="ch03.html#samba2-CHP-3-FIG-13">Figure 3-13</a>. As indicated by the text entry fields in the
811dialog, enter your old password, and then the new password, and again
812to confirm it. Click the OK button and then the Close button on the
813Password Properties dialog box. Reboot or log out, and use your new
814password when you log in again.</p>
815
816<div class="figure"><a name="samba2-CHP-3-FIG-12"/><img src="figs/sam2_0312.gif"/></div><h4 class="head4">Figure 3-12. The Password Properties dialog</h4>
817
818<div class="figure"><a name="samba2-CHP-3-FIG-13"/><img src="figs/sam2_0313.gif"/></div><h4 class="head4">Figure 3-13. The Change Windows Password dialog</h4>
819
820
821<div class="sect3"><a name="samba2-CHP-3-SECT-2.3.1"/>
822
823<h3 class="head3">Logging in for the first time</h3>
824
825<p>If you don't have a Change Passwords tab in the
826Passwords Properties window, it is because networking is not fully
827set up yet. Assuming you've followed all the
828directions given so far, you just need to reboot; when the system
829comes up, it will ask you to log in with a username and a password.</p>
830
831<p>Now for the big moment. Your Samba server is running, and you have
832set up your Windows 95/98/Me client to communicate with it.</p>
833
834
835</div>
836
837
838
839<div class="sect3"><a name="samba2-CHP-3-SECT-2.3.2"/>
840
841<h3 class="head3">Accessing the Samba Server from Windows 95/98</h3>
842
843<p><a name="INDEX-78"/><a name="INDEX-79"/>Double-click the Network Neighborhood
844icon on the desktop. You should see your Samba server listed as a
845member of the workgroup, as shown in <a href="ch03.html#samba2-CHP-3-FIG-14">Figure 3-14</a>.</p>
846
847<div class="figure"><a name="samba2-CHP-3-FIG-14"/><img src="figs/sam2_0314.gif"/></div><h4 class="head4">Figure 3-14. Windows 95/98 Network Neighborhood</h4>
848
849<p>Double-clicking the server name will show the resources that the
850server is offering to the network, as shown in <a href="ch03.html#samba2-CHP-3-FIG-15">Figure 3-15</a> (in this case, the <em class="emphasis">test</em>
851directory).</p>
852
853<div class="figure"><a name="samba2-CHP-3-FIG-15"/><img src="figs/sam2_0315.gif"/></div><h4 class="head4">Figure 3-15. The test shared folder on the Toltec server</h4>
854
855
856</div>
857
858
859
860<div class="sect3"><a name="samba2-CHP-3-SECT-2.3.3"/>
861
862<h3 class="head3">Accessing the Samba Server from Windows Me</h3>
863
864<p>Double-click the My Network Places icon on the desktop. You should
865see the test shared directory as shown in <a href="ch03.html#samba2-CHP-3-FIG-16">Figure 3-16</a>.</p>
866
867<div class="figure"><a name="samba2-CHP-3-FIG-16"/><img src="figs/sam2_0316.gif"/></div><h4 class="head4">Figure 3-16. My Network Places on Windows Me</h4>
868
869<p>Double-click the Entire Network icon, and you should see an icon for
870your workgroup, as shown in <a href="ch03.html#samba2-CHP-3-FIG-17">Figure 3-17</a>.</p>
871
872<div class="figure"><a name="samba2-CHP-3-FIG-17"/><img src="figs/sam2_0317.gif"/></div><h4 class="head4">Figure 3-17. Entire Network window, showing the Metran workgroup</h4>
873
874<p>Double-clicking the workgroup icon will bring up a window showing
875every computer in the workgroup, which should include your Samba
876server, as shown in <a href="ch03.html#samba2-CHP-3-FIG-18">Figure 3-18</a>.</p>
877
878<div class="figure"><a name="samba2-CHP-3-FIG-18"/><img src="figs/sam2_0318.gif"/></div><h4 class="head4">Figure 3-18. Computers in Metran workgroup</h4>
879
880<p>Double-click the Samba server's icon, and you will
881get a window showing its shared resources (in this case, the test
882directory) as shown in <a href="ch03.html#samba2-CHP-3-FIG-19">Figure 3-19</a>.</p>
883
884<div class="figure"><a name="samba2-CHP-3-FIG-19"/><img src="figs/sam2_0319.gif"/></div><h4 class="head4">Figure 3-19. View of shares on the Toltec server</h4>
885
886<p>If you don't see the server listed, it might be that
887browsing is not working correctly or maybe the server is just taking
888a few minutes to show up in the browse list. In either case, you can
889click the Start button, then select
890&quot;Run...&quot;. This will give you a
891dialog box into which you can type the name of your server and the
892share name <em class="emphasis">test</em> in the Windows UNC format
893<em class="filename">\\</em><em class="replaceable">server</em><em class="filename">\test</em>,
894as we did in <a href="ch01.html">Chapter 1</a>. This should open a window
895on the desktop showing the contents of the folder. If this does not
896work, there is likely a problem with name resolution, and you can try
897using the server's IP address instead of its
898computer name, like this:</p>
899
900<blockquote><pre class="code">\\172.16.1.1\test</pre></blockquote>
901
902<p>If things still aren't right, go directly to <a href="ch12.html#samba2-CHP-12-SECT-2">Section 12.2</a> to troubleshoot what is wrong
903with the network.</p>
904
905<p>If it works, congratulations! Try copying files to and from the
906server using the Windows drag-and-drop functionality. You might be
907pleasantly surprised how seamlessly everything works. <a name="INDEX-80"/></p>
908
909
910</div>
911
912
913</div>
914
915
916</div>
917
918
919
920<div class="sect1"><a name="samba2-CHP-3-SECT-3"/>
921
922<h2 class="head1">Setting Up Windows NT 4.0 Computers</h2>
923
924<p>Configuring <a name="INDEX-81"/>Windows NT
925is a little different than configuring Windows 95/98/Me. To use Samba
926with Windows NT, you will need both the Workstation service and the
927TCP/IP protocol. Both come standard with NT, but
928we'll work through installing and configuring them
929to make sure they are configured correctly.</p>
930
931
932<div class="sect2"><a name="samba2-CHP-3-SECT-3.1"/>
933
934<h3 class="head2">Basic Configuration</h3>
935
936<p><a name="INDEX-82"/>This section presents the steps
937to follow for TCP/IP-related configuration on Windows NT to get it to
938cooperate with Samba. If you need more details on Windows NT network
939administration, refer to Craig <a name="INDEX-83"/>Hunt and Robert Bruce
940<a name="INDEX-84"/>Thompson's
941<em class="citetitle">Windows NT TCP/IP Network Administration
942</em>(O'Reilly), an excellent guide.</p>
943
944<p>You should perform the following steps as the
945<tt class="literal">Administrator</tt> or another user in the
946<tt class="literal">Administrators</tt> group.</p>
947
948
949<div class="sect3"><a name="samba2-CHP-3-SECT-3.1.1"/>
950
951<h3 class="head3">Installing the TCP/IP protocol</h3>
952
953<p><a name="INDEX-85"/><a name="INDEX-86"/>From
954the Control Panel, double-click the Network icon, click the Protocols
955tab in the Network dialog box, and look to see if you have the TCP/IP
956protocol installed, as shown in <a href="ch03.html#samba2-CHP-3-FIG-20">Figure 3-20</a>.</p>
957
958<div class="figure"><a name="samba2-CHP-3-FIG-20"/><img src="figs/sam2_0320.gif"/></div><h4 class="head4">Figure 3-20. The Protocols tab</h4>
959
960<p>If the protocol is not installed, you need to add it. Click the Add
961button, which will display the Select Network Protocol dialog box
962shown in <a href="ch03.html#samba2-CHP-3-FIG-21">Figure 3-21</a>. You should immediately see the
963TCP/IP protocol as one of the last protocols listed.</p>
964
965<div class="figure"><a name="samba2-CHP-3-FIG-21"/><img src="figs/sam2_0321.gif"/></div><h4 class="head4">Figure 3-21. Select Network Protocol dialog box</h4>
966
967<p>Select TCP/IP as the protocol and confirm it. If
968possible, install only the TCP/IP protocol. If you see anything other
969than TCP/IP listed in the Protocols tab and it is not a protocol that
970you need, you can remove it. If you try to remove a protocol and get
971an error message saying that the protocol is being used by another
972service, you need to click the Services tab and remove that service
973before you can remove the protocol. For example, to remove the NWLink
974IPX/SPX Compatible Transport protocol, you would need to remove the
975Client Service for Netware first.</p>
976
977
978</div>
979
980
981
982<div class="sect3"><a name="samba2-CHP-3-SECT-3.1.2"/>
983
984<h3 class="head3">Installing the Workstation service</h3>
985
986<p><a name="INDEX-87"/><a name="INDEX-88"/>After installing TCP/IP, click the
987Services tab in the Network dialog, and check that you have a
988Workstation service, as shown at the end of the list in <a href="ch03.html#samba2-CHP-3-FIG-22">Figure 3-22</a>.<a name="FNPTR-8"/><a href="#FOOTNOTE-8">[8]</a></p>
989
990<div class="figure"><a name="samba2-CHP-3-FIG-22"/><img src="figs/sam2_0322.gif"/></div><h4 class="head4">Figure 3-22. Network Services tab</h4>
991
992<p>This service is actually the Microsoft Networking Client, which
993allows the computer to access SMB services. The Workstation service
994is mandatory. The service is installed by default on both Windows NT
995Workstation 4.0 and NT Server 4.0. If it's not
996there, you can install it much like TCP/IP. In this case you need to
997click the Add button and then select Workstation Service, as shown in
998<a href="ch03.html#samba2-CHP-3-FIG-23">Figure 3-23</a>.</p>
999
1000<div class="figure"><a name="samba2-CHP-3-FIG-23"/><img src="figs/sam2_0323.gif"/></div><h4 class="head4">Figure 3-23. Select Network Service dialog box</h4>
1001
1002
1003</div>
1004
1005
1006
1007<div class="sect3"><a name="samba2-CHP-3-SECT-3.1.3"/>
1008
1009<h3 class="head3">Configuring TCP/IP</h3>
1010
1011<p><a name="INDEX-89"/><a name="INDEX-90"/>After you've installed
1012the Workstation service, return to the Protocols tab and select the
1013TCP/IP Protocol entry in the window. Then click the Properties button
1014below the window. The Microsoft TCP/IP Protocol dialog will be
1015displayed. There are five tabs in the dialog, and you will need to
1016work with four of them:</p>
1017
1018<ul><li>
1019<p>IP Address</p>
1020</li><li>
1021<p>WINS Address</p>
1022</li><li>
1023<p>DNS</p>
1024</li><li>
1025<p>Bindings</p>
1026</li></ul>
1027
1028<div class="sect4"><a name="samba2-CHP-3-SECT-3.1.1.1"/>
1029
1030<h4 class="head4">IP Address tab</h4>
1031
1032<p><a name="INDEX-91"/><a name="INDEX-92"/>The IP
1033Address tab is shown in <a href="ch03.html#samba2-CHP-3-FIG-24">Figure 3-24</a>.</p>
1034
1035<div class="figure"><a name="samba2-CHP-3-FIG-24"/><img src="figs/sam2_0324.gif"/></div><h4 class="head4">Figure 3-24. Microsoft TCP/IP Properties dialog for Windows NT</h4>
1036
1037<p>Select the &quot;Specify an IP address&quot;
1038radio button, and enter the computer's IP address
1039and netmask in the space provided for the proper adapter (Ethernet
1040card). You or your network manager should have selected an address
1041for the client on the same subnet (LAN) as the Samba server. For
1042example, if the server's address is 172.16.1.1 and
1043its network mask is 255.255.255.0, you might use the address
1044172.16.1.13 (if it is available) for the NT workstation, along with
1045the same netmask. If you use DHCP on your network, select the
1046&quot;Obtain an IP Address from a DHCP
1047server&quot; button instead.</p>
1048
1049<p>The gateway field refers to a system typically known as a
1050<em class="emphasis">router</em>. If you have routers connecting multiple
1051networks, you should enter the IP address of the one on your subnet.
1052In our example, the gateway happens to be the same system as the
1053Samba server, but they do not by any means have to be the same.</p>
1054
1055
1056</div>
1057
1058
1059
1060<div class="sect4"><a name="samba2-CHP-3-SECT-3.1.1.2"/>
1061
1062<h4 class="head4">WINS Address tab</h4>
1063
1064<p><a name="INDEX-93"/><a name="INDEX-94"/>Click the
1065WINS Address tab, shown in <a href="ch03.html#samba2-CHP-3-FIG-25">Figure 3-25</a>, and you can
1066begin to enter information about name servers. Enter the address of
1067your WINS server in the space labeled Primary WINS Server. If your
1068Samba server is providing WINS service (in other words, you have the
1069line <tt class="literal">wins</tt> <tt class="literal">support</tt>
1070<tt class="literal">=</tt> <tt class="literal">yes</tt> in the
1071<em class="emphasis">smb.conf</em> file of your Samba server), provide the
1072Samba server's IP address here. Otherwise, provide
1073the address of another WINS server on your network.</p>
1074
1075<div class="figure"><a name="samba2-CHP-3-FIG-25"/><img src="figs/sam2_0325.gif"/></div><h4 class="head4">Figure 3-25. The WINS Address tab</h4>
1076
1077<p>You probably noticed that there is a field here for the network
1078adapter. This field must specify the Ethernet adapter on which
1079you're running TCP/IP so that WINS will provide name
1080service on the correct network. For example, if you have both a LAN
1081and a dial-up adapter, make sure you have the LAN's
1082network card specified here.</p>
1083
1084<p>The checkboxes in the lower half of the dialog are for enabling two
1085other methods of name resolution that Windows can incorporate into
1086its name service. Samba doesn't require either of
1087them, but you might want to enable them to increase the reliability
1088or functionality of name service for your client. See <a href="ch07.html">Chapter 7</a> for further information on name resolution
1089issues.</p>
1090
1091<p>If you'd like to use a DNS server, select the Enable
1092DNS for Windows Resolution checkbox. In addition, you will need to do
1093some configuration to allow the Windows system to find the DNS
1094server, unless you're using DHCP.</p>
1095
1096
1097</div>
1098
1099
1100
1101<div class="sect4"><a name="samba2-CHP-3-SECT-3.1.1.3"/>
1102
1103<h4 class="head4">DNS tab</h4>
1104
1105<p><a name="INDEX-95"/><a name="INDEX-96"/>Click
1106the tab for DNS, as shown in <a href="ch03.html#samba2-CHP-3-FIG-26">Figure 3-26</a>. Enter the
1107IP addresses for one or more DNS servers in the space provided. Also,
1108enter the hostname (which should be the same as the NetBIOS computer
1109name). You will enter this again later in another control panel, so
1110make sure they match. Finally, enter the DNS domain on which this
1111system resides. For example, if your workstation has a domain name
1112such as <em class="emphasis">metran.cx</em>, enter it here. You can safely
1113ignore the other options.</p>
1114
1115<div class="figure"><a name="samba2-CHP-3-FIG-26"/><img src="figs/sam2_0326.gif"/></div><h4 class="head4">Figure 3-26. The DNS tab</h4>
1116
1117
1118</div>
1119
1120
1121
1122<div class="sect4"><a name="samba2-CHP-3-SECT-3.1.1.4"/>
1123
1124<h4 class="head4">The LMHOSTS file</h4>
1125
1126<p>If you want to install an
1127<em class="filename">LMHOSTS</em><a name="INDEX-97"/><a name="INDEX-98"/> file, it
1128must be placed in the directory
1129<em class="filename">\system32\drivers\etc</em> under your Windows
1130installation directory (usually <em class="filename">C:\WINNT</em>). The
1131easy way to make sure it gets to the proper location is to use the
1132Import LMHOSTS button on the WINS Address tab. (But if you want to do
1133it over the network, you will have to do that after file sharing is
1134configured!) Remember to click the Enable LMHOSTS Lookup checkbox on
1135the WINS Address tab to enable this functionality.</p>
1136
1137<p>When you are satisfied with your settings for IP Address, WINS
1138Address, and DNS, click OK to return to the Network dialog box.</p>
1139
1140
1141</div>
1142
1143
1144
1145<div class="sect4"><a name="samba2-CHP-3-SECT-3.1.1.5"/>
1146
1147<h4 class="head4">Bindings</h4>
1148
1149<p><a name="INDEX-99"/><a name="INDEX-100"/>Now click the
1150Bindings tab, and check the bindings of network hardware, services,
1151and protocols. Set the &quot;Show Bindings
1152for&quot; field to &quot;all
1153services,&quot; and click all the + buttons in the tree.
1154You should see a display similar to <a href="ch03.html#samba2-CHP-3-FIG-27">Figure 3-27</a>,
1155which shows that the NetBIOS, Server, and Workstation interface
1156services are connected to the WINS client running TCP/IP protocol,
1157and that the WINS client is bound to the Ethernet adapter of the
1158local area network.</p>
1159
1160<div class="figure"><a name="samba2-CHP-3-FIG-27"/><img src="figs/sam2_0327.gif"/></div><h4 class="head4">Figure 3-27. The Bindings tab</h4>
1161
1162<p>You can safely leave the default values for the remainder of the tabs
1163in the Network dialog box. Click the OK button to complete the
1164configuration. Once the proper files are loaded (if any), you might
1165need to reboot for your changes to take effect.</p>
1166
1167
1168</div>
1169
1170
1171</div>
1172
1173
1174</div>
1175
1176
1177<div class="sect2"><a name="samba2-CHP-3-SECT-3.2"/>
1178
1179<h3 class="head2">Computer Name and Workgroup</h3>
1180
1181<p><a name="INDEX-101"/><a name="INDEX-102"/><a name="INDEX-103"/><a name="INDEX-104"/>The next
1182thing you need to do is to give the system a NetBIOS computer name.
1183From the Control Panel, double-click the Network icon to open the
1184Network dialog box. The first tab in this dialog box should be the
1185Identification tab, as illustrated in <a href="ch03.html#samba2-CHP-3-FIG-28">Figure 3-28</a>.</p>
1186
1187<div class="figure"><a name="samba2-CHP-3-FIG-28"/><img src="figs/sam2_0328.gif"/></div><h4 class="head4">Figure 3-28. The Identification tab</h4>
1188
1189<p>Here, you need to identify your computer with a name and change the
1190default workgroup to the one you specified in the
1191<em class="emphasis">smb.conf</em> file of your Samba server. Click the
1192Change button below the two text fields. This will open an
1193Identification Changes dialog box, where you can set the workgroup
1194and the computer name, as shown in <a href="ch03.html#samba2-CHP-3-FIG-29">Figure 3-29</a>.</p>
1195
1196<div class="figure"><a name="samba2-CHP-3-FIG-29"/><img src="figs/sam2_0329.gif"/></div><h4 class="head4">Figure 3-29. The Identification Changes dialog</h4>
1197<a name="samba2-CHP-3-NOTE-94"/><blockquote class="note"><h4 class="objtitle">WARNING</h4>
1198<p>You entered the computer name earlier as a DNS hostname while
1199configuring TCP/IP, so be sure that the two names match. The name you
1200set here is the NetBIOS name. You're allowed to make
1201it different from the TCP/IP hostname, but doing so is usually not a
1202good idea. Don't worry that Windows NT forces the
1203computer name and the workgroup to be all capital letters;
1204it's smart enough to figure out what you mean when
1205it connects to the network.</p>
1206</blockquote>
1207
1208
1209</div>
1210
1211
1212<div class="sect2"><a name="samba2-CHP-3-SECT-3.3"/>
1213
1214<h3 class="head2">Adding a User</h3>
1215
1216<p><a name="INDEX-105"/><a name="INDEX-106"/>In all
1217the previous steps, you were logged into your Windows NT system as
1218<tt class="literal">Administrator</tt> or another user in the
1219<tt class="literal">Administrators</tt> group. To access resources on the
1220Samba server, you will need to have a username and password that the
1221Samba server recognizes as valid. Generally, the best way to do this
1222is to add a user to your NT system, with the same username and
1223password as a user on the Samba host system.</p>
1224
1225<a name="samba2-CHP-3-NOTE-95"/><blockquote class="note"><h4 class="objtitle">TIP</h4>
1226<p>The directions in this section assume that your network is set up as
1227a workgroup. If you have already set up your network as a domain, as
1228we describe in <a href="ch04.html">Chapter 4</a>, you do not need to
1229follow the instructions here for adding a local user on the Windows
1230NT client system. Simply log on to the domain from the client using a
1231username and password in Samba's
1232<em class="filename">smbpasswd</em> account database, and continue with
1233the next section, <a href="ch03.html#samba2-CHP-3-SECT-3.4">Section 3.3.4</a>.</p>
1234</blockquote>
1235
1236<p>To add a new user, open the Start menu, navigate through the Programs
1237submenu to Administrative Tools (Common), and select User Manager for
1238Domains. Click the User menu and select the first item, Add User...,
1239shown in <a href="ch03.html#samba2-CHP-3-FIG-30">Figure 3-30</a>.</p>
1240
1241<div class="figure"><a name="samba2-CHP-3-FIG-30"/><img src="figs/sam2_0330.gif"/></div><h4 class="head4">Figure 3-30. User Manager for Domains window</h4>
1242
1243<p>This brings up the New User dialog box shown in <a href="ch03.html#samba2-CHP-3-FIG-31">Figure 3-31</a>.</p>
1244
1245<div class="figure"><a name="samba2-CHP-3-FIG-31"/><img src="figs/sam2_0331.gif"/></div><h4 class="head4">Figure 3-31. The New User dialog</h4>
1246
1247<p>Fill it out as shown, using the username and password that were added
1248in the previous chapter, and make sure that only the checkbox labeled
1249Password Never Expires is checked. (This is not the default!) Click
1250the Add button to add the user, and then click the Close button. You
1251should now see your new account added to the list in the User Manager
1252dialog box.</p>
1253
1254<p>Now open the Start menu, select Shut Down, and select the
1255&quot;Close all programs and log on as a different
1256user?&quot; radio button. Click the Yes button, then log
1257in as the user you just added.</p>
1258
1259
1260</div>
1261
1262
1263<div class="sect2"><a name="samba2-CHP-3-SECT-3.4"/>
1264
1265<h3 class="head2">Connecting to the Samba Server</h3>
1266
1267<p>Now for the big moment. Your <a name="INDEX-107"/><a name="INDEX-108"/>Samba
1268server is running, and you have set up your NT client to communicate
1269with it. Double-click the Network Neighborhood icon on the desktop,
1270and you should see your Samba server listed as a member of the
1271workgroup, as shown in <a href="ch03.html#samba2-CHP-3-FIG-32">Figure 3-32</a>.</p>
1272
1273<div class="figure"><a name="samba2-CHP-3-FIG-32"/><img src="figs/sam2_0332.gif"/></div><h4 class="head4">Figure 3-32. The Windows NT Network Neighborhood</h4>
1274
1275<p>Double-clicking the server name will show the resources that the
1276server is offering to the network, as shown in <a href="ch03.html#samba2-CHP-3-FIG-33">Figure 3-33</a>. In this case, the <em class="filename">test</em>
1277directory and the default printer are offered to the Windows NT
1278workstation.</p>
1279
1280<div class="figure"><a name="samba2-CHP-3-FIG-33"/><img src="figs/sam2_0333.gif"/></div><h4 class="head4">Figure 3-33. Shares offered by the Toltec server</h4>
1281
1282<p>If you don't see the server listed,
1283don't panic. Select Run... from the Start menu. A
1284dialog box appears that allows you to type the name of your server
1285and its share directory in Windows format. For example, you would
1286enter
1287<em class="filename">\\</em>toltec<em class="filename">\</em><tt class="literal">test</tt>,
1288as shown in <a href="ch03.html#samba2-CHP-3-FIG-34">Figure 3-34</a>, and use your
1289server's hostname instead of
1290&quot;toltec&quot;.</p>
1291
1292<div class="figure"><a name="samba2-CHP-3-FIG-34"/><img src="figs/sam2_0334.gif"/></div><h4 class="head4">Figure 3-34. Opening a shared directory, using the server's NetBIOS name in the UNC</h4>
1293
1294<p>This will work even if browsing services are not set up right, which
1295is a common problem. You can also work around a name-service problem
1296by entering the server's IP Address (such as
1297172.16.1.1 in our example) instead of the Samba
1298server's hostname, as shown in <a href="ch03.html#samba2-CHP-3-FIG-35">Figure 3-35</a>. Go back and check your configuration, and if
1299things still aren't right, go to <a href="ch12.html#samba2-CHP-12-SECT-2">Section 12.2</a> to troubleshoot what is wrong with the
1300network.</p>
1301
1302<div class="figure"><a name="samba2-CHP-3-FIG-35"/><img src="figs/sam2_0335.gif"/></div><h4 class="head4">Figure 3-35. Opening a shared directory, using the server's IP address in the UNC</h4>
1303
1304<p>If it works, congratulations! Try copying files to and from the
1305server by dragging their icons to and from the folder on the Samba
1306share. You might be pleasantly surprised how seamlessly everything
1307works. <a name="INDEX-109"/></p>
1308
1309
1310</div>
1311
1312
1313</div>
1314
1315
1316
1317<div class="sect1"><a name="samba2-CHP-3-SECT-4"/>
1318
1319<h2 class="head1">Setting Up Windows 2000 Computers</h2>
1320
1321<p><a name="INDEX-110"/>Although
1322Windows 2000 is based on NT technology and is similar to Windows NT
1323in many respects, configuring it for use with Samba is quite
1324different.</p>
1325
1326<p>You should perform the following steps as the
1327<tt class="literal">Administrator</tt> or another user in the
1328<tt class="literal">Administrators</tt> group.</p>
1329
1330
1331<div class="sect2"><a name="samba2-CHP-3-SECT-4.1"/>
1332
1333<h3 class="head2">Networking Components</h3>
1334
1335<p><a name="INDEX-111"/><a name="INDEX-112"/>Go to the Control Panel and
1336double-click the Network and Dial-up Connections icon. You should see
1337at least one Local Area Connection icon. If there is more than one,
1338identify the one that corresponds to the network adapter that is
1339connected to your Samba network. Right-click the Local Area
1340Connection icon, and click the Properties button. (Or double-click
1341the Local Area Connection icon, and then click the Properties button
1342in the dialog box that comes up.) You should now be looking at the
1343Local Area Connection Properties dialog box, as shown in <a href="ch03.html#samba2-CHP-3-FIG-36">Figure 3-36</a>.</p>
1344
1345<div class="figure"><a name="samba2-CHP-3-FIG-36"/><img src="figs/sam2_0336.gif"/></div><h4 class="head4">Figure 3-36. Windows 2000 Local Area Connection Properties dialog</h4>
1346
1347<p>First of all, you might want to click the Configure button under the
1348field for the network adapter, to make sure you see the message
1349&quot;This device is working properly&quot;
1350in the Device status window. If there is a problem, make sure to
1351correct it before continuing. You should also see the message
1352&quot;Use this device (enable)&quot; in the
1353Device usage field of the dialog box. Make sure to set it this way if
1354it is not already. Click OK or Cancel to get back to the Local Area
1355Connection Properties dialog box.</p>
1356
1357<p>You should see at least the following two components:</p>
1358
1359<ul><li>
1360<p>Client for Microsoft Networks</p>
1361</li><li>
1362<p>Internet Protocol (TCP/IP)</p>
1363</li></ul>
1364<p>If you do not see either Client for Microsoft Networks or Internet
1365Protocol (TCP/IP) in your list, you will need to add them. For
1366either, the method is to click the Install... button, click the type
1367of component (Client or Protocol), and then click the Add... button.
1368Next, click the component you want to add, and click the OK button.
1369You should see the component added to the list with the others.</p>
1370
1371<p>Some components should be removed if you see them in the list:</p>
1372
1373<ul><li>
1374<p>NetBEUI Protocol</p>
1375</li><li>
1376<p>NWLink NetBIOS</p>
1377</li><li>
1378<p>NWLink IPX/SPX/NetBIOS Compatible Transport Protocol</p>
1379</li><li>
1380<p>Client Service for Netware</p>
1381</li></ul>
1382<p>If you see anything other than TCP/IP listed as a protocol, and it is
1383not a protocol that you need, you can remove it. Uninstall NetBEUI,
1384unless you are sure you need it, and the other three if you do not
1385need to support Netware. If you try to remove a protocol and get an
1386error message saying that the protocol is being used by another
1387service, you need to remove that service before you can remove the
1388protocol. For example, to remove the NWLink IPX/SPX Compatible
1389Transport Protocol, you would need to remove the Client Service for
1390Netware first.</p>
1391
1392<p>To remove a component, click the component in the list, click the
1393Uninstall button, and then click Yes in the dialog box that pops up.
1394In some cases, Windows might need to reboot to put the change into
1395effect.</p>
1396
1397
1398</div>
1399
1400
1401<div class="sect2"><a name="samba2-CHP-3-SECT-4.2"/>
1402
1403<h3 class="head2">Bindings</h3>
1404
1405<p><a name="INDEX-113"/><a name="INDEX-114"/>Next to each
1406client, service, or protocol listed in the window in the Local Area
1407Connections Properties dialog box, you will see a checkbox. Make sure
1408the checkbox is checked for both Client for Microsoft Networks and
1409Internet Protocol (TCP/IP). The check marks indicate the networking
1410components are bound to the network adapter shown at the top of the
1411dialog box.</p>
1412
1413
1414</div>
1415
1416
1417<div class="sect2"><a name="samba2-CHP-3-SECT-4.3"/>
1418
1419<h3 class="head2">Configuring TCP/IP</h3>
1420
1421<p><a name="INDEX-115"/><a name="INDEX-116"/>Now click Internet Protocol (TCP/IP),
1422and then click Properties to open the Internet Protocol (TCP/IP)
1423Properties dialog box, shown in <a href="ch03.html#samba2-CHP-3-FIG-37">Figure 3-37</a>.</p>
1424
1425<div class="figure"><a name="samba2-CHP-3-FIG-37"/><img src="figs/sam2_0337.gif"/></div><h4 class="head4">Figure 3-37. Internet Protocol (TCP/IP) Properties dialog</h4>
1426
1427
1428<div class="sect3"><a name="samba2-CHP-3-SECT-4.3.1"/>
1429
1430<h3 class="head3">IP address</h3>
1431
1432<p><a name="INDEX-117"/><a name="INDEX-118"/>If
1433you are using DHCP on your network to assign IP addresses
1434dynamically, select the &quot;Obtain IP address
1435automatically&quot; radio button. Otherwise, select the
1436&quot;Use the following address:&quot; radio
1437button, and fill in the computer's IP address and
1438netmask in the spaces provided. You or your network manager should
1439have selected an address for the client on the same subnet (LAN) as
1440the Samba server. For example, if the server's
1441address is 172.16.1.1 and its network mask is 255.255.255.0, you
1442might use the address 172.16.1.14, if it is available, along with the
1443same netmask. You can also fill in the IP address of the default
1444gateway.</p>
1445
1446
1447</div>
1448
1449
1450
1451<div class="sect3"><a name="samba2-CHP-3-SECT-4.3.2"/>
1452
1453<h3 class="head3">DNS server</h3>
1454
1455<p><a name="INDEX-119"/><a name="INDEX-120"/>In
1456the lower part of the dialog box, click the &quot;Use the
1457following DNS server addresses:&quot; radio button, and
1458fill in the IP address of your DNS server.</p>
1459
1460<p>Now click the Advanced... button to bring up the Advanced TCP/IP
1461Settings dialog box, and then click the WINS tab.</p>
1462
1463
1464</div>
1465
1466
1467
1468<div class="sect3"><a name="samba2-CHP-3-SECT-4.3.3"/>
1469
1470<h3 class="head3">WINS server</h3>
1471
1472<p><a name="INDEX-121"/><a name="INDEX-122"/>Enter the
1473address of your WINS server in the space labeled
1474&quot;WINS addresses, in order of use:&quot;.
1475If your Samba server is providing WINS service (in other words, you
1476have the line <tt class="literal">wins</tt> <tt class="literal">service</tt>
1477<tt class="literal">=</tt> <tt class="literal">yes</tt> in the
1478<em class="emphasis">smb.conf</em> file of your Samba server), provide the
1479Samba server's IP address here. Otherwise, provide
1480the address of another WINS server on your network.</p>
1481
1482<p>Near the bottom of the dialog box, select the radio button labeled
1483&quot;Enable NetBIOS over TCP/IP&quot;. <a href="ch03.html#samba2-CHP-3-FIG-38">Figure 3-38</a> shows what your Advanced TCP/IP Settings
1484dialog box should look like at this point.</p>
1485
1486<div class="figure"><a name="samba2-CHP-3-FIG-38"/><img src="figs/sam2_0338.gif"/></div><h4 class="head4">Figure 3-38. Advanced TCP/IP Settings dialog, showing WINS tab</h4>
1487
1488
1489</div>
1490
1491
1492
1493<div class="sect3"><a name="samba2-CHP-3-SECT-4.3.4"/>
1494
1495<h3 class="head3">The LMHOSTS file</h3>
1496
1497<p>If you want to install an
1498<em class="filename">LMHOSTS</em><a name="INDEX-123"/><a name="INDEX-124"/> file,
1499it must be placed in the <em class="filename">\system32\drivers\etc</em>
1500directory under your Windows installation directory (usually
1501<em class="filename">C:\WINNT</em> ). The easy way to make sure it gets to
1502the proper location is to use the Import LMHOSTS... button on the
1503WINS Address tab. (But if you want to do it over the network, you
1504will have to do that after file sharing is configured!) Remember to
1505click the Enable LMHOSTS Lookup checkbox on the WINS Address tab to
1506enable this functionality.</p>
1507
1508<p>When you are satisfied with your settings for IP Address, WINS
1509Address, and DNS, click the OK buttons in each open dialog box to
1510complete the configuration. Windows might need to load some files
1511from the Windows 2000 distribution CD-ROM, and you might need to
1512reboot for your changes to take effect.</p>
1513
1514
1515</div>
1516
1517
1518</div>
1519
1520
1521<div class="sect2"><a name="samba2-CHP-3-SECT-4.4"/>
1522
1523<h3 class="head2">Computer and Workgroup Names</h3>
1524
1525<p><a name="INDEX-125"/><a name="INDEX-126"/><a name="INDEX-127"/><a name="INDEX-128"/>From
1526the Control Panel, double-click the System icon to open the System
1527Properties dialog box. Click the Network Identification tab, and your
1528System Properties dialog box will look similar to <a href="ch03.html#samba2-CHP-3-FIG-39">Figure 3-39</a>.</p>
1529
1530<div class="figure"><a name="samba2-CHP-3-FIG-39"/><img src="figs/sam2_0339.gif"/></div><h4 class="head4">Figure 3-39. System Properties dialog, showing Network Identification tab</h4>
1531
1532<p>To give your system computer a name and a workgroup, click the
1533Properties button, which will bring up the Identification Changes
1534dialog box, as in <a href="ch03.html#samba2-CHP-3-FIG-40">Figure 3-40</a>.</p>
1535
1536<div class="figure"><a name="samba2-CHP-3-FIG-40"/><img src="figs/sam2_0340.gif"/></div><h4 class="head4">Figure 3-40. Identification Changes dialog</h4>
1537
1538<p>You need to identify your computer with a name and change the
1539workgroup to the one you specified in the
1540<em class="emphasis">smb.conf</em> file of your Samba server.
1541Don't worry that Windows forces the computer name
1542and the workgroup to be all capital letters; it's
1543smart enough to figure out what you mean when it connects to the
1544network.</p>
1545
1546<p>Click the More... button to bring up the DNS Suffix and NetBIOS
1547Computer Name dialog box, shown in <a href="ch03.html#samba2-CHP-3-FIG-41">Figure 3-41</a>.</p>
1548
1549<div class="figure"><a name="samba2-CHP-3-FIG-41"/><img src="figs/sam2_0341.gif"/></div><h4 class="head4">Figure 3-41. DNS Suffix and NetBIOS Computer Name dialog</h4>
1550
1551<p>Enter the DNS domain name of this computer in the text field labeled
1552Primary DNS Suffix for this computer:, and then click OK. You should
1553now see the FQDN of this system underneath the label
1554&quot;Full computer name:&quot;. Click the OK
1555button and then reboot when requested to put your configuration
1556changes into effect. Once again, log in using your administrative
1557account.</p>
1558<a name="samba2-CHP-3-NOTE-96"/><blockquote class="note"><h4 class="objtitle">WARNING</h4>
1559<p>There have been reports of authentication problems with Samba when a
1560username on a Windows 2000 system is the same as its computer name.</p>
1561</blockquote>
1562
1563
1564</div>
1565
1566
1567<div class="sect2"><a name="samba2-CHP-3-SECT-4.5"/>
1568
1569<h3 class="head2">Adding a Samba-Enabled User</h3>
1570
1571<p><a name="INDEX-129"/><a name="INDEX-130"/>So far,
1572you have been logged into your Windows 2000 system as a user in the
1573<tt class="literal">Administrators</tt> group. To access resources on the
1574Samba server, you will need a username and password that the Samba
1575server recognizes as valid. If your administrative account has such a
1576username and password, you can use it, but you might want to access
1577your system and the network from a nonadministrative user account
1578instead.</p>
1579<a name="samba2-CHP-3-NOTE-97"/><blockquote class="note"><h4 class="objtitle">WARNING</h4>
1580<p>The directions in this section assume that your network is set up as
1581a workgroup. If you have already set up your network as a domain, as
1582we describe in <a href="ch04.html">Chapter 4</a>, you do not need to
1583follow the instructions here for adding a local user on the Windows
15842000 client system. Simply log on to the domain from the client using
1585a username and password in Samba's
1586<em class="filename">smbpasswd</em> account database, and continue with
1587the next section, <a href="ch03.html#samba2-CHP-3-SECT-4.6">Section 3.4.6</a>.</p>
1588</blockquote>
1589
1590<p>To add a new user, open the Control Panel, and double-click the Users
1591and Passwords icon to open the Users and Passwords dialog box, shown
1592in <a href="ch03.html#samba2-CHP-3-FIG-42">Figure 3-42</a>.</p>
1593
1594<div class="figure"><a name="samba2-CHP-3-FIG-42"/><img src="figs/sam2_0342.gif"/></div><h4 class="head4">Figure 3-42. Users and Passwords dialog</h4>
1595
1596<p>The first thing to do is make sure the checkbox labeled
1597&quot;Users must enter a user name and password to use
1598this computer.&quot; is checked. Next, click the Add...
1599button to bring up the first dialog box of the User Wizard, shown in
1600<a href="ch03.html#samba2-CHP-3-FIG-43">Figure 3-43</a>.</p>
1601
1602<div class="figure"><a name="samba2-CHP-3-FIG-43"/><img src="figs/sam2_0343.gif"/></div><h4 class="head4">Figure 3-43. Adding a new user</h4>
1603
1604<p>Fill out the fields, using the username of a valid user account on
1605the Samba host, and then click the Next &gt; button to enter and
1606confirm the user's password. This password must be
1607the same as the user's password on the Samba host.
1608If you are using encrypted passwords, make sure this username and
1609password are the same as what you used when you ran the
1610<em class="emphasis">smbpasswd</em> program. Click the Next &gt; button,
1611which brings up the final dialog box, shown in <a href="ch03.html#samba2-CHP-3-FIG-44">Figure 3-44</a>.</p>
1612
1613<div class="figure"><a name="samba2-CHP-3-FIG-44"/><img src="figs/sam2_0344.gif"/></div><h4 class="head4">Figure 3-44. Specifying a group for the new user</h4>
1614
1615<p>Pick a group for the user (the default Standard User should do), and
1616click the Finish button. You should now see your new account added to
1617the list in the Users and Passwords dialog box. Click the OK button
1618to complete the process.</p>
1619
1620<p>Now return to the Users and Passwords control panel window, click the
1621Advanced tab, then click on the Advanced button. Click the Users
1622folder in the left side of the Local Users and Groups window that
1623appears, and then double-click the account you just added in the
1624right side of the window. In the Properties window that opens, click
1625the checkbox labeled Password never expires. You are done! Click the
1626OK buttons in all the dialog boxes, and close all open windows.</p>
1627
1628<p>Open the Start menu, select Shut Down, and select Log off
1629<em class="emphasis">username</em> from the drop-down menu. Click the OK
1630button, then log on with the username and password you just added.</p>
1631
1632
1633</div>
1634
1635
1636<div class="sect2"><a name="samba2-CHP-3-SECT-4.6"/>
1637
1638<h3 class="head2">Connecting to the Samba Server</h3>
1639
1640<p>Now for the big moment. Your Samba server is running, and you have
1641set up your <a name="INDEX-131"/><a name="INDEX-132"/>Windows 2000 client to communicate with
1642it. Double-click the My Network Places icon on the desktop, and then
1643double-click the Computers Near Me icon to browse the workgroup. You
1644should see your Samba server listed as a member of the workgroup, as
1645shown in <a href="ch03.html#samba2-CHP-3-FIG-45">Figure 3-45</a>.</p>
1646
1647<div class="figure"><a name="samba2-CHP-3-FIG-45"/><img src="figs/sam2_0345.gif"/></div><h4 class="head4">Figure 3-45. The Computers Near Me window, showing computers in the workgroup</h4>
1648
1649<p>Double-clicking the server name will show the resources that the
1650server is offering to the network, as shown in <a href="ch03.html#samba2-CHP-3-FIG-46">Figure 3-46</a>.</p>
1651
1652<div class="figure"><a name="samba2-CHP-3-FIG-46"/><img src="figs/sam2_0346.gif"/></div><h4 class="head4">Figure 3-46. Shares offered by the Toltec server</h4>
1653
1654<p>In this case, the <em class="filename">test</em> directory and the default
1655printer are offered to the Windows 2000 workstation. If you
1656don't see the server listed, don't
1657panic. Select Run from the Start menu. A dialog box appears that
1658allows you to type the name of your server and its share directory in
1659Windows format. For example, you would enter
1660<em class="filename">\\toltec\</em><tt class="literal">test</tt>, as shown in
1661<a href="ch03.html#samba2-CHP-3-FIG-47">Figure 3-47</a>, and use your server's
1662hostname instead of &quot;toltec&quot;.</p>
1663
1664<div class="figure"><a name="samba2-CHP-3-FIG-47"/><img src="figs/sam2_0347.gif"/></div><h4 class="head4">Figure 3-47. Opening a shared directory, using the server's NetBIOS name in the UNC</h4>
1665
1666<p>This will work even if browsing services are not set up right, which
1667is a common problem. You can also work around a name-service problem
1668by entering the server's IP address (such as
1669172.16.1.1 in our example) instead of the Samba
1670server's hostname, as shown in <a href="ch03.html#samba2-CHP-3-FIG-48">Figure 3-48</a>.</p>
1671
1672<div class="figure"><a name="samba2-CHP-3-FIG-48"/><img src="figs/sam2_0348.gif"/></div><h4 class="head4">Figure 3-48. Opening a shared directory, using the server's IP address in the UNC</h4>
1673
1674<p>If things still aren't right, go directly to <a href="ch12.html#samba2-CHP-12-SECT-2">Section 12.2</a> to troubleshoot what is wrong
1675with the network.</p>
1676
1677<p>If it works, congratulations! Try copying files to and from the
1678server. You will be pleasantly surprised how seamlessly everything
1679works. Now that you've finished setting up the Samba
1680server and its clients, you can proceed to the next chapter.
1681<a name="INDEX-133"/></p>
1682
1683
1684</div>
1685
1686
1687</div>
1688
1689
1690
1691<div class="sect1"><a name="samba2-CHP-3-SECT-5"/>
1692
1693<h2 class="head1">Setting Up Windows XP Computers</h2>
1694
1695<p>Although <a name="INDEX-134"/>Windows XP
1696is very similar to Windows 2000, it has a very different user
1697interface, and there are a number of subtle differences. For example,
1698getting to the Control Panel is different than in any previous
1699version of Windows&mdash;one must click the Control Panel item from
1700the Start menu (there is no Settings item in the Start menu in XP).
1701By default, XP will display the Control Panel in Category View mode.
1702If you see this, click the Switch to Classic View item in the
1703upper-left corner of the window. All of our directions are for using
1704the Control Panel in Classic View mode.</p>
1705
1706<p>You should perform the following steps as the
1707<tt class="literal">Administrator</tt> or another user in the
1708Administrators group.</p>
1709
1710
1711<div class="sect2"><a name="samba2-CHP-3-SECT-5.1"/>
1712
1713<h3 class="head2">Networking Components</h3>
1714
1715<p><a name="INDEX-135"/><a name="INDEX-136"/>Go to the Control Panel and
1716double-click the Network and Dial-up Connections icon. You should see
1717at least one Local Area Connection icon. If there is more than one,
1718identify the one that corresponds to the network adapter that is
1719connected to your Samba network. Right-click the Local Area
1720Connection icon and click the Properties button. (Or double-click the
1721Local Area Connection icon and then click the Properties button in
1722the dialog box that comes up.) You should now be looking at the Local
1723Area Connection Properties dialog box, as shown in <a href="ch03.html#samba2-CHP-3-FIG-49">Figure 3-49</a>.</p>
1724
1725<div class="figure"><a name="samba2-CHP-3-FIG-49"/><img src="figs/sam2_0349.gif"/></div><h4 class="head4">Figure 3-49. The Local Area Connection Properties dialog</h4>
1726
1727<p>First of all, you might want to click the Configure button under the
1728field for the network adapter to make sure you see the message
1729&quot;This device is working properly&quot;
1730in the Device status window. If there is a problem, make sure to
1731correct it before continuing. You should also see the message
1732&quot;Use this device (enable)&quot; in the
1733Device usage field of the dialog box. Make sure to set it this way if
1734it is not already. Click OK or Cancel to close this dialog box, then
1735reopen the Local Area Connection Properties dialog box.</p>
1736
1737<p>You should see at least the following two components:</p>
1738
1739<ul><li>
1740<p>Client for Microsoft Networks</p>
1741</li><li>
1742<p>Internet Protocol (TCP/IP)</p>
1743</li></ul>
1744<p>If you do not see either Client for Microsoft Networks or Internet
1745Protocol (TCP/IP) in your list, you will need to add them. For
1746either, the method is to click the Install... button, click the type
1747of component (Client or Protocol), and then click the Add... button.
1748Next, click the component you want to add, and click the OK button.
1749You should see the component added to the list with the others.</p>
1750
1751<p>If you see anything other than TCP/IP listed as a protocol, and it is
1752not a protocol that you need, you can remove it. If NetBEUI appears
1753in the list, uninstall it if you possibly can. Also uninstall any
1754Netware-related components if you do not need to support Netware. If
1755you try to remove a protocol and get an error message saying that the
1756protocol is being used by another service, you need to remove that
1757service before you can remove the protocol. For example, to remove
1758the NWLink IPX/SPX Compatible Transport Protocol, you would need to
1759remove the Client Service for Netware first.</p>
1760
1761<p>To remove a component, click the component in the list, click the
1762Uninstall button, and then click Yes in the dialog box that pops up.
1763In some cases, Windows might need to reboot to put the change into
1764effect.</p>
1765
1766
1767<div class="sect3"><a name="samba2-CHP-3-SECT-5.1.1"/>
1768
1769<h3 class="head3">Bindings</h3>
1770
1771<p><a name="INDEX-137"/><a name="INDEX-138"/>Next to each client, service, or protocol
1772listed in the window in the Local Area Connections Properties dialog
1773box, you will see a checkbox. Make sure the checkbox is checked for
1774both Client for Microsoft Networks and Internet Protocol (TCP/IP).
1775The check marks indicate that the networking components are bound to
1776the network adapter shown at the top of the dialog box.</p>
1777
1778
1779</div>
1780
1781
1782</div>
1783
1784
1785<div class="sect2"><a name="samba2-CHP-3-SECT-5.2"/>
1786
1787<h3 class="head2">Configuring TCP/IP</h3>
1788
1789<p><a name="INDEX-139"/><a name="INDEX-140"/>Now click Internet Protocol
1790(TCP/IP) and then click Properties to open the Internet Protocol
1791(TCP/IP) Properties dialog box, shown in <a href="ch03.html#samba2-CHP-3-FIG-50">Figure 3-50</a>.</p>
1792
1793<div class="figure"><a name="samba2-CHP-3-FIG-50"/><img src="figs/sam2_0350.gif"/></div><h4 class="head4">Figure 3-50. The Internet Protocol (TCP/IP) Properties dialog</h4>
1794
1795
1796<div class="sect3"><a name="samba2-CHP-3-SECT-5.2.1"/>
1797
1798<h3 class="head3">IP address</h3>
1799
1800<p><a name="INDEX-141"/><a name="INDEX-142"/>If
1801you are using DHCP on your network to assign IP addresses
1802dynamically, select the &quot;Obtain IP address
1803automatically&quot; radio button. Otherwise, select the
1804&quot;Use the following address:&quot; radio
1805button, and fill in the computer's IP address and
1806netmask in the spaces provided. You or your network manager should
1807have selected an address for the client on the same subnet (LAN) as
1808the Samba server. For example, if the server's
1809address is 172.16.1.1 and its network mask is 255.255.255.0, you
1810might use the address 172.16.1.12 (if it is available) along with the
1811same netmask. You can also fill in the IP address of the default
1812gateway.</p>
1813
1814
1815</div>
1816
1817
1818
1819<div class="sect3"><a name="samba2-CHP-3-SECT-5.2.2"/>
1820
1821<h3 class="head3">DNS server</h3>
1822
1823<p><a name="INDEX-143"/><a name="INDEX-144"/>In the lower part of the dialog box, click
1824the &quot;Use the following DNS server
1825addresses:&quot; radio button, and fill in the IP address
1826of your DNS server.</p>
1827
1828<p>Now click the Advanced... button to bring up the Advanced TCP/IP
1829Settings dialog box, and then click the WINS tab.</p>
1830
1831
1832</div>
1833
1834
1835
1836<div class="sect3"><a name="samba2-CHP-3-SECT-5.2.3"/>
1837
1838<h3 class="head3">WINS server</h3>
1839
1840<p><a name="INDEX-145"/><a name="INDEX-146"/>Enter
1841the address of your WINS server in the space labeled
1842&quot;WINS addresses, in order of use:&quot;.
1843If your Samba server is providing WINS service (in other words, you
1844have the line <tt class="literal">wins</tt> <tt class="literal">support</tt>
1845<tt class="literal">=</tt> <tt class="literal">yes</tt> in the
1846<em class="emphasis">smb.conf</em> file of your Samba server), provide the
1847Samba server's IP address here. Otherwise, provide
1848the address of another WINS server on your network.</p>
1849
1850<p>Near the bottom of the dialog box, select the radio button labeled
1851Enable NetBIOS over TCP/IP. <a href="ch03.html#samba2-CHP-3-FIG-51">Figure 3-51</a> shows what
1852your Advanced TCP/IP Settings dialog box should look like at this
1853point.</p>
1854
1855<div class="figure"><a name="samba2-CHP-3-FIG-51"/><img src="figs/sam2_0351.gif"/></div><h4 class="head4">Figure 3-51. The Advanced TCP/IP Settings dialog, showing the WINS tab</h4>
1856
1857
1858</div>
1859
1860
1861
1862<div class="sect3"><a name="samba2-CHP-3-SECT-5.2.4"/>
1863
1864<h3 class="head3">The LMHOSTS file</h3>
1865
1866<p>If you want to install an
1867<em class="filename">LMHOSTS</em><a name="INDEX-147"/><a name="INDEX-148"/> file, it
1868must be placed in the <em class="filename">\system32\drivers\etc</em>
1869directory under your Windows installation directory (usually
1870<em class="filename">C:\WINNT</em> ). The easy way to make sure it gets to
1871the proper location is to use the Import LMHOSTS... button on the
1872WINS Address tab. (But if you want to do it over the network, you
1873will have to do that after file sharing is configured!) Remember to
1874click the Enable LMHOSTS Lookup checkbox on the WINS Address tab to
1875enable this functionality.</p>
1876
1877<p>When you are satisfied with your settings for IP Address, WINS
1878Address, and DNS, click the OK buttons in each open dialog box (and
1879the Close button in the Local Area Connection Properties dialog box)
1880to complete the configuration. Windows might need to load some files
1881from the Windows XP distribution CD-ROM, and you might need to reboot
1882for your changes to take effect.</p>
1883
1884
1885</div>
1886
1887
1888</div>
1889
1890
1891<div class="sect2"><a name="samba2-CHP-3-SECT-5.3"/>
1892
1893<h3 class="head2">Computer and Workgroup Names</h3>
1894
1895<p><a name="INDEX-149"/><a name="INDEX-150"/><a name="INDEX-151"/><a name="INDEX-152"/>From the
1896Control Panel, double-click the System icon to open the System
1897Properties dialog box. Click the Computer Name tab, and your System
1898Properties dialog box will look similar to <a href="ch03.html#samba2-CHP-3-FIG-52">Figure 3-52</a>.</p>
1899
1900<div class="figure"><a name="samba2-CHP-3-FIG-52"/><img src="figs/sam2_0352.gif"/></div><h4 class="head4">Figure 3-52. The System Properties dialog, showing the Computer Name tab</h4>
1901
1902<p>To give your system computer a name and a workgroup, click the
1903Change... button, which will bring up the Computer Name Changes
1904dialog box, as in <a href="ch03.html#samba2-CHP-3-FIG-53">Figure 3-53</a>.</p>
1905
1906<div class="figure"><a name="samba2-CHP-3-FIG-53"/><img src="figs/sam2_0353.gif"/></div><h4 class="head4">Figure 3-53. The Computer Name Changes dialog</h4>
1907
1908<p>You need to identify your computer with a name and change the
1909workgroup to the one you specified in the
1910<em class="emphasis">smb.conf</em> file of your Samba server.
1911Don't worry that Windows forces the workgroup to be
1912all capital letters; it's smart enough to figure out
1913what you mean when it connects to the network.</p>
1914
1915<p>Click the More... button to bring up the DNS Suffix and NetBIOS
1916Computer Name dialog box, shown in <a href="ch03.html#samba2-CHP-3-FIG-54">Figure 3-54</a>.</p>
1917
1918<div class="figure"><a name="samba2-CHP-3-FIG-54"/><img src="figs/sam2_0354.gif"/></div><h4 class="head4">Figure 3-54. The DNS Suffix and NetBIOS Computer Name dialog</h4>
1919
1920<p>Enter the DNS domain name of this computer in the text field labeled
1921Primary DNS Suffix for this computer:, and then click OK. You should
1922now see the FQDN of this system underneath the label Full computer
1923name: in the Computer Name Changes dialog box. Click the OK button
1924and then reboot when requested to put your configuration changes into
1925effect. Once again, log in using your administrative account.</p>
1926<a name="samba2-CHP-3-NOTE-98"/><blockquote class="note"><h4 class="objtitle">WARNING</h4>
1927<p>There have been reports of authentication problems with Samba when a
1928username on a Windows XP system is the same as its computer name.</p>
1929</blockquote>
1930
1931
1932</div>
1933
1934
1935<div class="sect2"><a name="samba2-CHP-3-SECT-5.4"/>
1936
1937<h3 class="head2">Adding a Samba-Enabled User</h3>
1938
1939<p><a name="INDEX-153"/><a name="INDEX-154"/>So far,
1940you have been logged into your Windows XP system as a user in the
1941Administrators group. To access resources on the Samba server, you
1942will need to have a username and password that the Samba server
1943recognizes as valid. If your administrative account has such a
1944username and password, you can use it, but you might want to access
1945your system and the network from a nonadministrative user account
1946instead.</p>
1947
1948<a name="samba2-CHP-3-NOTE-99"/><blockquote class="note"><h4 class="objtitle">TIP</h4>
1949<p>The directions in this section assume that your network is set up as
1950a workgroup. If you have already set up your network as a domain, as
1951we describe in <a href="ch04.html">Chapter 4</a>, you do not need to
1952follow the instructions here for adding a local user on the Windows
1953XP client system. Simply log on to the domain from the client using a
1954username and password in Samba's
1955<em class="filename">smbpasswd</em> account database, and continue with
1956the next section, <a href="ch03.html#samba2-CHP-3-SECT-5.5">Section 3.5.5</a>.</p>
1957</blockquote>
1958
1959<p>To add a new user, open the Control Panel, and double-click the Users
1960Accounts icon to open the User Accounts window, shown in <a href="ch03.html#samba2-CHP-3-FIG-55">Figure 3-55</a>.</p>
1961
1962<div class="figure"><a name="samba2-CHP-3-FIG-55"/><img src="figs/sam2_0355.gif"/></div><h4 class="head4">Figure 3-55. The User Accounts window</h4>
1963
1964<p>Click the Create a new account task, which will bring up the window
1965shown in <a href="ch03.html#samba2-CHP-3-FIG-56">Figure 3-56</a>. Enter the username, then click
1966the Next &gt; button.</p>
1967
1968<div class="figure"><a name="samba2-CHP-3-FIG-56"/><img src="figs/sam2_0356.gif"/></div><h4 class="head4">Figure 3-56. Entering the username</h4>
1969
1970<p>Click the radio button labeled
1971&quot;Limited&quot;, as shown in <a href="ch03.html#samba2-CHP-3-FIG-57">Figure 3-57</a>.</p>
1972
1973<p>Click the Create Account button, and you will see the username you
1974added next to a picture at the bottom of the User Accounts window. We
1975still need to assign a password to the account. Click the account to
1976bring up the &quot;What do you want to change about
1977<em class="emphasis">username</em>'s
1978account?&quot; window, and then click Create a password.
1979Enter the password, and enter it again to confirm it.</p>
1980
1981<div class="figure"><a name="samba2-CHP-3-FIG-57"/><img src="figs/sam2_0357.gif"/></div><h4 class="head4">Figure 3-57. Setting the account type</h4>
1982
1983<p>This password must be the same as the user's
1984password on the Samba host. If you are using encrypted passwords,
1985make sure this username and password are the same as what you used
1986when you ran the <em class="emphasis">smbpasswd</em> program. Click the
1987Create Password button, and you're done adding the
1988account.</p>
1989
1990<p>Now open the Start menu and click the Log Off button. In the Log Off
1991Windows dialog box that pops up, again click the Log Off button. When
1992Windows displays the login screen, click the user you just added, and
1993type in the password to log in.</p>
1994
1995
1996</div>
1997
1998
1999<div class="sect2"><a name="samba2-CHP-3-SECT-5.5"/>
2000
2001<h3 class="head2">Connecting to the Samba Server</h3>
2002
2003<p><a name="INDEX-155"/><a name="INDEX-156"/>Now for
2004the big moment. Your Samba server is running, and you have set up
2005your Windows XP client to communicate with it. In the Start menu,
2006select My Computer<a name="FNPTR-9"/><a href="#FOOTNOTE-9">[9]</a> to open the My Computer window. Click My
2007Network Places, in the Other Places box in the left part of the
2008window. You should see a folder icon for the
2009<em class="filename">test</em> directory, as shown in <a href="ch03.html#samba2-CHP-3-FIG-58">Figure 3-58</a>.</p>
2010
2011<div class="figure"><a name="samba2-CHP-3-FIG-58"/><img src="figs/sam2_0358.gif"/></div><h4 class="head4">Figure 3-58. The My Network Places window</h4>
2012
2013<p>Now click View workgroup computers in the Network Tasks box at the
2014left of the window. You should see your Samba server listed as a
2015member of the workgroup. Double-click its icon, and you will see a
2016window that looks like <a href="ch03.html#samba2-CHP-3-FIG-59">Figure 3-59</a>.</p>
2017
2018<div class="figure"><a name="samba2-CHP-3-FIG-59"/><img src="figs/sam2_0359.gif"/></div><h4 class="head4">Figure 3-59. Shares offered by the Toltec server</h4>
2019
2020<p>If you don't see the server listed in the workgroup,
2021don't panic. Select Run... from the Start menu. A
2022dialog box appears that allows you to type the name of your server
2023and its share directory in Windows format. For example, you would
2024enter <em class="filename">\\toltec\</em><tt class="literal">test</tt>, as shown
2025in <a href="ch03.html#samba2-CHP-3-FIG-60">Figure 3-60</a>, and use your
2026server's hostname instead of
2027&quot;toltec&quot;.</p>
2028
2029<div class="figure"><a name="samba2-CHP-3-FIG-60"/><img src="figs/sam2_0360.gif"/></div><h4 class="head4">Figure 3-60. Opening a shared directory, using the server's NetBIOS name in the UNC</h4>
2030
2031<p>This will work even if browsing services are not set up right, which
2032is a common problem. You can also work around a name-service problem
2033by entering the server's IP Address (such as
2034172.16.1.1 in our example) instead of the Samba
2035server's hostname, as shown in <a href="ch03.html#samba2-CHP-3-FIG-61">Figure 3-61</a>.</p>
2036
2037<div class="figure"><a name="samba2-CHP-3-FIG-61"/><img src="figs/sam2_0361.gif"/></div><h4 class="head4">Figure 3-61. Opening a shared directory, using the server's IP address in the UNC</h4>
2038
2039<p>If things still aren't right, go directly to <a href="ch12.html#samba2-CHP-12-SECT-2">Section 12.2</a> to troubleshoot what is wrong
2040with the network.</p>
2041
2042<p>If it works, congratulations! Try copying files to and from the
2043server by dragging their icons to and from the Samba
2044server's <em class="filename">test</em> folder. You might
2045be pleasantly surprised how seamlessly everything works. <a name="INDEX-157"/> <a name="INDEX-158"/></p>
2046
2047
2048</div>
2049
2050
2051</div>
2052
2053<hr/><h4 class="head4">Footnotes</h4><blockquote><a name="FOOTNOTE-1"/> <p><a href="#FNPTR-1">[1]</a> We are
2054intentionally omitting device drivers because they are
2055hardware-specific, and we assume you are getting installation
2056directions from the manufacturer.</p> <a name="FOOTNOTE-2"/>
2057<p><a href="#FNPTR-2">[2]</a> Make sure to use the same netmask as all other systems on the
2058network. You can find the netmask in use by checking with Unix or
2059Windows systems that have already been configured.</p> <a name="FOOTNOTE-3"/> <p><a href="#FNPTR-3">[3]</a> Keep in mind that IP addresses ending
2060in .0 are reserved for network addresses and that ones ending in .255
2061are for broadcast addresses. These should never be assigned to any
2062system on the network.</p> <a name="FOOTNOTE-4"/> <p><a href="#FNPTR-4">[4]</a> To be more explicit about
2063this, the system will identify itself to the network as a b-node
2064rather than an h-node.</p> <a name="FOOTNOTE-5"/> <p><a href="#FNPTR-5">[5]</a> We put the
2065names of the <em class="filename">LMHOSTS</em> and
2066<em class="filename">HOSTS</em> files in uppercase for additional
2067clarity&mdash;to remind you that we are referring to the files on
2068Windows rather than on Unix, and because that's the
2069way we see them in other books on Windows. The case of the letters in
2070the two names actually does not matter.</p> <a name="FOOTNOTE-6"/> <p><a href="#FNPTR-6">[6]</a> The address 127.0.0.1 is known as the
2071<em class="emphasis">localhost</em> address and always refers to itself.
2072For example, if you type <tt class="literal">ping</tt>
2073<tt class="literal">127.0.0.1</tt> on a Unix server, you should always get
2074a response, because you're pinging the host
2075itself.</p> <a name="FOOTNOTE-7"/> <p><a href="#FNPTR-7">[7]</a> This update is supplied in
2076various update packages issued by Microsoft.</p> <a name="FOOTNOTE-8"/> <p><a href="#FNPTR-8">[8]</a> Notice how in Windows NT,
2077some clients are called &quot;services&quot;!
2078In these directions, we will conform to Microsoft's
2079terminology.</p> <a name="FOOTNOTE-9"/> <p><a href="#FNPTR-9">[9]</a> If there is a My Network Places
2080item in the Start menu at this point, you can save yourself a little
2081time and just click that. If you don't see it,
2082don't worry; it will appear automatically
2083later.</p> </blockquote>
2084
2085<hr/><h4 class="head4"><a href="toc.html">TOC</a></h4>
2086</body></html>
Note: See TracBrowser for help on using the repository browser.