There are a few considerations at this point. If a short lease duration is configured, clients will be renewing their IP addresses more frequently. The result will be additional network traffic and additional strain on the DHCP server.
On the other hand if a long lease duration is configured, IP addresses previously obtained by decommissioned clients would remain leased and unavailable to future clients until the leases either expire or are manually deleted. Additionally if network changes occur, such as the implementation of a new DNS server, those clients would not receive those updates until their leases expire or the computers are restarted.
In an environment where computers are often moved and replaced, such as a wireless network, you would want to specify a short duration since a new wireless client could roam within range at any time. These are the other settings that help clients communicate on the network. Specify the router IP address. The first option we can configure is the IP address for the subnet's router for which this scope is providing IP addresses.
Keep in mind that this IP address must be in the same network as the IP addresses in the range that we created earlier. Configure domain name and DNS servers. Then enter When finished, click Next. If you had a DNS infrastructure in place, you could have simply typed in the fully qualified domain name of the DNS server and clicked Resolve. The DNS servers will be used by clients primarily for name resolution, but also for other purposes that are beyond the scope of this article.
Configure WINS servers. On the next screen, enter Finally, the wizard asks whether you want to activate the scope. At this point we almost have a functional DHCP server. Certain network devices, such as networked printers, are best configured with reserved IP addresses rather than static IP addresses.
For example, DHCP helps prevent address conflicts caused when the same IP address is mistakenly assigned to two hosts. Click Next to begin the installation process. After the installation wizard has completed, you can verify that the DHCP Server service has been installed on your computer by opening the DHCP console administrative tool.
The DHCP console, shown in Figure 1 , is the interface from which you can configure and manage virtually all features related to your DHCP server, including scopes, exclusions, reservations, and options. Only domain controllers and domain member servers participate in Active Directory, and only these server types can become authorized.
Stand-alone or workgroup DHCP servers running Microsoft Windows Server or Windows Server cannot become authorized in Active Directory networks, but they can coexist with these networks as long as they are not deployed on a subnet with any authorized DHCP servers.
Note, however, that this configuration is not recommended. Stand-alone DHCP servers implemented together with authorized servers are known as rogue servers. Reservations can be defined on the DHCP server to allow certain clients to have their own IP address this will be discussed a little later on. Addresses can be reserved for a MAC address or a host name so these clients will have a fixed IP address that is configured automatically.
Most Internet Service Providers use DHCP to assign new IP addresses to client computers when a customer connects to the internet - this simplifies things at user level. The above diagram diplays a simple structure consisting of a DHCP server and a number of client computers on a network. By using the "Manage your server" wizard, you are able to enter the details you require and have the wizard set the basics for you.
You will be asked to enter the name and description of your scope. The next window will ask you to define the range of addresses that the scope will distribute across the network and the subnet mask for the IP address. Enter the appropriate details and click next. You are shown a window in which you must add any exclusions to the range of IP addresses you specified in the previous window. If for example, the IP address In this example I have excluded a range of IP addresses, In this case, eleven IP's will be reserved and not distributed amongst the network clients.
It is now time to set the lease duration for how long a client can use an IP address assigned to it from this scope. The result will be additional network traffic and additional strain on the DHCP server. On the other hand if a long lease duration is configured, IP addresses previously obtained by decommissioned clients would remain leased and unavailable to future clients until the leases either expire or are manually deleted. Additionally if network changes occur, such as the implementation of a new DNS server, those clients would not receive those updates until their leases expire or the computers are restarted.
In an environment where computers are often moved and replaced, such as a wireless network, you would want to specify a short duration since a new wireless client could roam within range at any time. These are the other settings that help clients communicate on the network. Specify the router IP address.
The first option we can configure is the IP address for the subnet's router for which this scope is providing IP addresses. Keep in mind that this IP address must be in the same network as the IP addresses in the range that we created earlier. Configure domain name and DNS servers. Then enter When finished, click Next. If you had a DNS infrastructure in place, you could have simply typed in the fully qualified domain name of the DNS server and clicked Resolve. The DNS servers will be used by clients primarily for name resolution, but also for other purposes that are beyond the scope of this article.
Configure WINS servers. On the next screen, enter Finally, the wizard asks whether you want to activate the scope. At this point we almost have a functional DHCP server. Certain network devices, such as networked printers, are best configured with reserved IP addresses rather than static IP addresses.
This is similar to scope options except that these options are either inherited by all the scopes or overridden by them covered in ' Advanced DHCP Server Configuration on Windows ' article. Earlier, we only defined exclusions for our servers, router plus a few more spare IP addresses.
0コメント