When one computer on a shared switch can ping the entire network while another only reaches half, the issue typically stems from IP address conflicts, incorrect subnet masks, or VLAN segmentation. The affected machine likely has a misconfigured network stack or is placed in a different logical broadcast domain than its peer.
Verify IP Configuration and Subnet Masks
The most common cause for this asymmetric connectivity is a mismatch in subnet definitions. If Computer A has an IP address of 192.168.1.10 with a subnet mask of 255.255.255.0, it considers all addresses from 192.168.1.1 to 192.168.1.254 as local. However, if Computer B has the same IP but a subnet mask of 255.255.255.128, it only considers addresses up to 192.168.1.127 as local. Any device beyond that range appears "remote," requiring a gateway for communication. If the default gateway is unreachable or misconfigured for that specific interface, pings to the second half of the network will fail.
To diagnose this, open a command prompt on the affected computer and run
ipconfig /all. Compare the IPv4 Address and Subnet Mask against the working computer. If the masks differ, correct the setting on the problematic machine. In many cases, this is caused by a static IP assignment that was manually entered incorrectly. Switching back to automatic (DHCP) acquisition often resolves the discrepancy immediately, ensuring both devices adhere to the same network topology rules defined by your router.
Check for IP Address Conflicts
Another frequent culprit is an IP conflict. If two devices on the same subnet are assigned the same IP address, network switches and operating systems may experience ARP table instability. This can result in intermittent connectivity where one machine responds correctly while the other drops packets or fails to establish connections to certain hosts. The working computer might be receiving fresh ARP responses, while the conflicted machine is stuck with stale entries.
You can detect conflicts by observing network behavior. If you notice random disconnections or slow response times alongside the ping failure, check the system event logs on Windows or
/var/log/syslog on Linux for messages indicating duplicate IP detection. Running
arp -a can also reveal if multiple MAC addresses are associated with a single IP address, confirming a collision. Resolving this involves identifying the rogue device and reassigning its IP address, either through DHCP reservation or manual correction.
Investigate VLAN or Port Segmentation
If both computers have identical IP configurations and no conflicts exist, the physical switch itself may be isolating traffic. Managed switches often use Virtual LANs (VLANs) to segment network traffic for security or performance reasons. It is possible that the port connected to the problematic computer is assigned to a different VLAN than the working one. In such scenarios, Layer 2 isolation prevents direct communication between the two segments, even though they share the same physical hardware.
Check the switch configuration to see if port-based VLAN assignments are active. If the switch is unmanaged, this is less likely unless it is part of a larger routed infrastructure. However, some advanced unmanaged switches offer basic QoS or isolation features that might inadvertently restrict broadcast domains. Additionally, check if Network Access Control (NAC) policies are in place, which might block devices that do not meet specific compliance standards from accessing the full network range.
DNS and Routing Table Issues
While ping uses ICMP rather than DNS, routing table errors can still mimic DNS problems. If the affected computer has a corrupted routing table, it may know how to reach local subnets but fail to route packets to others. This can happen after changing network adapters or switching between Wi-Fi and Ethernet connections. The system might prioritize a non-existent route over the correct local subnet path.
Clear the routing cache by running
route print and looking for conflicting routes. If you see multiple routes for the same destination with different metrics, remove the incorrect entry using
route delete. Furthermore, ensure that the default gateway is correctly set. As noted in similar networking challenges, a missing or unreachable default gateway can severely limit network access. For more insights on gateway issues, refer to our guide on
Default Gateway cannot be reached for networked computer.
Firewall and Security Software Interference
Local firewall software on the affected computer might be configured to drop ICMP echo requests from specific IP ranges or subnets. While this usually blocks inbound pings, some advanced firewalls can also restrict outbound traffic based on zone policies. If the computer is classified as being in a "Public" zone rather than "Private" or "Domain," strict filtering rules may apply.
Inspect the firewall settings to ensure that network discovery and file sharing are enabled for the current network profile. Disable any third-party security suites temporarily to test if they are causing the restriction. If connectivity returns, adjust the firewall rules to allow ICMP traffic across the required subnets. This step is crucial because modern security tools often default to restrictive modes to protect against unauthorized access.
Frequently Asked Questions
Why does one PC ping everything while another doesn't?
This asymmetry usually indicates a configuration mismatch, such as a different subnet mask or an incorrect default gateway. The working PC operates within the expected broadcast domain, while the failing PC is logically isolated due to its own network settings.
Can a faulty cable cause partial ping failure?
A damaged cable typically causes complete link loss or severe packet corruption leading to timeouts, rather than selective ping failures. However, if the cable supports only one pair of wires due to damage, it might affect speed but rarely isolate specific IP ranges.
How do I reset the network stack on Windows?
Open Command Prompt as Administrator and run
netsh winsock reset followed by
ipconfig /flushdns. Restart the computer afterward to apply the changes and restore default network adapter states.
Is this problem related to Starlink or ISP issues?
No, this is a local network configuration issue. While external connectivity problems like those discussed in
Troubleshooting Starlink Connectivity Issues with a Multi-WAN Router and Blocked DNS affect internet access, they do not cause internal ping discrepancies between two wired devices.
What if the switch is unmanaged?
If the switch is unmanaged, it simply forwards all traffic within the same broadcast domain. Therefore, the issue must lie in the IP configuration, firewall settings, or OS-level routing tables of the individual computers, not the switch hardware itself.