You are your companys network administrator. Your network consists of a single Active Directory domain. The DHCP service is installed on a Windows Server 2003 computer named DHCP1. DHCP1 has been authorized in Active Directory. A single scope has been defined on DHCP1 with 200 IP addresses: 220.127.116.11 through 18.104.22.168. While performing routine maintenance, you notice a DHCP Jet database error in the Event Log on DHCP1. Later in the day, users report that IP addresses are not being delivered to client computers. You must ensure that DHCP can operate normally. What should you do?
A. Shorten the lease duration for both scopes. B. Add new addresses to the existing DHCP scopes. C. Shorten the lease duration for the subnet B scope only. D. Assign static IP addresses to the new Windows XP Professional clients. E. Configure both scope options to include the Perform Router Discovery option.
Shorten the lease duration for both scopes.-explanation: you should shorten the lease duration for both scopes. the problem you experienced indicates that there are not enough ip addresses available for leasing and that the lease duration of the ip addresses is too long. because it was stated that the 22.214.171.124/27 range was all that your company owned, shortening the lease duration is the only valid solution. you should not add new addresses to the existing dhcp scopes. this option is invalid because it was specifically stated that the 126.96.36.199/27 range was all that your company owned. you should not shorten the lease duration for the subnet b scope only. because the problem occurs with computers on both subnets, changing the lease length on the subnet b scope only will not be a complete solution. you should not assign static ip addresses to the new windows xp professional clients. this solution may provide immediate connectivity for computers experiencing problems, but is not a viable solution for a network where dhcp is chosen to provide ip configurations. however, using static ip addresses on some of the computers would cause conflicts in the dhcp scope. you should not configure both scope options to include the perform router discovery option. this option will only allow dhcp clients to discover their own routers. because other computers are receiving leases, it is not likely that routing is a problem. setting this option is not likely to affect the connectivity problems presented in this scenario. if a dhcp server is not found or if a lease configuration fails, a windows 2003 computer uses automatic private ip addressing (apipa) to automatically configure tcp/ip. when apipa is used, windows 2003 determines an address to use in the microsoft-reserved ip addressing range between 169.254.0.1 and 169.254.255.254. this address is used until a dhcp server is located. the subnet mask will be set to 255.255.0.0.