Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Download
Standard view
Full view
of .
Look up keyword
Like this
2Activity
0 of .
Results for:
No results containing your search query
P. 1
Troubleshooting DHCP Server

Troubleshooting DHCP Server

Ratings: (0)|Views: 125|Likes:
Published by farhan_abedi

More info:

Published by: farhan_abedi on Sep 06, 2010
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as DOCX, PDF, TXT or read online from Scribd
See more
See less

09/19/2010

pdf

text

original

 
Troubleshooting DHCP servers
Updated: January 21, 2005Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server2003 with SP2
Troubleshooting DHCP servers
What problem are you having?
The DHCP server is stopped.
Cause:
The DHCP server has not been authorized to operate on the network.
Solution:
Authorize the DHCP server in the enterprise where it is being used.
See also:
Cause:
Configuration details might be incorrect or missing at the server.
Solution:
If you have just completed setting up or administering the DHCP server, you might want toreview the provided checklist to see if you have missed a crucial step in the installation process.To help prevent the most common types of problems, review DHCP best practices for tips on deployingand managing your servers.Because many DHCP failures are first detected as client-side errors, you might want to start byinvestigating the problem there.
See also:
Cause:
The DHCP server has been stopped.
Solution:
Check the system event log and DHCP server audit log files for details.When the DHCP Server service either stops or cannot start, useful explanatory information about thesource of the service failure or shutdown can generally be found in these logs.
 
See also:
The DHCP server is unable to provide service to clients.
Cause:
The server is a multihomed computer and is not providing service on one or more of its networkconnections.
Solution:
Review Windows Server 2003 DHCP binding defaults for network connections based onwhether you have elected to either statically or dynamically configure TCP/IP for any or all installedconnections on the server computer. Also, review an example of multihomed DHCP server configuration tosee if you have missed any critical details.
See also:
Cause:
Scopes or superscopes on the DHCP server have not been either configured or activated for use.
Solution:
Add scopes and make sure that they are correctly configured along with any DHCP scopeoptions that need to be assigned for client use.
See also:
Cause:
The server is located on a different subnet as some of its clients and is not providing service toclients on remote subnets.
Solution:
If you are using a DHCP server in a routed network, you might want to review issues related toDHCP relay agents and the appropriate use of superscopes.
See also:
Cause:
The scope in use is full and can no longer lease addresses to requesting clients.
Solution:
If the DHCP server does not have IP addresses available to provide to its clients, it returnsDHCP negative acknowledgment messages (DHCPNAKs) to them. When this occurs, consider the followingpossible solutions:
1.
Expand the address range by increasing the
End IP address
for the current scope.2.Create a new additional scope and a superscope, then add the current scope and the new scope to thesuperscope.3.Create a new scope or extend the range. Optimally, you could renumber your current IP network.Deactivate the old scope as needed, and then configure and activate the new one.
4.
Reduce the lease duration. This can help to expedite the reclaiming of lapsed scope addresses.Other DHCP-related procedures and techniques might also help to accelerate or ease the transition froman existing scope being retired to a new scope created to take its place at the server. These include
 
deleting client leases from the scope being retired, excluding addresses from that scope, and thendeactivating it once the new scope has been activated. This ensures that the DHCP client obtains leasingfrom the new scope.
See also:
Cause:
The range of IP addresses being offered by the DHCP server is in conflict with the range of addresses being offered by another DHCP server on the network.You can confirm that this is the likely cause if DHCP server logs still indicate that DHCP negativeacknowledgment messages (DHCPNAKs) are being returned to requesting clients or if you have triedunsuccessfully at the client to renew its lease manually.
Solution:
Modify the scope address pool for the scopes at each DHCP server to ensure that scope IPaddresses do not overlap. You can add exclusions to the scopes as necessary, delete client leases, andtemporarily enable server-side conflict detection to assist in solving the problem.
See also:
One of two DHCP servers on the same subnet is not servicing clients.
Cause:
The DHCP server is not authorized in Active Directory.
Solution:
If the DHCP server is a domain member, authorize the server in Active Directory.In some circumstances you might accidentally have a standalone server and a domain member server onthe same subnet. When the standalone server detects the domain member server, it attempts to verifythat it is authorized in Active Directory. Even if a domain controller resides on the same subnet as thestandalone DHCP server, the DHCP server cannot verify its status with the domain controller because theDHCP server is not a domain member. When the standalone server is unable to access a domain controllerto discover whether it is authorized, it stops servicing clients and displays the red icon in the DHCPconsole that indicates the server is unauthorized. If you want the standalone server to service clients onthe subnet, remove the authorized DHCP server from the subnet.
See also:
The DHCP server appears to have suffered some data corruption or loss.
Cause:
The DHCP server database has become corrupted or is missing server data, possibly reportingJET database errors.
Solution:
Use DHCP server data recovery options to restore the database and correct any of the reportederrors. You can also use the Reconcile feature in the DHCP console to verify and reconcile any databaseinconsistencies that the server is able to find.

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->