Two PCs Over Ethernet to Diagnose a Network Problem

Updated 5 November 2026 · Standard formula, shown below

Connecting two PCs directly with an Ethernet cable can help determine whether a mysterious network problem is caused by a computer, a cable, or the wider network. The test works by removing the router and other network equipment from the path, then checking whether the PCs can exchange traffic and what changes when you reconnect them to the normal network.

What a direct Ethernet test can reveal

A direct connection is a simple isolation test, not a universal diagnosis. If two computers communicate over a direct cable but one cannot reach a shared device through the router, the PCs’ Ethernet interfaces and at least part of their network configuration are probably working. Attention can then shift to the router, switch, access point, cabling between rooms, address assignment, or network policies.

If the computers cannot communicate directly, that does not prove either one is defective. They may be on different IP subnets, have firewalls blocking the test, or lack a usable address. Link lights only show that the physical Ethernet link has been negotiated; they do not prove that IP communication or internet access works.

The test also has limits: a direct cable bypasses the router’s routing, DHCP service, firewall, and other network functions. It cannot, by itself, identify which of those is responsible for a failure on the normal network.

Prepare the PCs and cable

Use an Ethernet cable that fits both PCs, and connect it directly between their Ethernet ports. Most modern Ethernet interfaces support auto-MDI-X, so a standard cable generally works; older equipment may require a crossover cable. If either PC lacks an Ethernet port, a compatible USB-to-Ethernet adapter is an option, though it adds another component to check.

Note how each PC is normally connected: Ethernet, Wi-Fi, or both.
Record its current IP address, subnet mask, default gateway, and DNS settings before changing anything. On Windows, ipconfig /all displays these details in Command Prompt.
Temporarily disconnect Wi-Fi during the direct test, or make sure you know which adapter is carrying the test traffic. Otherwise, a successful ping may travel over Wi-Fi rather than the Ethernet cable.
Do not bridge the direct connection to an internet-connected interface or enable Internet Connection Sharing unless you specifically intend to share a connection.

Disconnecting the cable from the router does not require changing router settings. If you do adjust adapter settings, make a note of the original configuration and restore it afterward.

Give the direct link compatible addresses

Ethernet provides the physical link, but PCs also need compatible IP addresses to communicate using IP. When two computers are connected directly, there is usually no DHCP server to assign addresses automatically. They may assign themselves IPv4 link-local addresses, commonly in the 169.254.0.0/16 range, but this is not guaranteed to produce a convenient or successful test.

For a controlled IPv4 test, set temporary manual addresses on the Ethernet adapters, using the same subnet and different host addresses. For example, use 192.168.50.1 on PC A and 192.168.50.2 on PC B, with subnet mask 255.255.255.0 on both. Leave the default gateway and DNS fields empty for this isolated test. These example addresses are for the direct link; do not use them if they conflict with an existing network configuration.

On Windows, find the Ethernet adapter under Settings > Network & internet > Ethernet, then open its IP assignment settings to configure IPv4 manually; labels can vary by Windows version. On macOS, open System Settings > Network, select Ethernet, and use its TCP/IP settings. If you are unfamiliar with manual addressing, consult the operating system’s current help before changing settings.

Test communication in stages

Check the Ethernet port indicators, if present, and confirm the operating system reports a connected link. A missing link suggests checking the cable, adapter, port, or hardware.
Confirm each PC has the intended Ethernet IP address and subnet mask. On Windows, run ipconfig; on macOS, inspect the Ethernet service in Network settings or use a network-status command.
From one PC, ping the other PC’s address—for example, ping 192.168.50.2 from PC A. Then try the reverse direction. A reply confirms that ICMP traffic passed between them.
If the ping fails, check the address and mask, ensure Wi-Fi is not confusing the result, and check whether the operating system firewall permits the test. Firewalls commonly block incoming ping requests even when other communication is possible.
If the goal is file sharing, test that separately after basic connectivity works. Enable only the sharing features you need, use appropriate account permissions, and avoid making a private network’s shared folders accessible on a public network.

A failed ping is not conclusive: a firewall may suppress ping replies. Likewise, a successful ping confirms only a narrow kind of connectivity; it does not prove that file sharing, DNS, or internet access works.

Compare the direct test with the normal network

Once the direct test is complete, restore the PCs’ original IP settings, reconnect them to their usual network, and repeat relevant checks. If direct communication works but the original connection fails, compare the devices’ addresses and gateways on the normal network. A PC with an address beginning 169.254 often did not receive an IPv4 address from DHCP, which points toward a possible link, DHCP, or configuration issue—not necessarily a faulty PC.

Useful comparisons include whether both computers fail or only one, whether the problem occurs on Ethernet and Wi-Fi, and whether devices on the same local network can communicate. If a PC can reach the router but not the internet, the problem lies beyond the basic PC-to-router link; possible causes include router configuration, the internet connection, DNS, or an upstream outage. If only one wired port or room connection fails, test a known-good cable and another router or switch port before replacing equipment.

Common causes and what the test cannot prove

Address conflicts, mismatched subnets, disabled adapters, damaged cables, restrictive firewall rules, and incorrect network profiles can all make a working connection appear broken. A cable can also pass enough signal to show link while still producing unreliable performance. For intermittent faults, note when failures occur and look for packet loss, rather than relying on one successful ping.

Remember that the direct setup deliberately removes the router. It cannot test the router’s DHCP or DNS services, wireless coverage, internet-facing connection, or rules between network segments. To investigate those, test each component in the normal path: PC to router, router to another local device, and router to the internet. Avoid disabling the firewall entirely as a shortcut; if a firewall is involved, make a narrow, temporary rule for the specific test and restore the original protection.

Frequently Asked Questions

Can I connect two PCs directly with an Ethernet cable?
Yes. Most modern Ethernet ports work with a standard Ethernet cable and automatically handle the pair configuration. Older equipment may need a crossover cable or an intermediate switch.

Do two PCs need a router to communicate?
No. They can communicate over a direct cable if their network interfaces are enabled and their IP configuration is compatible. A router is normally needed for DHCP, routing to other networks, and often internet access.

Why do I see a 169.254 address?
That is an IPv4 link-local address, often assigned when a device cannot obtain an address from DHCP. On a direct link it may be expected, but the two computers still need compatible addresses and firewall settings to communicate.

Does a successful ping prove the internet is working?
No. A ping between two PCs tests local IP communication only. Internet access also depends on the router, its upstream connection, and potentially DNS and firewall settings.

Should I turn off the firewall to test the cable?
Usually not. First verify link status and IP settings. If ping is blocked, use a narrowly scoped temporary firewall allowance if appropriate, then remove it; do not leave the firewall disabled.

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.