Many Windows 11 users encounter a frustrating issue where the Ethernet connection remains stuck on the "Identifying" status. This loop indicates that while the operating system detects the network interface, it fails to complete the necessary configuration to establish a stable connection. Typically, this happens when the computer cannot obtain a valid network address from the DHCP server. If left unaddressed, Windows may assign an Automatic Private IP Addressing (APIPA) address, usually in the 169.254.x.x range, which prevents internet access.
Initial Physical Diagnostics
Before diving into complex software settings, it is crucial to verify the physical layer of the connection. Start by checking the link lights on both the Ethernet port of your computer and the corresponding port on your router or switch. If these lights are off or blinking irregularly, the issue is likely hardware-related. Try swapping the Ethernet cable with a known-good one and test a different port on your router. A damaged connector or a worn-out docking station port can mimic software faults. Remember that standard twisted-pair Ethernet cables are generally limited to 100 meters, but for most home offices, a short Cat5e or Cat6 cable is sufficient for a 1 Gbps link.
Inspecting Network Configuration
Once physical connections are verified, inspect the software configuration. Navigate to Settings > Network & internet > Ethernet to check the current status. For a deeper analysis, open Command Prompt as an administrator and run the command ipconfig /all. Look for your Ethernet adapter in the output. A healthy connection will display a valid IPv4 address, subnet mask, default gateway, and DNS servers. If you see an address like 169.254.22.8 with no gateway, it confirms that the DHCP exchange failed. Record these details before making any changes, as they provide a baseline for troubleshooting.
Resetting the TCP/IP Stack
If the DHCP lease is corrupted, you can reset the network stack to force a fresh address assignment. Open Windows Terminal or Command Prompt as an administrator and execute the following commands in sequence:
netsh int ip resetipconfig /releaseipconfig /renewarp -d *
The netsh command resets TCP/IP parameters, while the ipconfig commands release the current lease and request a new one. The arp command clears the local cache of IP-to-hardware mappings. After running these, restart your computer. Note that the connection will briefly drop during this process, so save your work first.
A successful gateway test shows local routing is working, while a successful 1.1.1.1 test shows that traffic can reach the internet.
Verifying Drivers and Services
If the issue persists, the problem may lie with the network adapter driver. Open Device Manager, expand Network adapters, and right-click your wired adapter to select Properties. Check the device status on the General tab and note the driver version. On the Power Management tab, temporarily disable the option to allow the computer to turn off the device to save power. You can also disable and then re-enable the device to restart the adapter without changing its permanent configuration. If a warning icon appears, uninstalling the device and restarting Windows may allow the system to rediscover and reinstall the correct driver.
Conclusion
Resolving the "Identifying" loop requires a methodical approach, starting with physical checks and moving to software resets. By verifying cable integrity, inspecting IP configurations, and resetting the TCP/IP stack, most users can restore connectivity without replacing hardware. If these steps fail, consider checking if your router's DHCP server is offline or out of address space, as Windows cannot repair a server that is not functioning correctly.