Although most computers will be properly set up for network access during Windows Setup, you might need to change these settings at some point—possibly immediately if the specified settings were wrong or incomplete. This section explains how to get a server running properly on a network.
Change is sometimes necessary—although with a server, it's better to spend your time planning first than to have to make changes later. However, as Robbie Burns might have said while reconfiguring his server, "The best laid schemes o' mice and men gang aft a-gley." So even with careful planning, you can discover that a machine needs to have a different name or needs to be joined to a different domain.
To change the identity of a server that isn't a domain controller, log on using an administrator's account and follow these steps:
Figure 6-5. The Identification Changes dialog box.
Changing the identity of a domain controller is a multistep process. First you must demote the domain controller by running DCPROMO. Then you can change the identity, and finally you can promote the domain controller again. The steps for this process are detailed in Chapter 11.
It's a good idea to use a computer name that is both DNS-compatible and NetBIOS-compatible so that all types of clients see the same name for your computer. To do this, make the name 15 characters or fewer and don't use asterisks or periods. To obtain the best application compatibility, try to avoid using spaces, underscores, and hyphens.
To add or change the settings for core network components such as clients, services, and protocols, open the Network and Dial-Up Connections folder, right-click the Local Area Connection icon, and choose Properties from the shortcut menu. This procedure opens the Local Area Connection Properties dialog box shown in Figure 6-6, which you can use to view and change your server's networking components.
Figure 6-6. The Local Area Connection Properties dialog box.
The top of the dialog box shows the network adapter to which you are binding networking services. Beneath that is the media access control (MAC) address for the network interface card, the unique identifier of your network card that is used for communications with other hosts in your subnet.
To install a network component, select Install, choose the type of component you want to install (Client, Service, or Protocol), and then click Add. Select the component from the list presented and click OK. To configure the component (if the component has a configurable option), select the component and click Properties.
If you have a multihomed server (a server with more than one network adapter), give your local area connections a name indicating to which network the adapters are connected. To do so, right-click the connections in the Network and Dial-Up Connections folder and choose Rename from the shortcut menu.
TCP/IP is the most important protocol in today's networks, and it's the backbone for Microsoft's vision of networking in Windows 2000 and beyond. The protocol is well suited to enterprise networking, and it's required for accessing the Internet. If you're unfamiliar with TCP/IP, see Chapter 13 for an introduction.
Before installing and configuring protocols on your network, review the checklists in the Windows 2000 Help files. Once you understand the following three areas, you can install all the necessary interlocking pieces.
TCP/IP is installed as the default network protocol if a network adapter was detected during installation. If the default was overridden during installation, you can add TCP/IP by following these steps:
The easiest and most reliable way to configure machines on a network running the TCP/IP suite is to use a DHCP server to automatically distribute IP addresses. DHCP can also inform clients of the appropriate DNS servers and gateways to use. A DHCP server not only simplifies client configuration, but it also saves headaches for the poor soul who would otherwise have to track the use of IP addresses, because it manages the database of available IP addresses dynamically and automatically.
Dynamic addressing using DHCP is the Windows 2000 default setting. If you need to check this or change a statically assigned host to a dynamically configured host, follow these steps:
Figure 6-7. The General tab of the Internet Protocol (TCP/IP) Properties dialog box.
Assigning IP Addresses for DNS and WINS Servers
When setting up a DNS or WINS server, it's tempting to use a static IP address. Although this is an acceptable use of static IP addresses, a better method for many networks is to allow the server to obtain an address from the DHCP server and then create an IP reservation for the server with an unlimited lease duration on the DHCP server. This step gives the server a permanent lease on the IP address it was assigned, ensuring that the IP address of the DNS server won't change, at the same time allowing the DHCP administrator to easily take back the address if the server is moved or decommissioned. See Chapter 14 for information on creating reservations on a DHCP server.
If your network doesn't have a DHCP server or if you're setting up a DHCP server, you need to manually configure TCP/IP to use a static IP address and DNS information. To do this, obtain an IP address from the person who maintains the database of IP addresses that your organization can use. If using DHCP, all DHCP servers also need to be updated to exclude your static IP address.
To set up a system with a static IP address, follow these steps:
The DNS service is critical for resolving host names such as http://www.microsoft.com into IP addresses that your computer can access. Without the DNS service, users could access resources only by typing in their IP addresses directly or by broadcasting their NetBIOS names (which only works on local subnets and consumes lots of network bandwidth).
If you aren't using a DHCP server to configure your server's IP address and associated settings and you need to enter other settings besides just your server's IP address and DNS servers, select Advanced in the TCP/IP Properties dialog box. This opens the Advanced TCP/IP Settings dialog box, shown in Figure 6-8, which you use to specify additional settings, including WINS servers, NetBIOS over TCP/IP, and optional TCP/IP parameters. Chapter 13 contains more information about configuring TCP/IP.
Figure 6-8. The IP Settings tab of the Advanced TCP/IP Settings dialog box.
Configuring IP Settings The Advanced TCP/IP Settings dialog box contains four tabs, the first of which is the IP Settings tab. You use this tab to add the IP address and subnet mask for your network connection and the gateways your server should use. To change the options on this tab, follow these steps:
Configuring DNS Settings Click the DNS tab to access the advanced DNS settings for your network connection, as shown in Figure 6-9. Then use the following procedure to configure your DNS settings:
Figure 6-9. The DNS tab of the Advanced TCP/IP Settings dialog box.
Configuring WINS Settings To configure the WINS settings for your computer, click the WINS tab in the Advanced TCP/IP Settings dialog box (Figure 6-10). If WINS servers are operating on your network, you should add their addresses here. Doing so gives you the best results when communicating with hosts that are running Microsoft operating systems earlier than Windows 2000. As with the other tabs in the Advanced TCP/IP Settings dialog box, use the Add, Edit, and Remove buttons to modify your WINS server list. For a more thorough discussion of when to use WINS servers on your network, see Chapter 14.
Figure 6-10. The WINS tab of the Advanced TCP/IP Settings dialog box.
To enable the use of an Lmhosts file for resolving NetBIOS names to IP addresses, select the Enable LMHOSTS Lookup check box, and click Import LMHOSTS to import an Lmhosts file. We recommend using Lmhosts files only when absolutely necessary because trying to keep them up-to-date can be tricky—the minuscule reduction of network traffic that Lmhosts files offer isn't worth it.
When you configure a WINS server, use the Ipconfig command at a command prompt to obtain your current IP address, and then enter that address in the WINS Addresses field. Don't enter any other WINS server in this field; you don't want your WINS server registering its NetBIOS name with another WINS server if WINS hasn't started in time to respond at bootup.
In all likelihood, you'll need to communicate with clients that are running Microsoft operating systems earlier than Windows 2000, so make sure the Enable NetBIOS Over TCP/IP option is selected. Disable this only if you communicate exclusively with other computers running Windows 2000 or computers that rely solely on DNS for name resolution services (for example, UNIX). Also, note that any applications that use NetBIOS won't work if you disable NetBIOS Over TCP/IP.
Configuring TCP/IP Options If you need to configure any TCP/IP options, click the Options tab in the Advanced TCP/IP Settings dialog box. Select an option you want to configure, and then click Properties. For more information about TCP/IP properties and secure TCP/IP connections, see Chapter 13.
The NWLink IPX/SPX protocol was designed as an easy-to-use-and-configure, routable protocol that is compatible with NetWare's IPX/SPX protocol. As such, it used to be a popular protocol in many companies and can still be useful in maintaining interoperability with older network environments. For detailed information about interoperating with NetWare, see Chapter 21.
Fortunately, configuring the NWLink IPX/SPX protocol is easy. Just follow these steps:
Figure 6-11. The General tab of the NWLink IPX/SPX/NetBIOS-Compatible Transport dialog box.