1<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�8.�MS Windows Network Configuration Guide</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.66.1"><link rel="start" href="index.html" title="The Official Samba-3 HOWTO and Reference Guide"><link rel="up" href="type.html" title="Part�II.�Server Configuration Basics"><link rel="prev" href="StandAloneServer.html" title="Chapter�7.�Stand-alone Servers"><link rel="next" href="optional.html" title="Part�III.�Advanced Configuration"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�8.�MS Windows Network Configuration Guide</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="StandAloneServer.html">Prev</a>�</td><th width="60%" align="center">Part�II.�Server Configuration Basics</th><td width="20%" align="right">�<a accesskey="n" href="optional.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="ClientConfig"></a>Chapter�8.�MS Windows Network Configuration Guide</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:jht@samba.org">jht@samba.org</a>></tt></p></div></div></div></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="ClientConfig.html#id2544351">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="ClientConfig.html#id2544376">Technical Details</a></span></dt><dd><dl><dt><span class="sect2"><a href="ClientConfig.html#id2544405">TCP/IP Configuration</a></span></dt><dt><span class="sect2"><a href="ClientConfig.html#id2545727">Joining a Domain: Windows 2000/XP Professional</a></span></dt><dt><span class="sect2"><a href="ClientConfig.html#id2546176">Domain Logon Configuration: Windows 9x/Me</a></span></dt></dl></dd><dt><span class="sect1"><a href="ClientConfig.html#id2546508">Common Errors</a></span></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2544351"></a>Features and Benefits</h2></div></div></div><p> 2Occasionally network administrators will report difficulty getting Microsoft Windows clients to interoperate 3correctly with Samba servers. It would appear that some folks just can not accept the fact that the right way 4to configure MS Windows network client is precisely as one would do when using Microsoft Windows NT4 or 200x 5servers. Yet there is repetitious need to provide detailed Windows client configuration instructions. 6</p><p> 7The purpose of this chapter is to graphically illustrate MS Windows client configuration for the most common 8critical aspects of such configuration. An experienced network administrator will not be interested in the 9details of this chapter. 10</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2544376"></a>Technical Details</h2></div></div></div><p> 11This chapter discusses TCP/IP protocol configuration as well as network membership for the platforms 12that are in common use today. These are: 13</p><div class="itemizedlist"><ul type="disc"><li><p> 14 Microsoft Windows XP Professional. 15 </p></li><li><p> 16 Windows 2000 Professional. 17 </p></li><li><p> 18 Windows Millennium edition (Me). 19 </p></li></ul></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2544405"></a>TCP/IP Configuration</h3></div></div></div><p> 20 The builder of a house must ensure that all construction takes place on a firm foundation. 21 The same is true of TCP/IP-based networking. Fundamental network configuration problems 22 will plague all network users until they are resolved. 23 </p><p> 24 Microsoft Windows workstations and servers can be configured either with fixed 25 IP addresses or via DHCP. The examples that follow demonstrate the use of DHCP 26 and make only passing reference to those situations where fixed IP configuration 27 settings can be effected. 28 </p><p> 29 It is possible to use shortcuts or abbreviated keystrokes to arrive at a 30 particular configuration screen. The decision was made to base all examples in this 31 chapter on use of the <span class="guibutton">Start</span> button. 32 </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2544439"></a>MS Windows XP Professional</h4></div></div></div><p> 33 There are two paths to the Windows XP TCP/IP configuration panel. Choose the access method that you prefer: 34 </p><p> 35 Click <span class="guimenu">Start -> Control Panel -> Network Connections</span> 36 </p><p> 37 <span class="emphasis"><em>Alternately,</em></span> click <span class="guimenu">Start -></span>, and right click <span class="guimenu">My Network Places</span> 38 then select <span class="guimenuitem">Properties</span> 39 </p><p> 40 The following procedure steps through the Windows XP Professional TCP/IP configuration process: 41 </p><div class="procedure"><ol type="1"><li><p> 42 On some installations the interface will be called <span class="guimenu">Local Area Connection</span> and 43 on others it will be called <span class="guimenu">Network Bridge</span>. On our system it is called <span class="guimenu">Network Bridge</span>. 44 Right click on <span class="guimenu">Network Bridge -> Properties</span>. See <a href="ClientConfig.html#WXPP002" title="Figure�8.1.�Network Bridge Configuration.">???</a>. 45 </p><div class="figure"><a name="WXPP002"></a><p class="title"><b>Figure�8.1.�Network Bridge Configuration.</b></p><div class="mediaobject"><img src="images/WXPP002.png" alt="Network Bridge Configuration."></div></div><p> 46 </p></li><li><p> 47 The Network Bridge Configuration, or Local Area Connection, panel is used to set TCP/IP protocol settings. 48 In <span class="guimenuitem">This connection uses the following items:</span> box, 49 click on <span class="guimenu">Internet Protocol (TCP/IP)</span>, then click the on <span class="guibutton">Properties</span>. 50 </p><p> 51 The default setting is DHCP enabled operation. 52 (i.e., “<span class="quote"><span class="emphasis"><em>Obtain an IP address automatically</em></span></span>”). See <a href="ClientConfig.html#WXPP003" title="Figure�8.2.�Internet Protocol (TCP/IP) Properties.">???</a>. 53 </p><div class="figure"><a name="WXPP003"></a><p class="title"><b>Figure�8.2.�Internet Protocol (TCP/IP) Properties.</b></p><div class="mediaobject"><img src="images/WXPP003.png" alt="Internet Protocol (TCP/IP) Properties."></div></div><p> 54 </p><p> 55 Many network administrators will want to use DHCP to configure all client TCP/IP 56 protocol stack settings. (For information on how to configure the ISC DHCP server 57 for Microsoft Windows client support see, <a href="DNSDHCP.html#DHCP" title="DHCP Server">???</a>. 58 </p><p> 59 If it is necessary to provide a fixed IP address, click on “<span class="quote"><span class="emphasis"><em>Use the following IP address</em></span></span>” and proceed to enter the 60 IP Address, the subnet mask, and the default gateway address in the boxes provided. 61 </p></li><li><p> 62 Click the <span class="guibutton">Advanced</span> button to proceed with TCP/IP configuration. 63 This opens a panel in which it is possible to create additional IP Addresses for this interface. 64 The technical name for the additional addresses is <span class="emphasis"><em>IP Aliases</em></span>, and additionally this 65 panel permits the setting of more default gateways (routers). In most cases where DHCP is used, it will not be 66 necessary to create additional settings. See <a href="ClientConfig.html#WXPP005" title="Figure�8.3.�Advanced Network Settings">???</a> to see the appearance of this panel. 67 </p><div class="figure"><a name="WXPP005"></a><p class="title"><b>Figure�8.3.�Advanced Network Settings</b></p><div class="mediaobject"><img src="images/WXPP005.png" alt="Advanced Network Settings"></div></div><p> 68 </p><p> 69 Fixed settings may be required for DNS and WINS if these settings are not provided automatically via DHCP. 70 </p></li><li><p> 71 Click the <span class="guimenu">DNS</span> tab to add DNS server settings. 72 The example system uses manually configured DNS settings. When finished making changes, click the <span class="guibutton">OK</span> to commit 73 the settings. See <a href="ClientConfig.html#WXPP014" title="Figure�8.4.�DNS Configuration.">???</a>. 74 </p><div class="figure"><a name="WXPP014"></a><p class="title"><b>Figure�8.4.�DNS Configuration.</b></p><div class="mediaobject"><img src="images/WXPP014.png" alt="DNS Configuration."></div></div><p> 75 </p></li><li><p> 76 Click the <span class="guibutton">WINS</span> tab to add manual WINS server entries. 77 This step demonstrates an example system that uses manually configured WINS settings. 78 When finished making, changes click the <span class="guibutton">OK</span> to commit 79 the settings. See <a href="ClientConfig.html#WXPP009" title="Figure�8.5.�WINS Configuration">???</a>. 80 </p><div class="figure"><a name="WXPP009"></a><p class="title"><b>Figure�8.5.�WINS Configuration</b></p><div class="mediaobject"><img src="images/WXPP009.png" alt="WINS Configuration"></div></div><p> 81 </p></li></ol></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2544906"></a>MS Windows 2000</h4></div></div></div><p> 82 There are two paths to the Windows 2000 Professional TCP/IP configuration panel. Choose the access method that you prefer: 83 </p><p> 84 Click <span class="guimenu">Start -> Control Panel -> Network and Dial-up Connections</span> 85 </p><p> 86 <span class="emphasis"><em>Alternately,</em></span> click on <span class="guimenu">Start</span>, then right click <span class="guimenu">My Network Places</span> and 87 select <span class="guimenuitem">Properties</span>. 88 </p><p> 89 The following procedure steps through the Windows XP Professional TCP/IP configuration process: 90 </p><div class="procedure"><ol type="1"><li><p> 91 Right click on <span class="guimenu">Local Area Connection</span>, now click the 92 <span class="guimenuitem">Properties</span>. See <a href="ClientConfig.html#w2kp001" title="Figure�8.6.�Local Area Connection Properties.">???</a>. 93 </p><div class="figure"><a name="w2kp001"></a><p class="title"><b>Figure�8.6.�Local Area Connection Properties.</b></p><div class="mediaobject"><img src="images/w2kp001.png" alt="Local Area Connection Properties."></div></div><p> 94 </p></li><li><p> 95 The Local Area Connection Properties is used to set TCP/IP protocol settings. Click on <span class="guimenu">Internet Protocol (TCP/IP)</span> in the 96 <span class="guimenuitem">Components checked are used by this connection:</span> box, then click the <span class="guibutton">Properties</span> button. 97 </p></li><li><p> 98 The default setting is DHCP enabled operation. 99 (i.e., “<span class="quote"><span class="emphasis"><em>Obtain an IP address automatically</em></span></span>”). See <a href="ClientConfig.html#w2kp002" title="Figure�8.7.�Internet Protocol (TCP/IP) Properties.">???</a>. 100 </p><div class="figure"><a name="w2kp002"></a><p class="title"><b>Figure�8.7.�Internet Protocol (TCP/IP) Properties.</b></p><div class="mediaobject"><img src="images/w2kp002.png" alt="Internet Protocol (TCP/IP) Properties."></div></div><p> 101 </p><p> 102 Many network administrators will want to use DHCP to configure all client TCP/IP 103 protocol stack settings. (For information on how to configure the ISC DHCP server 104 for Microsoft Windows client support, see <a href="DNSDHCP.html#DHCP" title="DHCP Server">???</a>. 105 </p><p> 106 If it is necessary to provide a fixed IP address, click on “<span class="quote"><span class="emphasis"><em>Use the following IP address</em></span></span>” and proceed to enter the 107 IP Address, the subnet mask, and the default gateway address in the boxes provided. 108 For this example we are assuming that all network clients will be configured using DHCP. 109 </p></li><li><p> 110 Click the <span class="guimenu">Advanced</span> button to proceed with TCP/IP configuration. 111 Refer to <a href="ClientConfig.html#w2kp003" title="Figure�8.8.�Advanced Network Settings.">???</a>. 112 </p><div class="figure"><a name="w2kp003"></a><p class="title"><b>Figure�8.8.�Advanced Network Settings.</b></p><div class="mediaobject"><img src="images/w2kp003.png" alt="Advanced Network Settings."></div></div><p> 113 </p><p> 114 Fixed settings may be required for DNS and WINS if these settings are not provided automatically via DHCP. 115 </p></li><li><p> 116 Click the <span class="guimenu">DNS</span> tab to add DNS server settings. 117 The example system uses manually configured DNS settings. When finished making changes, 118 click on <span class="guibutton">OK</span> to commit the settings. See <a href="ClientConfig.html#w2kp004" title="Figure�8.9.�DNS Configuration.">???</a>. 119 </p><div class="figure"><a name="w2kp004"></a><p class="title"><b>Figure�8.9.�DNS Configuration.</b></p><div class="mediaobject"><img src="images/w2kp004.png" alt="DNS Configuration."></div></div><p> 120 </p></li><li><p> 121 Click the <span class="guibutton">WINS</span> tab to add manual WINS server entries. 122 This step demonstrates an example system that uses manually configured WINS settings. 123 When finished making changes, click on <span class="guibutton">OK</span> to commit the settings. 124 See <a href="ClientConfig.html#w2kp005" title="Figure�8.10.�WINS Configuration.">???</a>. 125 </p><div class="figure"><a name="w2kp005"></a><p class="title"><b>Figure�8.10.�WINS Configuration.</b></p><div class="mediaobject"><img src="images/w2kp005.png" alt="WINS Configuration."></div></div><p> 126 </p></li></ol></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2545351"></a>MS Windows Me</h4></div></div></div><p> 127 There are two paths to the Windows Millennium edition (Me) TCP/IP configuration panel. Choose the access method that you prefer: 128 </p><p> 129 Click <span class="guimenu">Start -> Control Panel -> Network Connections</span> 130 </p><p> 131 <span class="emphasis"><em>Alternately,</em></span> click on <span class="guimenu">Start -></span>, and right click on <span class="guimenu">My Network Places</span> 132 then select <span class="guimenuitem">Properties</span>. 133 </p><p> 134 The following procedure steps through the Windows Me TCP/IP configuration process: 135 </p><div class="procedure"><ol type="1"><li><p> 136 In the box labeled <span class="guimenuitem">The following network components are installed:</span>, 137 click on <span class="guimenu">Internet Protocol TCP/IP</span>, now click on the <span class="guibutton">Properties</span> button. See <a href="ClientConfig.html#WME001" title="Figure�8.11.�The Windows Me Network Configuration Panel.">???</a>. 138 </p><div class="figure"><a name="WME001"></a><p class="title"><b>Figure�8.11.�The Windows Me Network Configuration Panel.</b></p><div class="mediaobject"><img src="images/WME001.png" alt="The Windows Me Network Configuration Panel."></div></div><p> 139 </p></li><li><p> 140 Many network administrators will want to use DHCP to configure all client TCP/IP 141 protocol stack settings. (For information on how to configure the ISC DHCP server 142 for Microsoft Windows client support see, <a href="DNSDHCP.html#DHCP" title="DHCP Server">???</a>. 143 The default setting on Microsoft Windows Me workstations is for DHCP enabled operation, 144 i.e., <span class="guimenu">Obtain IP address automatically</span> is enabled. See <a href="ClientConfig.html#WME002" title="Figure�8.12.�IP Address.">???</a>. 145 </p><div class="figure"><a name="WME002"></a><p class="title"><b>Figure�8.12.�IP Address.</b></p><div class="mediaobject"><img src="images/WME002.png" alt="IP Address."></div></div><p> 146 </p><p> 147 If it is necessary to provide a fixed IP address, click on <span class="guimenuitem">Specify an IP address</span> and proceed to enter the 148 IP Address and the subnet mask in the boxes provided. For this example we are assuming that all network clients will be configured using DHCP. 149 </p></li><li><p> 150 Fixed settings may be required for DNS and WINS if these settings are not provided automatically via DHCP. 151 </p></li><li><p> 152 If necessary, click the <span class="guimenu">DNS Configuration</span> tab to add DNS server settings. 153 Click the <span class="guibutton">WINS Configuration</span> tab to add WINS server settings. 154 The <span class="guimenu">Gateway</span> tab allows additional gateways (router addresses) to be added to the network 155 interface settings. In most cases where DHCP is used, it will not be necessary to 156 create these manual settings. 157 </p></li><li><p> 158 The following example uses manually configured WINS settings. See <a href="ClientConfig.html#WME005" title="Figure�8.13.�DNS Configuration.">???</a>. 159 When finished making changes, click on <span class="guibutton">OK</span> to commit the settings. 160 </p><div class="figure"><a name="WME005"></a><p class="title"><b>Figure�8.13.�DNS Configuration.</b></p><div class="mediaobject"><img src="images/WME005.png" alt="DNS Configuration."></div></div><p> 161 </p><p> 162 This is an example of a system that uses manually configured WINS settings. One situation where 163 this might apply is on a network that has a single DHCP server that provides settings for multiple 164 Windows workgroups or domains. See <a href="ClientConfig.html#WME003" title="Figure�8.14.�WINS Configuration.">???</a>. 165 </p><div class="figure"><a name="WME003"></a><p class="title"><b>Figure�8.14.�WINS Configuration.</b></p><div class="mediaobject"><img src="images/WME003.png" alt="WINS Configuration."></div></div><p> 166 </p></li></ol></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2545727"></a>Joining a Domain: Windows 2000/XP Professional</h3></div></div></div><p> 167 Microsoft Windows NT/200x/XP Professional platforms can participate in Domain Security. 168 This section steps through the process for making a Windows 200x/XP Professional machine a 169 member of a Domain Security environment. It should be noted that this process is identical 170 when joining a domain that is controlled by Windows NT4/200x as well as a Samba PDC. 171 </p><div class="procedure"><ol type="1"><li><p> 172 Click <span class="guimenu">Start</span>. 173 </p></li><li><p> 174 Right click <span class="guimenu">My Computer</span>, then select <span class="guimenuitem">Properties</span>. 175 </p></li><li><p> 176 The opening panel is the same one that can be reached by clicking <span class="guimenu">System</span> on the Control Panel. 177 See <a href="ClientConfig.html#wxpp001" title="Figure�8.15.�The General Panel.">???</a>. 178 </p><div class="figure"><a name="wxpp001"></a><p class="title"><b>Figure�8.15.�The General Panel.</b></p><div class="mediaobject"><img src="images/wxpp001.png" alt="The General Panel."></div></div><p> 179 </p></li><li><p> 180 Click the <span class="guimenu">Computer Name</span> tab. 181 This panel shows the <span class="guimenuitem">Computer Description</span>, the <span class="guimenuitem">Full computer name</span>, 182 and the <span class="guimenuitem">Workgroup</span> or <span class="guimenuitem">Domain name</span>. 183 </p><p> 184 Clicking the <span class="guimenu">Network ID</span> button will launch the configuration wizard. Do not use this with 185 Samba-3. If you wish to change the computer name, join or leave the domain, click the <span class="guimenu">Change</span> button. 186 See <a href="ClientConfig.html#wxpp004" title="Figure�8.16.�The Computer Name Panel.">???</a>. 187 </p><div class="figure"><a name="wxpp004"></a><p class="title"><b>Figure�8.16.�The Computer Name Panel.</b></p><div class="mediaobject"><img src="images/wxpp004.png" alt="The Computer Name Panel."></div></div><p> 188 </p></li><li><p> 189 Click on <span class="guimenu">Change</span>. This panel shows that our example machine (TEMPTATION) is in a workgroup called WORKGROUP. 190 We will join the domain called MIDEARTH. See <a href="ClientConfig.html#wxpp006" title="Figure�8.17.�The Computer Name Changes Panel.">???</a>. 191 </p><div class="figure"><a name="wxpp006"></a><p class="title"><b>Figure�8.17.�The Computer Name Changes Panel.</b></p><div class="mediaobject"><img src="images/wxpp006.png" alt="The Computer Name Changes Panel."></div></div><p> 192 </p></li><li><p> 193 Enter the name <span class="guimenu">MIDEARTH</span> in the field below the Domain radio button. 194 </p><p> 195 This panel shows that our example machine (TEMPTATION) is set to join the domain called MIDEARTH. See <a href="ClientConfig.html#wxpp007" title="Figure�8.18.�The Computer Name Changes Panel Domain MIDEARTH.">???</a>. 196 </p><div class="figure"><a name="wxpp007"></a><p class="title"><b>Figure�8.18.�The Computer Name Changes Panel Domain MIDEARTH.</b></p><div class="mediaobject"><img src="images/wxpp007.png" alt="The Computer Name Changes Panel Domain MIDEARTH."></div></div><p> 197 </p></li><li><p> 198 Now click the <span class="guimenu">OK</span> button. A dialog box should appear to allow you to provide the credentials (username and password) 199 of a Domain administrative account that has the rights to add machines to the Domain. 200 </p><p> 201 Enter the name “<span class="quote"><span class="emphasis"><em>root</em></span></span>” and the root password from your Samba-3 server. See <a href="ClientConfig.html#wxpp008" title="Figure�8.19.�Computer Name Changes User name and Password Panel.">???</a>. 202 </p><div class="figure"><a name="wxpp008"></a><p class="title"><b>Figure�8.19.�Computer Name Changes User name and Password Panel.</b></p><div class="mediaobject"><img src="images/wxpp008.png" alt="Computer Name Changes User name and Password Panel."></div></div><p> 203 </p></li><li><p> 204 Click on <span class="guimenu">OK</span>. 205 </p><p> 206 The “<span class="quote"><span class="emphasis"><em>Welcome to the MIDEARTH domain.</em></span></span>” dialog box should appear. At this point the machine must be rebooted. 207 Joining the domain is now complete. 208 </p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2546176"></a>Domain Logon Configuration: Windows 9x/Me</h3></div></div></div><p> 209 We follow the convention used by most in saying that Windows 9x/Me machines can participate in Domain logons. The truth is 210 that these platforms can use only the LanManager network logon protocols. 211 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> 212 Windows XP Home edition cannot participate in Domain or LanManager network logons. 213 </p></div><div class="procedure"><ol type="1"><li><p> 214 Right click on the <span class="guimenu">Network Neighborhood</span> icon. 215 </p></li><li><p> 216 The Network Configuration Panel allows all common network settings to be changed. 217 See <a href="ClientConfig.html#WME009" title="Figure�8.20.�The Network Panel.">???</a>. 218 </p><div class="figure"><a name="WME009"></a><p class="title"><b>Figure�8.20.�The Network Panel.</b></p><div class="mediaobject"><img src="images/WME009.png" alt="The Network Panel."></div></div><p> 219 </p><p> 220 Make sure that the <span class="guimenu">Client for Microsoft Networks</span> driver is installed as shown. 221 Click on the <span class="guimenu">Client for Microsoft Networks</span> entry in <span class="guimenu">The following network 222 components are installed:</span> box. Then click the <span class="guibutton">Properties</span> button. 223 </p></li><li><p> 224 The Client for Microsoft Networks Properties panel is the correct location to configure network logon 225 settings. See <a href="ClientConfig.html#WME010" title="Figure�8.21.�Client for Microsoft Networks Properties Panel.">???</a>. 226 </p><div class="figure"><a name="WME010"></a><p class="title"><b>Figure�8.21.�Client for Microsoft Networks Properties Panel.</b></p><div class="mediaobject"><img src="images/WME010.png" alt="Client for Microsoft Networks Properties Panel."></div></div><p> 227 </p><p> 228 Enter the Windows NT domain name, check the <span class="guimenu">Log on to Windows NT domain</span> box, 229 click <span class="guimenu">OK</span>. 230 </p></li><li><p> 231 Click on the <span class="guimenu">Identification</span> button. This is the location at which the workgroup 232 (domain) name and the machine name (computer name) need to be set. See <a href="ClientConfig.html#WME013" title="Figure�8.22.�Identification Panel.">???</a>. 233 </p><div class="figure"><a name="WME013"></a><p class="title"><b>Figure�8.22.�Identification Panel.</b></p><div class="mediaobject"><img src="images/WME013.png" alt="Identification Panel."></div></div><p> 234 </p></li><li><p> 235 Now click the <span class="guimenu">Access Control</span> button. If you want to be able to assign share access 236 permissions using domain user and group accounts, it is necessary to enable 237 <span class="guimenu">User-level access control</span> as shown in this panel. See <a href="ClientConfig.html#WME014" title="Figure�8.23.�Identification Panel.">???</a>. 238 </p><div class="figure"><a name="WME014"></a><p class="title"><b>Figure�8.23.�Identification Panel.</b></p><div class="mediaobject"><img src="images/WME014.png" alt="Identification Panel."></div></div><p> 239 </p></li></ol></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2546508"></a>Common Errors</h2></div></div></div><p> 240The most common errors that can afflict Windows networking systems include: 241</p><div class="itemizedlist"><ul type="disc"><li><p>Incorrect IP address.</p></li><li><p>Incorrect or inconsistent netmasks.</p></li><li><p>Incorrect router address.</p></li><li><p>Incorrect DNS server address.</p></li><li><p>Incorrect WINS server address.</p></li><li><p>Use of a Network Scope setting watch out for this one!</p></li></ul></div><p> 242The most common reasons for which a Windows NT/200x/XP Professional client cannot join the Samba controlled domain are: 243</p><div class="itemizedlist"><ul type="disc"><li><p><tt class="filename">smb.conf</tt> does not have correct <a class="indexterm" name="id2546570"></a>add machine script settings.</p></li><li><p>“<span class="quote"><span class="emphasis"><em>root</em></span></span>” account is not in password backend database.</p></li><li><p>Attempt to use a user account instead of the “<span class="quote"><span class="emphasis"><em>root</em></span></span>” account to join a machine to the domain.</p></li><li><p>Open connections from the workstation to the server.</p></li><li><p>Firewall or filter configurations in place on either the client or on the Samba server.</p></li></ul></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="StandAloneServer.html">Prev</a>�</td><td width="20%" align="center"><a accesskey="u" href="type.html">Up</a></td><td width="40%" align="right">�<a accesskey="n" href="optional.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter�7.�Stand-alone Servers�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Part�III.�Advanced Configuration</td></tr></table></div></body></html> 244
