DHCP, Process: Classification and initial support

Process: Classification and initial support

Description

Incidents must be classified so they can be handled as effectively as possible with the appropriate resolution taken. Classification is the process of categorizing and prioritizing a given incident. It is a very important first stage in incident management as it determines the subsequent action to be taken.

Task: Service desk steps to eliminate the DHCP server/service as causing the issue

Purpose

The following procedures provide supplemental diagnostics to quickly eliminate the DHCP server as a cause for a given issue. Unlike troubleshooting guides, which help to solve specific DHCP problems, these steps assist service desk operators in focusing on the actual incident areas.

If the following procedures are run successfully, the DHCP server/service is not the likely cause of an issue.

Procedure 1: Verify if the client is configured for DHCP

To verify if the client is configured for DHCP via GUI

1. Access the client system either physically or via Terminal Services.
2. Open Control Panel by clicking Start, then Run, typing Control.exe and clicking OK.
3. Double-click Network Connections, select the appropriate network interface, and click Properties.
4. Double-click Internet Protocol (TCP/IP), which will open the Internet Protocol (TCP/IP) Properties window.
5. Verify that Obtain an IP address automatically and Obtain DNS server address automatically are selected.
6. Click the DNS tab and verify the entry for DNS suffix for this connection is correct.

To verify if the client is configured for DHCP via command line

1. Access the client system either physically or via Terminal Services.
2. Start a command line by clicking Start, then Run, typing cmd and clicking OK.
3. At the prompt, type the command:
   

   netsh interface ip show config	

Procedure 2: Verify DHCP server is up and responding to requests

1. Access the DHCP client system.
2. Start a command line by clicking Start, then Run, typing cmd and clicking OK.
3. At the prompt, type the commands:
   

   ipconfig/renew all
   netsh diag show dhcp/v	

4. Verify that the correct DHCP server responded with appropriate response times. Slow connections may cause timeouts and DHCP configuration may not be processed.

Procedure 3: Verify accuracy of dispensed configuration

To verify the accuracy of dispensed configuration via GUI

1. Access the client system either physically or via Terminal Services.
2. On the Start menu, click Run. Type Control.exe, and then click OK.
3. Double-click Network Connections, select the appropriate network interface, and click Properties.
4. Double-click Internet Protocol (TCP/IP), which will open the Internet Protocol (TCP/IP) Properties window.
5. Verify the information shown in this Properties window, and click Advanced.
6. Verify the information shown in this Advanced TCP/IP Settings window: IP Settings, WINS, and Options tabs.
7. Click the DNS tab and verify the nameserver addresses, and that the entry for DNS suffix for this connection is correct.

To verify the accuracy of dispensed configuration using command line

1. Access the client system either physically or via Terminal Services.
2. Start a command line by clicking Start, then Run, typing cmd and clicking OK.
3. At the prompt, type the commands:
   

   ipconfig /all
   netsh interface ip show config	

4. These commands output the configuration of the all network devices, including DHCP-configured interfaces. Verify that the configuration is correct, including:
   ● IP address issued
   ● WINS server
   ● DNS server
   ● Default gateway
   ● Suffixes
   ● Options

Dependencies

None

Technology Required

Base DHCP Windows Server 2003