iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
A Wi-Fi or “connected” indicator does not prove that a website, app, or network service can be reached. To find the fault, test from the device outward: check the local connection and IP settings, then the gateway, external IP connectivity, DNS, and finally the exact service that is failing. A failed ping or a single unresponsive route hop is only one clue—not a diagnosis.
First, define what is failing
Before changing settings, narrow the symptom. A problem affecting one app on one device calls for different checks than a failure across every device on the network.
- Does it affect one device or several? If possible, test another device on the same network.
- Does one website or app fail, or do multiple unrelated destinations fail?
- Does the same device work over Ethernet, another Wi-Fi network, or a phone hotspot?
- What exact error appears, when did it occur, and is it constant or intermittent?
A device can be connected to Wi-Fi while lacking a working route to the internet. It can also reach the internet while one app, destination, or service fails. Record the current configuration and results before renewing an address, resetting networking, or changing security settings; that record can help identify what changed and is useful when escalating.
Check the local connection and IP configuration
Confirm that the intended network interface is enabled, the device is connected to the expected network, and airplane mode is off. On Windows, open Command Prompt and run:
#1 Best Overall
- Cable performance testing up to 10GBASE-T plus troubleshooting (distance to fault, wire map, toning)
- Network features include IPv4 and v6 ping, nearest switch diagnostics (IP address, name, port / VLAN number, and advertised data rates).
- Ethernet Alliance-certified PoE Verification detects the PoE class (1-8) and power, and performs a load test of available PoE from the connected switch
- Wi-Fi analysis to Wi-Fi 6E, including networks, channels, and access points
ipconfig /all
For the active adapter, inspect the IP address, subnet mask, default gateway, DNS server, and connection-specific DNS suffix where applicable. Compare them with the values expected on that network. An absent or unexpected gateway or DNS server can point to a local configuration or address-assignment problem; an address alone does not prove that the rest of the path works.
If the device uses automatic (DHCP) configuration, renewing its address may help when the lease or assigned settings are stale. Record the existing values first, and avoid network resets until the simpler checks have narrowed the issue. On a wired connection, trying another cable can help isolate a physical link fault; it will not fix DNS, routing, firewall, VPN, or remote-service problems.
Test connectivity in layers
Work outward from the device. On Windows, ping can test reachability using ICMP, but the network or destination may block those probes. A timeout therefore does not, by itself, establish that the connection is broken.
Free tools Windows power users keep installed
One-click scans. No signup required.
Rank #2
- Cable performance testing up to 10GBASE-T plus troubleshooting (distance to fault, wire map, toning)
- Network features include IPv4 and v6 ping, nearest switch diagnostics (IP address, name, port / VLAN number, and advertised data rates).
- Ethernet Alliance-certified PoE Verification detects the PoE class (1-8) and power, and performs a load test of available PoE from the connected switch
- Wi-Fi analysis to Wi-Fi 6E, including networks, channels, and access points
- Test the local gateway. Use the default gateway shown by
ipconfig /allas the target for a ping. A reply indicates that the gateway answered an ICMP probe from the device; no reply may mean the gateway is unreachable, or simply that it does not answer ping. - Test a known external IP address. If the gateway responds but an external IP does not, investigate the route beyond the local network, network policy, or the destination’s handling of ICMP. Do not infer that a specific website is down from this test alone.
- Test a hostname. If an external IP test works but a hostname fails, investigate name resolution. On Windows, query a hostname with
nslookup; by default it reports the DNS server being used and the response it receives. Compare the result with the exact destination name that is failing.
These tests separate useful clues: a gateway check concerns the local path, an external IP check avoids hostname lookup, and a hostname query tests DNS behavior. None proves that a particular application protocol or destination service is healthy.
Check the failing app, destination, and port
If only one site or app fails, verify that the destination name is correct and determine which service and port the app needs. A TCP connection test to that service’s listening port is more relevant than ping when the application uses TCP: ICMP may be blocked even when the service works, and a ping reply does not prove that the application port is open.
- If the service port cannot be reached, check whether the service is listening and whether a firewall, proxy, VPN, antivirus network filter, or other connection-monitoring software is affecting the path.
- If the port connects but the app still fails, focus on the application, its account or configuration, and the response it receives rather than treating the result as a general internet outage.
- If the problem occurs only with a VPN or security tool enabled, compare behavior with the network administrator’s approved settings. Do not disable managed protections or bypass workplace policy to run a test.
Windows’ “connected” state and an application’s own status can disagree with actual browsing or service access. Microsoft’s Network Connectivity Status Indicator documentation notes that an apparent “no internet” result in an app while websites work can be an NCSI issue, rather than proof that internet access is unavailable.
Rank #3
- Performance testing on EtherNet/IP, PROFINET, EtherCAT and other Industrial Ethernet cabling plus troubleshooting (distance to fault, wire map, toning)
- Network features including: IPv4 and v6 ping, nearest switch diagnostics (IP address, name, port / VLAN number, and advertised data rates).
- Ethernet Alliance certified PoE Verification – Detects the PoE class (1-8) and power, and performs a load test of available PoE from the connected switch
- Wi-Fi analysis to Wi-Fi 6E, including networks, channels, and access points
Use route diagnostics carefully
When results suggest a problem beyond the device, inspect the path toward the destination. Windows uses tracert; Linux and macOS commonly use traceroute when installed. MTR, where available, combines route discovery with repeated measurements, showing latency and reported loss at hops over time.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsA router may not answer diagnostic probes even while forwarding ordinary traffic. An asterisk or apparent loss at one intermediate hop is not enough to assign blame: the router may be filtering or deprioritizing probes. Look for whether the destination itself is affected and whether the pattern persists across repeated observations. Packet loss can arise from local policy or security software, resource limits, missing routes, congestion, remote policy, a lost session, or MTU-related drops; a single hop result cannot distinguish these causes.
Platform-specific checks
Windows
Use Get Help’s network troubleshooter where it is available, and check Wi-Fi state, airplane mode, and the selected network. After recording the current configuration, use ipconfig /all to inspect addressing and nslookup to examine DNS responses. Windows also provides DHCP renewal and TCP/IP or Winsock reset options, but these change network state and are best reserved for cases where basic tests indicate a local configuration problem. For advanced diagnosis, Windows guidance includes Packet Monitor (pktmon), netsh trace, and packet captures.
Rank #4
- PREMIUM 3-YEAR ASSURANCE BUNDLE – Get the full power of the SignalTEK QT Pro with the added security of a total of 3-year warranty and a heavy-duty rugged hard carry case. This professional bundle is designed to protect your investment in the harshest field environments.
- EXPANDED COPPER & FIBER TESTING – Includes a full set of 12 remote IDs (Male & Female #1-12) for high-volume copper testing up to 10Gb/s. Qualify fiber links up to 100Gb/s with included High-Stability Single-mode (1310nm) and Multimode (850nm) SFP modules and Cable Tracing Probe.
- ADVANCED WI-FI & NETWORK DIAGNOSTICS – Perform comprehensive Wi-Fi site surveys and troubleshooting using both internal and external antennas. Identify channel conflicts, locate hidden APs, and verify network performance across 2.4GHz and 5GHz bands.
- 90W POE LOAD TESTING & TOOLS – Validate PoE power delivery up to 90W (802.3 af/at/bt) with actual load testing. Built-in network tools include VLAN detection, Device Discovery, Ping, Traceroute, and Switch Port identification for rapid troubleshooting.
- CLOUD MANAGEMENT & REMOTE SUPPORT – Manage projects and share professional PDF reports instantly via TREND AnyWARE Cloud. Features integrated TeamViewer and VNC support, allowing off-site managers to assist technicians in real time.
macOS
Apple’s Wi-Fi guidance recommends checking the selected Wi-Fi network, restarting the Mac or renewing its address, and verifying date and time. Also check for macOS updates, router firmware updates, VPNs, or other software that monitors or interacts with network connections. Wi-Fi Recommendations and Wireless Diagnostics can help identify certain wireless issues; Recommendations may not be available on personal hotspots or some enterprise-security networks. If practical, compare with another network, then contact the ISP if the problem appears to extend beyond the device and local network.
Linux and other environments
Check the active interface, its IP configuration, gateway, and DNS settings using the tools provided by the distribution and network manager. Use traceroute or MTR if installed to examine the route. Configuration interfaces and commands vary, so do not assume a particular network manager or apply Windows reset steps to another operating system.
Recommended Free Tools
Escalate with evidence, not just “the internet is down”
If the fault remains unclear, capture the failure while it happens. A packet capture or platform trace can show whether traffic leaves the device, where a response stops, or whether an endpoint sent a reset. Microsoft notes that simultaneous captures at the source and destination can help identify where a packet disappears or which endpoint reset a connection.
Best Value
- Multifunctional Network Cable Tester: TESMEN TLP-123A Supports RJ45 and RJ11, enabling rapid detection of line connectivity, short circuits, open circuits, miswiring, and cable shielding status. An essential tool for troubleshooting line faults and network maintenance, it effectively boosts your work efficiency
- Convenient and Efficient: Featuring one-button operation and a test speed adjustment gear on the main control unit for enhanced flexibility. Clear LED indicators provide intuitive test result displays, making it easy for both professionals and home users to operate
- Portable and Durable: Compact and lightweight design for easy portability. Constructed with high-quality plastic housing for robust structure, ensuring both durability and stability. Ideal for home wiring, IT equipment setup, electrical maintenance, and LAN DIY projects
- Detachable design: The main control unit and remote unit can be separated and used independently, allowing you to test both ends of long cables. This makes it ideal for wall-mounted ports, long-distance cabling, or structured cabling systems, perfect for homes, offices, or professional IT environments
- What you will get: 1 * TLP-123A Network Cable Tester, 1 * user manual, 2 * AAA batteries
Give the network administrator, application provider, or ISP a concise record:
- Exact time and time zone of the failure, and whether it was intermittent.
- Destination name, service or port if known, and the exact error message.
- Whether other devices, destinations, networks, or wired access work.
- Relevant IP configuration, DNS query results, and gateway or external tests, noting that ping uses ICMP.
- Route observations or a capture/trace, if collected, and any VPN or security software in use.
Packet captures can contain sensitive information, so share them only through an approved support channel and follow your organization’s handling rules.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.

