A desktop support technician is troubleshooting a Windows 11 workstation that cannot access local network resources following a subnet migration. To resolve potential IP address lease conflicts and clear stale name resolution records, the technician must execute a series of network diagnostic utilities from an administrative Command Prompt. In what order should the technician execute the steps below to release the old network lease, acquire a new IP configuration from the DHCP server, purge stale domain mappings, and inspect the cleared resolver cache?
- 1Execute `ipconfig /release` to drop the current dynamic IP address assignment and inform the DHCP server that the lease is relinquished.
- 2Execute `ipconfig /renew` to broadcast a request and obtain a new IP address configuration from the active DHCP server.
- 3Execute `ipconfig /flushdns` to purge all cached host-to-IP address mapping entries from the local DNS client resolver cache.
- 4Execute `ipconfig /displaydns` to review the current contents of the DNS resolver cache and verify that stale entries have been purged.
Cevap
The correct sequence begins by releasing the existing lease using `ipconfig /release`, requesting a new lease via `ipconfig /renew`, clearing stale DNS cache entries with `ipconfig /flushdns`, and finally verifying the cache status using `ipconfig /displaydns`.
In Windows networking, resetting client network connectivity following subnet changes requires a logical progression: first, `ipconfig /release` disassociates the old IP parameters; second, `ipconfig /renew` fetches fresh parameters from the DHCP server; third, `ipconfig /flushdns` clears outdated host mappings from memory; and fourth, `ipconfig /displaydns` allows the technician to verify the cache state.
Adım Adım Çözüm
Anahtar Kavram
Windows Network Command-Line Diagnostics (ipconfig parameters)