Line 12: |
Line 12: |
| This chapter helps you configure software and hardware supplied by other companies and for that reason is not as specific as the rest of this guide. Given the wide range of computers, operating systems and software applications, we cannot accurately explain the process of configuring each of them. If your computers and applications came with manuals, they might be useful supplements to this chapter. Technical problems encountered in networking your desktop computers and applications are best resolved with the vendors who support them for you. | | This chapter helps you configure software and hardware supplied by other companies and for that reason is not as specific as the rest of this guide. Given the wide range of computers, operating systems and software applications, we cannot accurately explain the process of configuring each of them. If your computers and applications came with manuals, they might be useful supplements to this chapter. Technical problems encountered in networking your desktop computers and applications are best resolved with the vendors who support them for you. |
| | | |
− | {| cellspacing="0" border="1" | + | {{DrawBoxWarning|content=This chapter demonstrates only one of the many possible ways to configure your client computers and is provided here as an example.}} |
− | ||'''Important'''
| |
− | This chapter demonstrates only one of the many possible ways to configure your client computers and is provided here as an example.|| | |
− | |}
| |
| | | |
| ====7.2. Configuring Your Desktop Operating System==== | | ====7.2. Configuring Your Desktop Operating System==== |
Line 27: |
Line 24: |
| |} | | |} |
| | | |
− | {| cellspacing="0" border="1" | + | {{DrawBoxNote|content=We strongly recommend that you configure all clients machines using DHCP rather than manually using static IP addresses. Should you ever need to change network settings or troubleshoot your network later, you will find it much easier to work in an environment where addresses are automatically assigned.}} |
− | |'''Note'''
| |
− | |We strongly recommend that you configure all clients machines using DHCP rather than manually using static IP addresses. Should you ever need to change network settings or troubleshoot your network later, you will find it much easier to work in an environment where addresses are automatically assigned.||
| |
− | |}
| |
| | | |
| On a Windows 95/98 system, the window will look like the image below. | | On a Windows 95/98 system, the window will look like the image below. |
Line 39: |
Line 33: |
| Your server provides a DHCP server that assigns each of the computers on your network an IP address, subnet mask, gateway IP address and DNS IP address(es). For a more detailed explanation of DHCP, consult the section in the|Chapter 5 called "Configuring Your DHCP Server". | | Your server provides a DHCP server that assigns each of the computers on your network an IP address, subnet mask, gateway IP address and DNS IP address(es). For a more detailed explanation of DHCP, consult the section in the|Chapter 5 called "Configuring Your DHCP Server". |
| | | |
− | {| cellspacing="0" border="1" | + | {{DrawBoxNote|content=In some rare cases, you may want to use a static IP address for a particular client machine. The typical approach is to manually enter this IP address into the network properties of the specific machine. The negative side of this approach is that you cannot easily change or alter network settings without having to go in and modify the information on the client machine. However, it is possible to provide this static IP address directly through DHCP rather than manually configuring the client computer. To do so, you will first need to determine the Ethernet address of the client computer (usually through the network properties). Next you will go to the Hostnames and addresses web panel of the server manager and enter the information there.}} |
− | |'''Note'''
| |
− | |In some rare cases, you may want to use a static IP address for a particular client machine. The typical approach is to manually enter this IP address into the network properties of the specific machine. The negative side of this approach is that you cannot easily change or alter network settings without having to go in and modify the information on the client machine. However, it is possible to provide this static IP address directly through DHCP rather than manually configuring the client computer. To do so, you will first need to determine the Ethernet address of the client computer (usually through the network properties). Next you will go to the Hostnames and addresses web panel of the server manager and enter the information there.||
| |
− | |}
| |
| | | |
− | {| cellspacing="0" border="1" | + | {{DrawBoxWarning|content=Only One DHCP Server |
− | ||'''Important'''
| + | It is imperative that no other DHCP server is on your network. If a former DHCP server configured your computers, you should remove that DHCP server from your network. Leave DHCP enabled, and reboot each computer. New IP addresses, netmasks, gateway IP addresses and DNS addresses will be assigned automatically by the server DHCP server.}} |
− | Only One DHCP Server | |
− | It is imperative that no other DHCP server is on your network. If a former DHCP server configured your computers, you should remove that DHCP server from your network. Leave DHCP enabled, and reboot each computer. New IP addresses, netmasks, gateway IP addresses and DNS addresses will be assigned automatically by the server DHCP server.|| | |
− | |}
| |
| | | |
| =====7.2.2. Manual entry for computers not using DHCP service===== | | =====7.2.2. Manual entry for computers not using DHCP service===== |
Line 85: |
Line 73: |
| However if you create a group and name it whatever you want but put one of the above for the description then the newly created group will replace the above mapping. So if you create a group called "admins" and give it a description of "Domain Admins" then anyone you assign to this group will be a domain admin and also a local admin on ANY box that has joined the domain. | | However if you create a group and name it whatever you want but put one of the above for the description then the newly created group will replace the above mapping. So if you create a group called "admins" and give it a description of "Domain Admins" then anyone you assign to this group will be a domain admin and also a local admin on ANY box that has joined the domain. |
| | | |
− | {| cellspacing="0" border="1" | + | {{DrawBoxNote|content=A word about domain names<br /> |
− | |'''Note'''
| + | Once you've set up your server, there's typically a delay of one or more days before your Domain Registrar publishes your domain address records (the domain name or names and the associated numerical IP address) so that the information is accessible to other computers on the Internet. Until it does, incoming mail won't be able to find you and computers elsewhere on the Internet won't be able to contact your server using your domain name (for example, www.yourdomain.xxx). However, on your local network you should be able to connect to your server using the short names of 'www' (for web access) and 'mail' (for e-mail clients).}} |
− | |A word about domain names<br />
| |
− | Once you've set up your server, there's typically a delay of one or more days before your Domain Registrar publishes your domain address records (the domain name or names and the associated numerical IP address) so that the information is accessible to other computers on the Internet. Until it does, incoming mail won't be able to find you and computers elsewhere on the Internet won't be able to contact your server using your domain name (for example, www.yourdomain.xxx). However, on your local network you should be able to connect to your server using the short names of 'www' (for web access) and 'mail' (for e-mail clients).|| | |
− | |}
| |