Program/Course : Computer System Servicing NC II

Unit of Competency : Set-up Computer Networks

Module : Set Network Configuration

TCP/IP Configuration

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 Start button.

For Windows XP:

Step 1
Click Start->Control Panel->select and double click Network and internet connections->select
and double click Network Connections.

Step 2
Double-click the Local Area Connection icon; highlight Internet Protocol (TCP/IP) tab in the Local
Area Connection Properties window that appears:
Step 3
Double click it or click Properties. The TCP/IP Properties window will display.

Step 4
Now you have two ways to configure the TCP/IP protocol below:
1. Assigned by DHCP Sever
Select Obtain an IP address automatically and Obtain DNS Server address automatically, as
shown in the figure below. These may be selected by default. Then click OK to save setting.

2. Assigned manually
1) Select Use the following IP address, as shown in the following figure.
If the router’s LAN IP address is 192.168.1.1, please type in IP address 192.168.1.x （x is from 2
to 253）, subnet mask 255.255.255.0, and default gateway 192.168.1.1.

2) Select Use the following DNS server addresses, as shown in the following figure. And then
type the DNS server IP address, which should be provided by your ISP. Finally remember to
click OK to save settings.
Note: In most cases, type your local area DNS server IP addresses into it.
The Preferred DNS server is same to default gateway. For Secondary DNS server, you could leave
it blank or type in 8.8.8.8.

Step 5
Click OK to save and apply your settings.

For Windows Vista & Windows 7

Step 1
Click on windows key+ R key on the keyboard at the same time.

Step 2
Type ncpa.cpl in the box, then press OK.
Step 3
Select the local area connection, right click it and select Properties.

Step 4
Select Internet Protocol Version 4(TCP/IPv4), double click it or click Properties.
Step 5
There are two ways to configure the TCP/IP Properties, Assigned by DHCP server
automatically or manually.
1. Assigned by DHCP server
Select Obtain an IP address automatically and Obtain DNS server address automatically. If
necessary, then click OK to save the settings.
2. Assigned manually
1) Select Use the following IP address, type IP address, subnet mask and default gateway IP
address into it.
If the router’s LAN IP address is 192.168.1.1, please type in IP address 192.168.1.x （x is from 2
to 253）, subnet mask 255.255.255.0, and default gateway 192.168.1.1.

2) Select Use the following DNS server addresses, as shown in the following figure. And then
type the DNS server IP address, which should be provided by your ISP. If necessary, then
click OK to save the settings.

Note: In most cases, type your local area DNS server IP addresses into it.
The Preferred DNS server is same to default gateway. For Secondary DNS server, you could leave
it blank or type in 8.8.8.8.
Step 6
Click OK to save and apply your settings.

Joining a Domain: Windows 2000/XP Professional

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.

1. Click Start.
2. Right-click My Computer, then select Properties.
3. The opening panel is the same one that can be reached by clicking System on the Control
Panel. See “The General Panel.”.
 Figure 8.15. The General Panel.

4. Click the Computer Name tab. This panel shows the Computer Description, the Full
computer name, and the Workgroup or Domain name.

Clicking the Network ID 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
Change button. See “The Computer Name Panel.”.
 Figure 8.16. The Computer Name Panel.

5. Click on Change. 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.”.
 Figure 8.17. The Computer Name Changes Panel.

6. Enter the name MIDEARTH 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.”.

Figure 8.18. The Computer Name Changes Panel Domain MIDEARTH.

7. Now click the OK 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.”.

Figure 8.19. Computer Name Changes Username and Password Panel.

 8. Click on OK.

The “Welcome to the MIDEARTH domain.” dialog box should appear. At this point the
machine must be rebooted. Joining the domain is now complete.

Common Errors

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.conf does 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.