Installing TCP/IP

TCP/IP is installed automatically when the Windows Server 2003 setup process runs. It is not usually necessary to install TCP/IP after the Windows Server 2003 setup process completed.

The instances when you might need to manually install TCP/IP are listed below:

  • TCP/IP was disabled when the Windows Server 2003 setup process executed.
  • TCP/IP was uninstalled from the computer.

How to install the TCP/IP protocol suite

  1. Click Start, Control Panel, and then click Network Connections
  2. In the Network Connections window, right-click the network connection for which you want to install TCP/IP and then click Properties from the shortcut menu.
  3. If you are working with the local area connection, you will use the General tab in the following step. If you are working with any other connection, you will use the Networking tab
  4. Click Install, and then click Protocol.
  5. Click Add to open the Select Network Protocol dialog box.
  6. Click Internet Protocol (TCP/IP) in the dialog box.
  7. Click OK
  8. Confirm that the Internet Protocol (TCP/IP) checkbox is enabled.

Manually Assigning IP Addresses

When you manually assign IP addresses, you assign a particular IP address to a TCP/IP host or client. This statically assigned IP address only changes via a manual configuration.

You would normally manually assign IP addresses under the following conditions:

  • There are no configured DHCP servers on the network and the network haves multiple network segments.
  • You are configuring a computer as a DHCP server, and need to assign that computer a static IP addresses.
  • You are configuring computers as important network servers such as domain controllers, or DNS servers. You would manually assign the IP address to these computers.

When you configure the properties of the TCP/IP protocol using the properties of a particular network connection, you can perform the following tasks:

  • Assign an IP address and subnet mask
  • Assign the default gateway
  • Assign DNS servers and WINS servers.

How to manually assign IP Addresses to TCP/IP hosts or clients

  1. Click Start, Control Panel, and then click Network Connections.
  2. Right-click the network connection you want to work with, and then click Properties from the shortcut menu.
  3. If you working with the local area connection, you will use the General tab in the following step. If you are working with any other connection, you will use the Networking tab
  4. On either of these tabs, select Internet Protocol (TCP/IP), and then click the Properties button.
  5. The Internet Protocol (TCP/IP) Properties dialog box opens.
  6. Select the Use The Following IP Address option.
  7. If you are working with the local area connection enter the address, subnet mask, and default gateway in the available fields.
  8. If you are working with any other network connection, assign the proper IP address.
  9. If you want to configure the DNS server settings of the computer, select the Use The Following DNS Server Addresses option, and then enter the primary and secondary DNS server addresses in the Preferred DNS Server text box, and in the Alternate DNS Server text box respectively.
  10. If you want to configure a WINS server, click the Advanced button.
  11. Click OK.

How to configure Advanced DNS settings

  1. Click Start, Control Panel, and then click Network Connections.
  2. Right-click the network connection you want to work with, and then click Properties from the shortcut menu.
  3. If you working with the local area connection, on the General tab, select Internet Protocol (TCP/IP), and then click the Properties btton.
  4. When the Internet Protocol (TCP/IP) Properties dialog box opens, click the Advanced button.
  5. The Advanced TCP/IP Settings dialog box contains four tabs (IP Settings, DNS, WINS, Option) which you can use to either extend or override the settings from the Internet Protocol (TCP/IP) Properties dialog box.
  6. Click the DNS tab.
  7. The DNS Server Addresses, In Order Of Use list displays all the DNS servers configured for this particular client. The DNS Server Addresses, In Order Of Use list can contain up to 20 different DNS servers. A DNS query is sent to the first server in the list. If this DNS server is unable to service the query, the query is sent to the second DNS server in the list, and so forth, until a DNS server returns a valid answer, or until all DNS servers have been tried.
  8. To add, remove, and edit DNS servers from the DNS Server Addresses, In Order Of Use list, click the appropriate button: Add button, Edit button, Remove button.
  9. To change the order of the DNS servers listed in the DNS Server Addresses, In Order Of Use list, click the server whose order you want to change, and then use the Up and Down arrows to position the server.
  10. Click the Append Primary And Connection Specific DNS Suffixes option if you want DNS to automatically append the primary DNS suffix and all other connection specific suffixes when DNS requests are made.
  11. Click the Append Parent Suffixes Of The Primary DNS Suffix checkbox if you want the parent suffixes of the primary suffix appended.
  12. Click the Append These DNS Suffixes (In Order) option if you want to specify the list of suffixes for DNS, rather than using any primary and connection specific suffixes.
  13. If you want to define a default connection suffix to append to DNS queries, enter it in the DNS Suffix For This Connection text box.
  14. Select the Register This Connection’s Addresses In DNS checkbox if you want the DHCP client to register its name and IP address with the closest dynamic DNS server.
  15. Select the Use This Connection’s DNS Suffix In DNS Registration checkbox if you want the primary or connection specific DNS suffix to be used in the client registration with the dynamic DNS service.
  16. Click OK to close the Advanced TCP/IP Settings dialog box.
  17. Click OK to close the Internet Protocol (TCP/IP) Properties dialog box.

How to configure a WINS client

WINS listens to NetBIOS over TCP/IP (NBT) and then collects these broadcasts to a central source. If your clients are set up to utilize a WINS server, NBT addresses can be resolved without broadcasts being used. The method which your client would use is determined by the node type configured for the client. The NTB settings which you configure on the WINS tab of the Advanced TCP/IP Settings dialog box determine the client’s node type.

The NetBIOS node types are listed below:

  • B-node, broadcast: For name registration, and name resolution, NBT queries are broadcasted.
  • P-node, peer to peer node: A NetBIOS name server or a WINS server is used to resolve NetBIOS names.
  • M-node, mixed: By default, this is similar to b-node. P-node is used if it cannot resolve a NetBIOS name.
  • H-node, hybrid: By default, this is similar to p-node. B-node is used if it cannot a name.

To configure a WINS client,

  1. Click Start, Control Panel, and then click Network Connections.
  2. Right-click the network connection you want to work with, and then click Properties from the shortcut menu.
  3. If you working with the local area connection, on the General tab, select Internet Protocol (TCP/IP), and then click the Properties button.
  4. When the Internet Protocol (TCP/IP) Properties dialog box opens, click the Advanced button.
  5. The Advanced TCP/IP Settings dialog box contains four abs (IP Settings, DNS, WINS, Options) which you can use to extend or override the settings of the Internet Protocol (TCP/IP) Properties dialog box dialog box.
  6. Click the WINS tab.
  7. Click Add
  8. In the TCP/IP WINS Server dialog box, enter the IP address of the WINS server, and then click the Add button.
  9. The initial server in the WINS address list group must be the server physically nearest to the actual client machine.
  10. You can enter additional WINS servers and change the order of the servers.
  11. If you want to enable LMHOSTS lookups for allconnections which are using TCP/IP, click the Enable LMHOSTS Lookup checkbox.
  12. The settings which you can configure in the NetBIOS Setting portion of the WINS tab are listed below:
    • Default: Use NetBIOS Setting From The DHCP Server; this option forces the client to use the settings of the DHCP server over the WINS settings and LMHOSTS file settings.
    • Enable NetBIOS Over TCP/IP; this option overrides DHCP settings
    • Disable NetBIOS Over TCP/IP; this option disables NetBIOS Over TCP/IP.
  1. Click OK to close the Advanced TCP/IP Settings dialog box.
  2. Click OK to close the Internet Protocol (TCP/IP) Properties dialog box.

Dynamically Assigning IP Addresses

In Windows Server 2003, dynamic IP addressing is enabled by Dynamic Host Configuration Protocol (DHCP). The Dynamic Host Configuration Protocol (DHCP) is a protocol and service that functions at the application layer of the TCP/IP protocol suite. The DHCP protocol automates the configuration of TCP/IP clients because IP addressing occurs through the system. You can configure a computer as a DHCP server so that the DHCP server can automatically assign IP addresses to DHCP clients, and with no manual intervention. IP addresses that are assigned via a DHCP server are regarded as dynamically assigned IP addresses. The DHCP server assigns IP addresses from a predetermined IP address range(s).

Using dynamic IP addressing leads the following benefits:

  • Simpler management of IP addressing. You can manage IP addressing from a central location.
  • Because the system assigns IP addresses, it leads to less incorrect configurations of IP addresses.
  • Duplicated IP addresses are prevented.
  • Dynamic addressing also easily scales from small to large networking environments.

For dynamic IP addressing to occur, the following tasks has to be completed:

  • A DHCP server must be installed in your networking environment.
  • Your clients must be configured to obtain their address configuration data automatically.
  • You can optionally specify that clients obtain other TCP/IP configuration information or parameters automatically as well, such as:
    • DNS server address
    • WINS server address
    • Default gateway
  • A DHCP server must be installed in your networking environment.

To install the DHCP server, you would need to perform the following steps:

  • Install the DHCP service on the client computer
  • Configure the range of IP addresses which the DHCP server assign IP addresses from. This range of IP addresses is called a scope.
  • Activate the scope.
  • If you are using the Active Directory directory service, you can authorize the DHCP server in the Active Directory.

A scopecan be defined as a set of IP addresses which the DHCP server can allocate or assign to DHCP clients. A scope contains specific configuration information for clients that have IP addresses which are within the particular scope. Scope information for each DHCP server is specific to that particular DHCP server only, and is not shared between DHCP servers. Scopes for DHCP servers are configured by administrators.

Microsoft Windows computers running TCP/IP automatically install the DHCP client service as a component of TCP/IP. This includes servers and workstations running:

  • Windows 98, Windows ME, Windows NT, Windows XP, Windows 2000, and Windows Server 2003

How to install the DHCP service

  1. Log on to the server using Administrative privileges.
  2. Click Start, Control Panel, and then click Add Or Remove Programs.
  3. When the Add Or Remove Programs dialog box opens, click Remove Windows Components.
  4. This starts the Windows Components Wizard.
  5. In the Components list box, select Networking Services, and then click the Details button.
  6. The Networking Services dialog box opens.
  7. In the Sub-components Of Networking Services list box, check the Dynamic Host Configuration Protocol (DHCP) checkbox.
  8. Click OK.
  9. Click Next.
  10. When The Completing The Windows Components Wizard page is displayed, click Finish.

How to authorize the DHCP server

  1. Click Start, All Programs, Administrative Tools and then click DHCP to open the DHCP management console.
  2. In the console tree, expand the DHCP server node.
  3. Click the DHCP server.
  4. Click the Action menu, and then select Authorize.

How to create and configure a DHCP scope for the DHCP server

  1. Click Start, All Programs, Administrative Tools and then click DHCP to open the DHCP management console.
  2. In the console tree, expand the DHCP server node.
  3. Select the DHCP server.
  4. Click the Action menu, and then select New Scope
  5. The New Scope Wizard starts.
  6. Click Next on the initial page of the New Scope Wizard.
  7. On the Scope Name page, enter a name for the new scope in the Name text box.
  8. Enter a description in the Description text box. Click Next.
  9. On the IP Address Range page, enter the start IP address and end IP address that defines the range of new scope in the Start IP Address text box, and End IP Address text box respectively.
  10. The server automatically provides the mask in the Subnet Mask text box.
  11. Select the value in the Length spin box. The subnet length mask is automatically defined as 24. Click Next.
  12. On the Add Exclusions page, using the Start IP Address End IP Address text boxes, define any exclusion. Click Add. Click Next.
  13. On the Lease Duration page, you can change the default lease duration of 8 days. Click Next.
  14. On Configure DHCP Options page, click the No, I Will Configure These Options Later option to indicate that you will configure the DHCP options later. Click Next.
  15. On the Completing The New Scope Wizard page, click Next.

How to configure TCP/IP for dynamic addressing from a DHCP server

  1. Click Start, Control Panel, and then click Network Connections.
  2. Right-click the network connection you want to work with, and then click Properties from the shortcut menu.
  3. If you are working with the local area connection, on the General tab, select Internet Protocol (TCP/IP), and then click the Properties button
  4. When the Internet Protocol (TCP/IP) Properties dialog box opens, click the Obtain An IP Address Automatically option.
  5. If you want the client to automatically obtain DNS server information from the DHCP server, select the Obtain DNS Server Address Automatically option.
  6. Click OK.

How to configure an Alternate IP Addressing Configuration

You can configure alternate IP address configuration parameters which can be used if the DHCP server cannot be accessed. Configuring the alternate IP address configuration is ideal for laptop computers which connect to a number of different networks.

An alternate I addressing configuration contains the following settings:

  • IP address, subnet mask and default gateway
  • DNS server IP address
  • WINS server IP address

To configure an alternate IP addressing configuration,

  1. Click Start, Control Panel, and then click Network Connections.
  2. Right-click Local Area Connection, and then click Properties from the shortcut menu.
  3. On the General tab, select Internet Protocol (TCP/IP), and then click the Properties button.
  4. On the Internet Protocol (TCP/IP) Properties dialog box select the Obtain IP Address Automatically option.
  5. Click the Alternate Configuration tab.
  6. The Automatic Private IP address option is selected by default on the Alternate Configuration tab.
  7. Click the User configured button.
  8. Enter the appropriate information in the provided text boxes:
    • IP address
    • Subnet mask
    • Default gateway
    • Preferred DNS server
    • Alternate DNS server
    • Preferred WINS server
    • Alternate WINS server
  1. Click OK

Troubleshooting TCP/IP Addressing

One of the more common issues that arise in TCP/IP networks is the duplication of IP addresses. Duplicated IP addresses result in packets being sent to the incorrect destination computers. Windows operating systems can however detect the duplication of IP addresses.

The process that occurs to detect duplicate IP addresses is illustrated below:

  1. When the computer starts, the system checks for any duplicate IP addresses
  2. The TCP/IP protocol stack is disabled on the computer when the system detects duplicate IP addresses.
  3. An error message is shown that indicates the hardware address of the other system that this computer is in conflict with.
  4. The computer that initially owned the duplicate IP address experiences no interruptions, and operates as normally.
  5. You have to reconfigure the conflicting computer with a unique IP address so that the TCP/IP protocol stack can be enabled on that particular computer again.

A few strategies for troubleshooting TCP/IP addressing issues are briefly discussed below:

  • If a computer cannot communicate with any other systems on the network verify that the correct subnet mask is configured for the computer. Incorrectly configured subnet masks would prevent computers on the same subnet from communicating.
  • If a TCP based computer cannot communicate with systems on other LANs, but can communicate with systems on the same LAN, the problem is probably due to an incorrectly configured default gateway. The computer uses the default gateway when it needs to communicate with computers that are located on other networks. Computers that have no specified default gateway can only communicate with computers on the same LAN. It cannot communicate with systems on other LANs.
  • Communication could not be occurring between computers because an issue exists that pertains to name resolution. In TCP based networks, communication is based on IP addresses. If names cannot be resolved to IP addresses, the computers would not have the IP addresses required to communicate. If you are using the Active Directory directory service, DNS is used for name resolution. DNS name resolution is also necessary to establish a connection to the Internet. To use DNS for name resolution, the computer must have the IP address of a DNS server specified in its TCP/IP properties.
  • If a DHCP server is configured to dynamically assign IP addresses and you have a computer that was assigned the incorrect IP address, it was probably due to the computer not being able to contact the DHCP server. When this occurs, the computer assigns its own IP address through Automatic Private IP Addressing (APIPA). Computers cold be unable to contact the DHCP server for a number of reasons:
    • A problem might exist with the hardware or software of the DHCP server.
    • A Data-link protocol issue could be preventing the computer from communicating with the network.
    • The DHCP server and the client are on different LANs and there is no DHCP relay agent. A DHCP relay agent enables a DHCP server to handle IP address requests of clients that are located on a different LAN.
  • If you have clients that cannot obtain IP addresses from the DHCP server, even though they can contact the DHCP server, verify the following:
    • Verify that the DHCP Server service is running on the particular server.
    • Check the actual TCP/IP configuration settings on the DHCP server.
    • If you are using the Active Directory directory service, verify that the DHCP server is authorized by Active Directory.
    • The DHCP server could be configured with the incorrect scope. Check that the scope is correct on the DHCP server, and verify that it is active.