| Action | Verification Command | |--------|----------------------| | Confirm physical connectivity | ping 127.0.0.1 (loopback) | | Release current DHCP lease | ipconfig /release (optional) | | Identify critical static IP settings | ipconfig /all (document existing static config) | | Close all network‑dependent applications | N/A | | Open an elevated (administrator) command prompt | Right‑click Command Prompt → Run as administrator | Resetting TCP/IP will remove any custom settings (e.g., static IPs, custom DNS entries, manual routing table modifications). Have this information backed up. 4. Primary Method: Using netsh int ip reset The Windows built‑in tool netsh (Network Shell) provides a dedicated command to reset TCP/IP components. 4.1. Execute the Reset At an elevated command prompt, type:
If external ping works but DNS fails, check that the DNS Client service is running: how to reset tcp ip
sc query dnscache For help desk deployment, consolidate the full reset into an administrative script: Primary Method: Using netsh int ip reset The
| Test | Command | Expected Result | |-------|---------|------------------| | Loopback | ping 127.0.0.1 | 0% loss | | Local IP | ping <your_ip> | 0% loss | | Gateway | ping <default_gateway> | ≤1% loss | | External | ping 8.8.8.8 | 0% loss | | DNS resolution | nslookup microsoft.com | Non‑authoritative answer | | Connectivity | curl https://example.com | Returns HTML (or Invoke-WebRequest in PowerShell) | custom DNS entries