Your desktop or laptop cannot ping over a wired Ethernet connection while Wi-Fi works because the wired interface is likely assigned to a different network profile, has an incorrect IP subnet configuration, or is blocked by firewall rules that treat the local area network as untrusted. This discrepancy often arises when Windows or macOS classifies the Ethernet connection as "Public" instead of "Private," isolating it from other devices on the same physical switch or router.
Verify Physical Link and Driver Status
Before diving into software configurations, ensure the physical layer is functioning correctly. A link light that is off indicates a broken cable, a faulty port, or a disabled network adapter in the BIOS. If the lights are blinking but pings fail, the issue is almost certainly software-related. Check your operating system’s network settings to confirm the Ethernet adapter is enabled and not showing an "Unidentified Network" status, which typically signals a lack of DHCP lease or a driver mismatch.
Update your network card drivers from the manufacturer’s website rather than relying solely on automatic updates. Outdated drivers can cause compatibility issues with modern switches or routers, leading to packet loss that prevents ICMP echo requests (pings) from succeeding. In Device Manager, look for any yellow exclamation marks next to the Ethernet controller. If present, right-click and select "Update Driver."
Check Network Profile Classification
One of the most common reasons for successful Wi-Fi pings but failed Ethernet pings is the network profile setting. Operating systems like Windows 10 and 11 automatically assign network profiles based on connectivity type. Wi-Fi might be set to "Private," allowing file sharing and discovery, while Ethernet defaults to "Public," which blocks incoming connections for security.
To fix this, navigate to your network settings. In Windows, go to Settings > Network & Internet > Ethernet. Click on the connected network and change the network profile type from "Public" to "Private." This action tells the OS to trust the network, enabling necessary services like NetBIOS and ICMP responses. On macOS, open System Preferences > Network, select Ethernet, and ensure the service is active. While macOS does not use the same Public/Private terminology, you should verify that the firewall is not blocking incoming connections specifically for the Ethernet interface.
Troubleshooting Fritzbox Router Broadcasting Issues
Validate IP Configuration and Subnets
Even if both devices are connected to the same router, they must reside on the same IP subnet to communicate directly via ping. Verify the IP address of both machines using
ipconfig on Windows or
ifconfig /
ip addr on Linux/macOS. Ensure both devices have IPs in the same range, such as
192.168.1.x, with the same subnet mask (typically
255.255.255.0).
If one device shows an APIPA address starting with
169.254.x.x, it means it failed to obtain an IP from the DHCP server. This can happen if the Ethernet cable is plugged into a VLAN port that is isolated or if the router’s DHCP pool is exhausted. Release and renew the IP address by running
ipconfig /release followed by
ipconfig /renew in the command prompt. Alternatively, try assigning a static IP within the correct subnet to rule out DHCP issues entirely.
Inspect Firewall and Antivirus Rules
Firewalls are designed to block unauthorized access, and they often treat wired connections differently than wireless ones due to perceived security risks. Even if your general firewall is open, specific rules may be blocking ICMP traffic. Temporarily disable your third-party antivirus firewall to see if pinging resumes. If it does, create an exception for ICMP Echo Request packets in your firewall settings.
In Windows Defender Firewall, ensure that "File and Printer Sharing" is allowed on Private networks. You can test this by temporarily turning off the firewall completely; if pinging works, re-enable it and carefully configure the inbound rules to allow ICMPv4 and ICMPv6. Some enterprise-grade firewalls or endpoint protection suites install kernel-level drivers that intercept traffic before the OS firewall, so check those applications specifically for network isolation features.
Diagnose Switch and Router Port Issues
If software settings are correct, the issue may lie with the network infrastructure. Managed switches often have port security features enabled by default, such as storm control or MAC address filtering, which can drop ping packets if the source MAC address changes rapidly or if broadcast traffic exceeds a threshold. Check the switch logs if you have administrative access.
Additionally, some routers isolate clients on different ports for guest networking purposes. Ensure that both computers are plugged into the LAN ports of the main router and not into a secondary access point configured in AP mode with client isolation enabled. If you are using a mesh system, verify that the wired backhaul is active and not causing routing loops or ARP table conflicts.
Wifi Keep Disconnecting After Sometime (Wireless Adapter or Access Point)
Test with Cable Replacement and Port Swapping
Physical media failures can manifest as intermittent connectivity or complete inability to establish a stable session for protocols requiring handshakes. Swap the Ethernet cable with a known-good Cat5e or Cat6 cable. Try plugging into a different port on the router or switch to rule out a damaged RJ45 jack.
Use a cable tester if available to check for crossed wires or shorts. While modern auto-MDI/MDIX ports handle crossover issues automatically, a severely damaged cable may still fail to maintain the electrical signal integrity required for consistent ICMP replies. If possible, connect one computer directly to the other using a standard Ethernet cable to bypass the router entirely. If pinging works in this direct setup, the problem is definitely with the router or switch configuration.
Frequently Asked Questions
Why can I browse the web over Ethernet but not ping?
Web browsing uses TCP ports 80 and 443, which are typically allowed by default through NAT and firewalls. Ping uses ICMP protocol, which is often blocked by stricter security policies or misconfigured firewalls that only permit application-layer traffic.
Does disabling IPv6 help with Ethernet ping issues?
Sometimes, dual-stack configurations where both IPv4 and IPv6 are active can cause routing confusion. Disabling IPv6 temporarily forces the system to use IPv4 exclusively, which can resolve ARP resolution failures or prefix delegation issues on certain ISPs.
How do I clear the ARP cache to fix ping errors?
Stale ARP entries can cause pings to fail if the MAC address of the gateway or target device has changed. Run
arp -d * in an elevated command prompt to clear the cache, forcing the system to request fresh MAC-to-IP mappings.
Can a VPN cause Ethernet ping failures?
Yes, many VPN clients route all traffic through the tunnel, including local LAN pings. Check your VPN settings to ensure "Local LAN Access" or "Split Tunneling" is enabled, allowing local network traffic to bypass the encrypted tunnel.
What is the difference between a public and private network profile?
A public network profile assumes the network is untrusted and disables file sharing, network discovery, and allows fewer incoming connections. A private profile trusts the network environment, enabling these features which are essential for device-to-device communication like pinging.