Table of Contents
Occasionally network administrators report difficulty getting Microsoft Windows clients to interoperate correctly with Samba servers. It seems that some folks just cannot accept the fact that the right way to configure an MS Windows network client is precisely as one would do when using MS Windows NT4 or 200x servers. Yet there is repetitious need to provide detailed Windows client configuration instructions.
The purpose of this chapter is to graphically illustrate MS Windows client configuration for the most common critical aspects of such configuration. An experienced network administrator will not be interested in the details of this chapter.
This chapter discusses TCP/IP protocol configuration as well as network membership for the platforms that are in common use today. These are:
Microsoft Windows XP Professional
Windows 2000 Professional
Windows Millennium edition (Me)
The builder of a house must ensure that all construction takes place on a firm foundation. The same is true for the builder of a TCP/IP-based networking system. Fundamental network configuration problems will plague all network users until they are resolved.
MS Windows workstations and servers can be configured either with fixed IP addresses or via DHCP. The examples that follow demonstrate the use of DHCP and make only passing reference to those situations where fixed IP configuration settings can be effected.
It is possible to use shortcuts or abbreviated keystrokes to arrive at a particular configuration screen. The decision was made to base all examples in this chapter on use of the button.
There are two paths to the Windows XP TCP/IP configuration panel. Choose the access method that you prefer:
Click .
Alternately, click , and right-click then select .
The following procedure steps through the Windows XP Professional TCP/IP configuration process:
On some installations the interface will be called and on others it will be called . On our system it is called . Right-click on . See “Network Bridge Configuration.”.
The Network Bridge Configuration, or Local Area Connection, panel is used to set TCP/IP protocol settings. In box, click on , then click on .
The default setting is DHCP-enabled operation (i.e., “Obtain an IP address automatically”). See “Internet Protocol (TCP/IP) Properties.”.
Many network administrators will want to use DHCP to configure all client TCP/IP protocol stack settings. (For information on how to configure the ISC DHCP server for Windows client support see the DNS and DHCP Configuration Guide, DHCP Server.
If it is necessary to provide a fixed IP address, click on “Use the following IP address” and enter the IP Address, the subnet mask, and the default gateway address in the boxes provided.
Click the button to proceed with TCP/IP configuration. This opens a panel in which it is possible to create additional IP addresses for this interface. The technical name for the additional addresses is IP aliases, and additionally this panel permits the setting of more default gateways (routers). In most cases where DHCP is used, it will not be necessary to create additional settings. See “Advanced Network Settings” to see the appearance of this panel.
Fixed settings may be required for DNS and WINS if these settings are not provided automatically via DHCP.
Click the tab to add DNS server settings. The example system uses manually configured DNS settings. When finished making changes, click the to commit the settings. See “DNS Configuration.”.
Click the tab to add manual WINS server entries. This step demonstrates an example system that uses manually configured WINS settings. When finished making changes, click to commit the settings. See “WINS Configuration”.
There are two paths to the Windows 2000 Professional TCP/IP configuration panel. Choose the access method that you prefer:
Click .
Alternatively, click , then right-click , and select .
The following procedure steps through the Windows XP Professional TCP/IP configuration process:
Right-click on , then click . See “Local Area Connection Properties.”.
The Local Area Connection Properties is used to set TCP/IP protocol settings. Click on in the box, then click the button.
The default setting is DHCP-enabled operation (i.e., “Obtain an IP address automatically”). See “Internet Protocol (TCP/IP) Properties.”.
Many network administrators will want to use DHCP to configure all client TCP/IP protocol stack settings. (For information on how to configure the ISC DHCP server for Windows client support, see, “DHCP Server”.
If it is necessary to provide a fixed IP address, click on “Use the following IP address” and enter the IP Address, the subnet mask, and the default gateway address in the boxes provided. For this example we are assuming that all network clients will be configured using DHCP.
Click the button to proceed with TCP/IP configuration. Refer to “Advanced Network Settings.”.
Fixed settings may be required for DNS and WINS if these settings are not provided automatically via DHCP.
Click the tab to add DNS server settings. The example system uses manually configured DNS settings. When finished making changes, click to commit the settings. See “DNS Configuration.”.
Click the tab to add manual WINS server entries. This step demonstrates an example system that uses manually configured WINS settings. When finished making changes, click to commit the settings. See “WINS Configuration.”.
There are two paths to the Windows Millennium edition (Me) TCP/IP configuration panel. Choose the access method that you prefer:
Click .
Alternatively, click on , and right click on then select .
The following procedure steps through the Windows Me TCP/IP configuration process:
In the box labeled , click on , then click on the button. See “The Windows Me Network Configuration Panel.”.
Many network administrators will want to use DHCP to configure all client TCP/IP protocol stack settings. (For information on how to configure the ISC DHCP server for Windows client support see the DNS and DHCP Configuration Guide, DHCP Server. The default setting on Windows Me workstations is for DHCP-enabled operation (i.e., is enabled). See “IP Address.”.
If it is necessary to provide a fixed IP address, click on and enter the 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.
Fixed settings may be required for DNS and WINS if these settings are not provided automatically via DHCP.
If necessary, click the tab to add DNS server settings. Click the tab to add WINS server settings. The tab allows additional gateways (router addresses) to be added to the network interface settings. In most cases where DHCP is used, it will not be necessary to create these manual settings.
The following example uses manually configured WINS settings. See “DNS Configuration.”. When finished making changes, click to commit the settings.
This is an example of a system that uses manually configured WINS settings. One situation where this might apply is on a network that has a single DHCP server that provides settings for multiple Windows workgroups or domains. See “WINS Configuration.”.
Microsoft Windows NT/200x/XP Professional platforms can participate in domain security. This section steps through the process for making a Windows 200x/XP Professional machine a member of a domain security environment. It should be noted that this process is identical when joining a domain that is controlled by Windows NT4/200x as well as a Samba PDC.
Click .
Right-click , then select .
The opening panel is the same one that can be reached by clicking on the Control Panel. See “The General Panel.”.
Click the tab. This panel shows the , the , and the or .
Clicking the button will launch the configuration wizard. Do not use this with Samba-3. If you wish to change the computer name or join or leave the domain, click the button. See “The Computer Name Panel.”.
Click on . This panel shows that our example machine (TEMPTATION) is in a workgroup called WORKGROUP. We will join the domain called MIDEARTH. See “The Computer Name Changes Panel.”.
Enter the name in the field below the domain radio button.
This panel shows that our example machine (TEMPTATION) is set to join the domain called MIDEARTH. See “The Computer Name Changes Panel Domain MIDEARTH.”.
Now click the button. A dialog box should appear to allow you to provide the credentials (username and password) of a domain administrative account that has the rights to add machines to the domain.
Enter the name “root” and the root password from your Samba-3 server. See “Computer Name Changes Username and Password Panel.”.
Click on .
The “Welcome to the MIDEARTH domain.” dialog box should appear. At this point the machine must be rebooted. Joining the domain is now complete.
We follow the convention used by most in saying that Windows 9x/Me machines can participate in domain logons. The truth is that these platforms can use only the LanManager network logon protocols.
Right-click on the icon.
The Network Configuration Panel allows all common network settings to be changed. See “The Network Panel.”.
Make sure that the driver is installed as shown. Click on the entry in box. Then click the button.
The Client for Microsoft Networks Properties panel is the correct location to configure network logon settings. See “Client for Microsoft Networks Properties Panel.”.
Enter the Windows NT domain name, check the box, and click .
Click on the button. This is the location at which the workgroup (domain) name and the machine name (computer name) need to be set. See “Identification Panel.”.
Now click the button. If you want to be able to assign share access permissions using domain user and group accounts, it is necessary to enable as shown in this panel. See “Access Control Panel.”.
The most common errors that can afflict Windows networking systems include:
Incorrect IP address.
Incorrect or inconsistent netmasks.
Incorrect router address.
Incorrect DNS server address.
Incorrect WINS server address.
Use of a Network Scope setting watch out for this one!
The most common reasons for which a Windows NT/200x/XP Professional client cannot join the Samba controlled domain are:
smb.confdoes not have correct add machine script settings.“root” account is not in password backend database.
Attempt to use a user account instead of the “root” account to join a machine to the domain.
Open connections from the workstation to the server.
Firewall or filter configurations in place on either the client or the Samba server.