TCP/IP configuration items

  • Article

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

TCP/IP configuration items

For TCP/IP to function properly, you need to configure the following:

  • IP address

  • Subnet mask

  • Default gateway

  • DNS server

  • WINS server

IP address

You must configure each interface on each TCP/IP node (host or router) with a unique IP address that is correct for the attached network segment. The IP address is a required configuration item.

For more information, see IP addressing.

Subnet mask

You must configure each interface on each TCP/IP node (host or router) with a subnet mask that, when combined with the IP address, yields the network ID. All IP interfaces on the same network segment must use the same network ID. Therefore, all IP interfaces on the same network segment must use the same subnet mask. The subnet mask is a required configuration item.

For more information, see Subnet masks.

Default gateway

To communicate with TCP/IP nodes on other network segments, you must configure at least one interface with the IP address of a default gateway (a local router that forwards remote TCP/IP traffic to its destination).

You do not need to configure a default gateway for a network that consists of a single network segment.

For more information, see IP routing.

DNS server

A DNS server can resolve domain names to IP addresses. When a TCP/IP host is configured with the IP address of a DNS server, the TCP/IP host sends DNS name queries to the DNS server for resolution. A DNS server is required for computers operating in an Active Directory-based network environment.

You do not need to configure a DNS server for a network that consists of a single network segment.

For more information, see Host name resolution.

A server running Windows Server 2003 can be a DNS server. For more information, see DNS.

WINS server

A WINS server can store and resolve NetBIOS names to IP addresses. When a TCP/IP host is configured with the IP address of a WINS server, the TCP/IP host registers its own NetBIOS names with the WINS server and sends NetBIOS name queries to the WINS server for resolution. A WINS server is highly recommended when there is more than one network segment in your network and when you have computers that are not based on Active Directory (for example, computers running Windows NT 4.0, Windows 95, Windows 98, and Windows Millennium Edition).

You do not need to configure a WINS server for a network that consists of a single network segment.

For more information, see NetBIOS name resolution.

A server running Windows Server 2003 can be a WINS server. For more information, see WINS.

IPSec

To provide security for TCP/IP, you need to configure Internet Protocol security (IPSec). IPSec is a framework of open standards for ensuring private, secure communications over Internet Protocol (IP) networks, through the use of cryptographic security services. It provides aggressive protection against private network and Internet attacks through end-to-end security. In Windows XP and the Windows Server 2003 family, IPSec provides the ability to protect communication between workgroups, local area network computers, domain clients and servers, branch offices (which might be physically remote), extranets, and roving clients.

For more information, see Internet Protocol Security (IPSec).