You are the systems administrator for Exponent Mathematicians, and you have been asked to implement DHCP on a multinetted network segment. What should you do to ensure that you do this successfully?
2.
You are the administrator of the DHCP server for the Get Bux pawnshop chain. You are getting complaints from users that they keep getting address conflict messages when they turn on their computers. What DHCP counter might help you identify the problem?
3.
You are the administrator for Fly Away Travel. When administering Fly Away's DHCP server, you notice that the number of DHCP requests is very high for the number of users on the network. Where is the first place you should look for a server-related problem?
4.
You're the administrator of the DHCP server for Little Faith Enterprises. You notice that the DHCP server is running sluggishly during peak hours. When you check the Performance utility, you notice that the DHCP Conflict Check Queue Length counter is very high. What could be causing the DHCP server to be running slowly?
5.
You're the administrator of the DHCP server for Little Faith Enterprises. You have just installed the DHCP service and created your first scope by using the New Scope Wizard. You are trying to provide DHCP addresses to a group of users that are two router hops away. What do you still need to do?
Answers to Review Questions
1.
To successfully implement DHCP in a multinetted environment, you should consider using a superscope to ease the management of the scopes for each of the multinetted networks. For more information, see the section "Understanding DHCP Superscopes."
2.
You should check the Declines/Sec counter in the Performance console for the DHCP object. The number of DHCPDECLINE messages received per second by the DHCP server from client computers can be used to see whether the DHCP client computer has declined the IP address issued by the server. You see this number rise when client computers start having address conflict problems, and it could indicate a network problem, computers with static addresses also being part of a scope, or a rogue DHCP server being on the network. For more information, see the section "Troubleshooting DHCP Server Authorization Problems."
3.
You should check the length of the DHCP lease. If the lease has been set to a very short duration, client computers would need to request addresses frequently. For more information, see the section "Creating a DHCP Scope."
4.
There are either a lot of DHCP requests occurring during peak hours or the Conflict Detection Attempts parameter is set too high. If that parameter is enabled, the Windows Server 2003 DHCP service issues an address, and it checks whether any IP address conflicts exist. This can put a lot of additional overhead on the server and drive up the DHCP conflict check queue length. For more information, see the section "Troubleshooting DHCP Server Authorization Problems."
5.
First, you need to authorize the DHCP server in Active Directory. The DHCP server cannot provide addresses until that occurs. You also need to configure the BOOTP forwarder on any routers between the DHCP server and the client workstations so that the routers know where to forward DHCP messages. For more information, see the section "Authorizing a DHCP Server in Active Directory."
