Specifying the IP address range of a scope requires some knowledge of subnetting. Each scope in a DHCP server holds a pool of IP addresses to give out to clients, and the range of IP addresses must be within the allowed range of the subnet that you specify on the subnet mask field.
For simplicity we entered a classful, class C IP address range from Notice that the range encompasses the IP address of our server, the DNS servers and the default gateway, meaning that the DHCP server could potentially assign a client an IP address that is already in use! Do not worry -- we will take care of that later. Specify IP addresses to exclude from assignment. For the Start IP address , enter Certain network devices, such as servers, will need statically configured IP addresses.
The IP addresses may sometimes be within the range of IP addresses defined for a scope. We have the opportunity here to define those IP addresses that are to be excluded. We specified IP addresses Specify the lease duration for the scope. Verify that Days is 8 and click Next. The lease duration is how long clients should keep their IP addresses before having to renew them.
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.
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. In case you need to exclude more IP addresses, you can do it at this point by following these instructions:. When the Add Exclusion window comes up, enter the required range and then click Add.
In our example, we've excluded the addition range Notice that the server node and scope node still has a red arrow pointing down. Right-click the server server After you have installed the DHCP service and started it, you must create a scope.
Microsoft recommends that, each DHCP server in your environment has at least one scope that does not overlap with any other DHCP server scope in your environment. The following sections explain how to troubleshoot some of the issues that you may experience, when you try to install and configure a Windows Server based DHCP server in a workgroup.
This issue can be caused by a network problem, or because the DHCP server is unavailable. When the DHCP server started and other clients can obtain valid addresses, verify that the client has a valid network connection and that all the related client hardware devices including cables and network adapters are working properly.
In this case, the server may not be authorized to operate on the network. These logs may explain why you cannot start the DHCP service. Skip to main content. This browser is no longer supported.
0コメント