Soru

Zorluk: OrtaTroubleshooting IP Addressing and DHCP Services

A network technician is responding to a user ticket reporting a duplicate IP address error notification on VLAN 12 (10.12.0.0/2410.12.0.0/24). Place the following diagnostic and remediation steps in the correct chronological order from initial investigation to final resolution.

  1. 1Run `ipconfig /all` on the affected workstation to inspect its network configuration and confirm the conflicting IP address.
  2. 2Execute `ipconfig /release` on the workstation to drop the conflicting IP assignment.
  3. 3Perform an ARP scan across the subnet to map the conflicting IP address to the MAC address of the statically configured device.
  4. 4Add an exclusion range on the central DHCP server corresponding to the statically configured device's IP address.
  5. 5Run `ipconfig /renew` on the client workstation to request a new valid IP lease from the DHCP pool.

Cevap

The correct sequence begins with gathering client interface configuration details (`ipconfig /all`), releasing the conflicting IP (`ipconfig /release`), conducting an ARP scan to locate the rogue static host, adding a DHCP scope exclusion for that static IP address, and renewing the workstation lease (`ipconfig /renew`).
Following standard operating procedure, the technician first gathers diagnostic info (`ipconfig /all`) to identify the conflicting IP. Next, releasing the address (`ipconfig /release`) stops active IP collisions on the client. With the client quieted, an ARP query isolates the MAC address of the statically assigned rogue device. Defining a DHCP scope exclusion for that IP prevents the server from issuing it again. Finally, `ipconfig /renew` requests a clean IP address for the workstation.

Adım Adım Çözüm

1
Inspect local network settings on the affected host.
The exact conflicting IP address (10.12.0.4510.12.0.45) and current lease status are confirmed.
CompTIA troubleshooting methodology mandates identifying problem symptoms and gathering information prior to making changes.
2
Release the IP address lease on the client workstation using `ipconfig /release`.
The workstation stops broadcasting and listening on the conflicting IP address.
Releasing the lease clears local address binding so traffic on the subnet can be cleanly probed without interference from the client workstation.
3
Perform an ARP scan or ping test for 10.12.0.4510.12.0.45 from a remote administrative terminal.
The ARP table maps 10.12.0.4510.12.0.45 to the hardware MAC address of the statically misconfigured device.
Identifying the MAC address isolates the unmanaged static device causing the collision within the DHCP scope.
4
Configure an exclusion for 10.12.0.4510.12.0.45 in the DHCP scope settings.
The DHCP pool marks 10.12.0.4510.12.0.45 as unavailable for dynamic assignment.
Scope exclusions guarantee the DHCP server will not attempt to lease out statically assigned IP addresses.
5
Execute `ipconfig /renew` on the workstation.
The workstation successfully receives an unallocated, unique IP address from the DHCP pool.
Renewing after fixing the scope configuration restores full network connectivity without IP address collisions.

Anahtar Kavram

DHCP Address Conflict Remediation Workflow
Bu soruyu puanla