Home › Docs › How to Troubleshoot IPv4 Connectivity Issues

How to Troubleshoot IPv4 Connectivity Issues

When you encounter IPv4 connectivity problems, it can disrupt your ability to access the internet and network resources. This comprehensive guide provides a systematic approach to diagnose and resolve IPv4 connectivity issues, covering common problems from DHCP failures to firewall misconfigurations across Windows, macOS, and Linux systems.

If you're also experiencing IPv6 connectivity issues, see our dedicated guide for IPv6 troubleshooting.

Quick Diagnostic Checklist

Before diving into detailed troubleshooting, use this checklist to quickly assess your IPv4 connectivity status:

Understanding IPv4 Connectivity Problems

Common Symptoms

When IPv4 connectivity fails, you may experience:

Root Causes

IPv4 connectivity issues typically stem from:

Step 1: Verify the Problem with Online Testing

Start here every time. Before making any changes, confirm that you have an IPv4 connectivity problem and understand its scope.

Visit test-ipv6.run to run comprehensive connectivity tests. This tool tests:

What the results mean:

If the test confirms IPv4 connectivity failure, proceed to the next steps to diagnose the root cause.

Step 2: Check Physical Connections

Physical connectivity issues are surprisingly common and should be ruled out first.

Wired Connections (Ethernet)

Check cable connections:

Test the cable:

Wireless Connections (Wi-Fi)

Check signal strength:

Verify wireless is enabled:

Network Adapter Status

Windows:

  1. Open Network Connections (ncpa.cpl)
  2. Verify your adapter shows "Enabled" status
  3. If disabled, right-click and select "Enable"

macOS:

  1. System Preferences > Network
  2. Verify your connection shows "Connected" with a green dot

Linux:

ip link show

Look for "state UP" on your network interface.

Step 3: Verify IPv4 Address Assignment

A valid IPv4 address is essential for network connectivity. Check your IP configuration across different operating systems.

Windows: Check IP Configuration

View your IP address:

ipconfig /all

What to look for:

Problem indicators:

macOS: Check IP Configuration

View your IP address:

ifconfig en0

Or for a summary:

ipconfig getifaddr en0

Check IP configuration in GUI:

  1. Open System Preferences > Network
  2. Select your active connection
  3. View the IP address, Subnet Mask, and Router (gateway)

Linux: Check IP Configuration

Modern method (ip command):

ip addr show

View specific interface:

ip addr show eth0

Traditional method (ifconfig):

ifconfig

Check routing table:

ip route show

Look for a default route like: default via 192.168.1.1 dev eth0

Understanding Address Types

Valid Private IPv4 Ranges:

APIPA (Automatic Private IP Addressing):

If you have an APIPA address, proceed to Step 4 to fix DHCP issues.

Step 4: Troubleshoot DHCP Issues

DHCP (Dynamic Host Configuration Protocol) automatically assigns IP addresses to devices. When DHCP fails, you get an APIPA address or no connectivity.

Common DHCP Problems

DHCP server unavailable:

DHCP configuration errors:

Renew DHCP Lease

Force your device to request a new IP address from the DHCP server.

Windows:

ipconfig /release
ipconfig /renew

macOS:

sudo ipconfig set en0 DHCP

Or through GUI:

  1. System Preferences > Network
  2. Select connection > Advanced > TCP/IP
  3. Click "Renew DHCP Lease"

Linux (DHCP client dependent):

For dhclient:

sudo dhclient -r eth0
sudo dhclient eth0

For NetworkManager:

sudo nmcli connection down "Connection Name"
sudo nmcli connection up "Connection Name"

Check Router DHCP Configuration

Access your router:

  1. Open a web browser
  2. Navigate to your router's IP address (commonly 192.168.1.1 or 192.168.0.1)
  3. Log in with admin credentials

Verify DHCP settings:

Check DHCP client list:

Configure Static IP (Temporary Workaround)

If DHCP continues to fail, temporarily configure a static IP to restore connectivity while troubleshooting.

Windows:

  1. Network Connections > Right-click adapter > Properties
  2. Select "Internet Protocol Version 4 (TCP/IPv4)" > Properties
  3. Select "Use the following IP address"
  4. Enter:
    • IP address: 192.168.1.100 (choose unused IP in your subnet)
    • Subnet mask: 255.255.255.0 (match your network)
    • Default gateway: 192.168.1.1 (your router's IP)
    • DNS servers: 8.8.8.8 and 8.8.4.4 (Google DNS)

macOS:

  1. System Preferences > Network > Advanced > TCP/IP
  2. Configure IPv4: Manually
  3. Enter IP address, Subnet Mask, Router
  4. Go to DNS tab and add DNS servers: 8.8.8.8, 8.8.4.4

Linux: Edit network configuration (method varies by distribution):

For NetworkManager-based systems:

sudo nmcli connection modify "Connection Name" ipv4.method manual ipv4.addresses 192.168.1.100/24 ipv4.gateway 192.168.1.1 ipv4.dns "8.8.8.8 8.8.4.4"
sudo nmcli connection up "Connection Name"

Important: Remember to switch back to DHCP after resolving the underlying issue.

Step 5: Test Default Gateway Connectivity

The default gateway (your router) routes traffic between your local network and the internet. Gateway problems prevent external connectivity even when local network works.

Find Your Default Gateway

Windows:

ipconfig | findstr /i "Gateway"

macOS:

netstat -nr | grep default

Or:

route -n get default

Linux:

ip route | grep default

Or:

route -n

The default gateway is typically 192.168.1.1, 192.168.0.1, or 10.0.0.1.

Test Gateway Reachability

Ping your default gateway:

Windows/macOS/Linux:

ping 192.168.1.1

(Replace 192.168.1.1 with your actual gateway IP)

Expected results:

Troubleshoot Gateway Problems

If ping fails:

  1. Check router is powered on and functioning

    • Verify router lights indicate normal operation
    • Try accessing router admin interface via browser

  2. Verify correct gateway IP

    • Confirm you're pinging the correct address
    • Check router documentation for default gateway IP

  3. Check firewall blocking ICMP

    • Some routers/firewalls block ping by default
    • Try accessing router web interface as alternative test

  4. Network path issues

    • Verify network switch is functioning (if applicable)
    • Test direct connection to router (bypass switches)

  5. Restart network equipment

    • Power cycle modem and router
    • Wait 30 seconds before powering back on
    • Wait for full startup (2-5 minutes)

Add Default Route Manually (Advanced)

If default gateway is missing from routing table:

Windows:

route add 0.0.0.0 mask 0.0.0.0 192.168.1.1

Linux:

sudo ip route add default via 192.168.1.1 dev eth0

macOS:

sudo route add default 192.168.1.1

Step 6: Test DNS Resolution

DNS (Domain Name System) translates domain names to IP addresses. DNS failures prevent accessing websites by name even when internet connectivity works.

Understanding DNS Issues

Symptoms of DNS failure:

Test DNS Resolution

Windows:

nslookup google.com

macOS/Linux:

nslookup google.com

Or using dig:

dig google.com

Expected output:

If DNS lookup fails:

Test Direct IP Connectivity

Verify internet connectivity works without DNS:

Ping a public IP address:

ping 8.8.8.8

Results interpretation:

Flush DNS Cache

Clear stale or corrupted DNS cache entries.

Windows:

ipconfig /flushdns

macOS:

sudo dscacheutil -flushcache
sudo killall -HUP mDNSResponder

Linux: Depends on DNS caching service:

For systemd-resolved:

sudo systemd-resolve --flush-caches

For nscd:

sudo /etc/init.d/nscd restart

Configure DNS Servers Manually

Switch to reliable public DNS servers to bypass problematic DNS configuration.

Public DNS options:

Google Public DNS:

Cloudflare DNS:

OpenDNS:

Windows:

  1. Network Connections > Right-click adapter > Properties
  2. Select "Internet Protocol Version 4 (TCP/IPv4)" > Properties
  3. Select "Use the following DNS server addresses"
  4. Enter preferred DNS (8.8.8.8) and alternate DNS (8.8.4.4)
  5. Click OK

macOS:

  1. System Preferences > Network > Advanced > DNS
  2. Click "+" to add DNS servers
  3. Add 8.8.8.8 and 8.8.4.4
  4. Click OK and Apply

Linux:

For NetworkManager:

sudo nmcli connection modify "Connection Name" ipv4.dns "8.8.8.8 8.8.4.4"
sudo nmcli connection up "Connection Name"

Or edit /etc/resolv.conf (may be overwritten):

sudo nano /etc/resolv.conf

Add:

nameserver 8.8.8.8
nameserver 8.8.4.4

After changing DNS, test again:

nslookup google.com

Step 7: Check for IP Address Conflicts

IP address conflicts occur when multiple devices on the network use the same IP address, causing connectivity failures for both devices.

Symptoms of IP Conflicts

Detect IP Conflicts

Windows automatically detects conflicts:

Check Windows Event Viewer:

  1. Open Event Viewer (eventvwr.msc)
  2. Navigate to Windows Logs > System
  3. Filter for "Tcpip" source and Event ID 4198 or 4199

Manual detection (all platforms):

If you suspect a conflict:

  1. Note your IP address and MAC address:

Windows:

ipconfig /all

macOS/Linux:

ip addr show
ifconfig
  1. Scan network for duplicate IPs:

Use arp command to check MAC addresses:

arp -a | grep 192.168.1.100

(Replace with your IP)

If multiple MAC addresses appear for the same IP, you have a conflict.

Resolve IP Conflicts

For DHCP-assigned addresses:

  1. Release and renew IP address:

Windows:

ipconfig /release
ipconfig /renew

macOS:

sudo ipconfig set en0 DHCP

Linux:

sudo dhclient -r
sudo dhclient
  1. Restart network adapter:

Windows:

netsh interface set interface "Ethernet" disable
netsh interface set interface "Ethernet" enable

macOS:

sudo ifconfig en0 down
sudo ifconfig en0 up

For static IP addresses:

  1. Change to a different unused IP address

    • Choose an IP outside the DHCP range
    • Verify the new IP isn't in use: ping <new-ip>

  2. Reserve IP in DHCP server

    • Access router configuration
    • Create DHCP reservation binding MAC address to specific IP
    • Prevents DHCP from assigning that IP to other devices

Prevent Future Conflicts

Best practices:

  1. Use DHCP reservations for devices needing static IPs

    • Configure in router DHCP settings
    • Binds specific IP to device MAC address
    • Prevents DHCP from assigning to other devices

  2. Separate static IP range from DHCP pool

    • Example: DHCP pool 192.168.1.100-200, static IPs use 192.168.1.2-99
    • Prevents overlap between static and dynamic assignments

  3. Document static IP assignments

    • Maintain list of devices with static IPs
    • Note IP address, MAC address, and device name

Step 8: Review Firewall Configuration

Firewalls can block legitimate IPv4 traffic, causing connectivity failures. Check firewall rules across different platforms.

Windows Firewall

Check firewall status:

netsh advfirewall show allprofiles

Temporarily disable to test (for troubleshooting only):

netsh advfirewall set allprofiles state off

If disabling firewall fixes connectivity:

View blocking rules:

  1. Open Windows Defender Firewall with Advanced Security
  2. Click "Monitoring" > "Firewall"
  3. Review dropped packets and blocked connections

Create allow rule:

  1. Inbound Rules > New Rule
  2. Select rule type (Port, Program, etc.)
  3. Configure action to "Allow the connection"
  4. Apply to all profiles
  5. Name and save the rule

macOS Firewall

Check firewall status:

sudo /usr/libexec/ApplicationFirewall/socketfilterfw --getglobalstate

Temporarily disable to test:

  1. System Preferences > Security & Privacy > Firewall
  2. Click lock and authenticate
  3. Click "Turn Off Firewall"

Configure firewall rules:

  1. Firewall Options
  2. Add applications to allow list
  3. Enable "Automatically allow built-in software to receive incoming connections"

Linux Firewall (iptables)

Check iptables rules:

sudo iptables -L -v -n

Check for blocking rules:

sudo iptables -L INPUT -v -n
sudo iptables -L OUTPUT -v -n

Temporarily disable iptables (Ubuntu/Debian):

sudo iptables -F

Temporarily disable firewalld (RHEL/CentOS/Fedora):

sudo systemctl stop firewalld

Allow specific traffic:

Allow HTTP (port 80):

sudo iptables -A INPUT -p tcp --dport 80 -j ACCEPT

Allow HTTPS (port 443):

sudo iptables -A INPUT -p tcp --dport 443 -j ACCEPT

Save iptables rules:

Ubuntu/Debian:

sudo netfilter-persistent save

RHEL/CentOS:

sudo service iptables save

Third-Party Firewall/Antivirus

Many security suites include firewalls that may interfere with connectivity:

Common issues:

Troubleshooting steps:

  1. Check security software firewall settings
  2. Temporarily disable to test (for troubleshooting only)
  3. Review logs for blocked connections
  4. Create exceptions for necessary applications
  5. Update to latest version (fixes bugs)

Step 9: Reset Network Stack

If basic troubleshooting hasn't resolved the issue, resetting the network stack clears corrupted configurations and restores default settings.

Windows: Reset Network Stack

Complete network reset:

netsh winsock reset
netsh int ip reset
ipconfig /release
ipconfig /renew
ipconfig /flushdns

Reset specific protocols:

netsh int ipv4 reset
netsh int tcp reset

Restart your computer after running these commands.

Alternative: Windows Settings reset (Windows 10/11):

  1. Settings > Network & Internet > Status
  2. Click "Network reset"
  3. Click "Reset now"
  4. Restart when prompted

macOS: Reset Network Settings

Remove network configuration files:

  1. Backup current settings (optional):
sudo cp /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist ~/backup-NetworkInterfaces.plist
sudo cp /Library/Preferences/SystemConfiguration/preferences.plist ~/backup-preferences.plist
  1. Delete network configuration:
sudo rm /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist
sudo rm /Library/Preferences/SystemConfiguration/preferences.plist

  1. Restart Mac

  2. Reconfigure network connections in System Preferences > Network

Renew DHCP and flush DNS:

sudo dscacheutil -flushcache
sudo killall -HUP mDNSResponder

Linux: Reset Network Configuration

Method 1: Restart NetworkManager:

sudo systemctl restart NetworkManager

Method 2: Reset interface:

sudo ip addr flush dev eth0
sudo systemctl restart networking

Method 3: Remove and reconfigure connection:

sudo nmcli connection delete "Connection Name"
sudo nmcli connection add type ethernet ifname eth0 con-name "Connection Name"

Flush routing table:

sudo ip route flush table main

Step 10: Update Network Drivers

Outdated, corrupted, or incompatible network drivers frequently cause IPv4 connectivity issues.

Windows: Update Network Drivers

Method 1: Device Manager (automatic):

  1. Open Device Manager (devmgmt.msc)
  2. Expand "Network adapters"
  3. Right-click your network adapter
  4. Select "Update driver"
  5. Choose "Search automatically for updated driver software"
  6. Restart if prompted

Method 2: Manufacturer website (recommended):

  1. Identify your network adapter model:
wmic nic get name, manufacturer
  1. Visit manufacturer website (Intel, Realtek, Broadcom, etc.)
  2. Download latest driver for your model and Windows version
  3. Install driver and restart

Method 3: Windows Update:

  1. Settings > Update & Security > Windows Update
  2. Click "Check for updates"
  3. Install any driver updates
  4. Restart

Uninstall and reinstall driver (if problematic):

  1. Device Manager > Network adapters
  2. Right-click adapter > Uninstall device
  3. Check "Delete the driver software for this device"
  4. Restart (Windows will reinstall driver)

macOS: Update Network Drivers

macOS drivers are included in system updates:

  1. System Preferences > Software Update
  2. Install any available updates
  3. Restart if required

For third-party adapters:

Linux: Update Network Drivers

Update system packages:

Ubuntu/Debian:

sudo apt update
sudo apt upgrade

Fedora:

sudo dnf update

Arch:

sudo pacman -Syu

Check for hardware-specific drivers:

Ubuntu:

sudo ubuntu-drivers autoinstall

Reload network driver module:

Identify module:

lspci -k | grep -A 3 -i network

Reload module (example for e1000e driver):

sudo modprobe -r e1000e
sudo modprobe e1000e

Step 11: Advanced Diagnostic Tools

Use these advanced tools for deeper troubleshooting when standard methods don't resolve the issue.

[Traceroute](traceroute-ipv6): Identify Connection Path

Traceroute shows the path packets take to reach a destination and where failures occur.

Windows:

tracert google.com

macOS/Linux:

traceroute google.com

Interpreting results:

Example interpretation:

1    1 ms    1 ms    1 ms  192.168.1.1         # Your router (success)
2    10 ms   10 ms   10 ms  10.0.0.1            # ISP gateway (success)
3    *       *       *      Request timed out.  # Problem at this hop

Problem is beyond your network, likely ISP-side.

Pathping: Combined Ping and Traceroute (Windows)

pathping google.com

Provides detailed statistics on packet loss at each hop, useful for identifying intermittent issues.

Netstat: View Active Connections

Windows/Linux/macOS:

netstat -an

Show listening ports:

netstat -an | grep LISTEN

Show routing table:

netstat -rn

ARP Table: View MAC Address Mappings

Display ARP cache:

Windows:

arp -a

macOS/Linux:

arp -n

Clear ARP cache:

Windows:

arp -d

Linux:

sudo ip -s -s neigh flush all

Network Connectivity Test (Windows)

Test connectivity to specific service:

Test-NetConnection google.com -Port 80

Test TCP connection:

Test-NetConnection -ComputerName google.com -Port 443 -InformationLevel Detailed

Troubleshooting Flowchart

┌─────────────────────────────────┐
│ Test at test-ipv6.run           │
│ Does IPv4 work?                 │
└─────────────┬───────────────────┘
              │
         No   │   Yes
    ┌─────────┴────────┐
    │                  │
    ▼                  ▼
┌────────────────┐  ┌──────────────────┐
│ Check physical │  │ Issue is likely  │
│ connections    │  │ application or   │
└───┬────────────┘  │ site-specific    │
    │               └──────────────────┘
    │ OK         Problem
    │    ┌──────────┘
    │    │
    ▼    ▼
┌──────────────┐  ┌────────────────────┐
│ Restart      │  │ Do you have valid  │
│ modem/router │  │ IPv4 address?      │
└──────────────┘  └───┬────────────────┘
                      │
                      │ No (APIPA)    Yes
                 ┌────┴─────┐          │
                 │          │          │
                 ▼          │          ▼
          ┌──────────────┐ │  ┌────────────────┐
          │ Troubleshoot │ │  │ Can you ping   │
          │ DHCP issues  │ │  │ default gateway?│
          └──────────────┘ │  └───┬────────────┘
                 │         │      │
                 └─────────┘      │ No      Yes
                           ┌──────┘          │
                           │                 │
                           ▼                 ▼
                    ┌──────────────┐  ┌─────────────┐
                    │ Check gateway│  │ Can you     │
                    │ connectivity │  │ resolve DNS?│
                    │ and routing  │  └───┬─────────┘
                    └──────────────┘      │
                           │               │ No    Yes
                           │          ┌────┴───┐   │
                           │          │        │   │
                           ▼          ▼        │   ▼
                    ┌──────────────┐ ┌────┐   │  ┌────────────┐
                    │ Check for IP │ │DNS │   │  │ Check      │
                    │ conflicts    │ │fix │   │  │ firewall   │
                    └──────────────┘ └────┘   │  │ rules      │
                           │          │       │  └────────────┘
                           └──────────┘       │         │
                                    │         │         │
                                    └─────────┴─────────┘
                                             │
                                             ▼
                                    ┌────────────────────┐
                                    │ Reset network      │
                                    │ stack & update     │
                                    │ drivers            │
                                    └────────────────────┘

Common Error Messages and Solutions

"IPv4 No Internet Access" (Windows)

Cause: Device has IPv4 configured but cannot reach the internet.

Solutions:

  1. Restart router and modem
  2. Run network troubleshooter: Settings > Network & Internet > Status > Network troubleshooter
  3. Reset network stack: netsh winsock reset and netsh int ip reset
  4. Release and renew IP: ipconfig /release then ipconfig /renew
  5. Update network drivers
  6. Check router internet connection status

"IPv4 No Network Access"

Cause: Cannot communicate even on local network.

Solutions:

  1. Verify network cable is connected properly
  2. Check network adapter is enabled
  3. Disable and re-enable network adapter
  4. Verify router is powered on
  5. Check for IP address conflict
  6. Reset network adapter settings

"APIPA Address Assigned (169.254.x.x)"

Cause: Cannot obtain IP address from DHCP server.

Solutions:

  1. Check network cable connection
  2. Verify router DHCP server is enabled
  3. Restart router
  4. Release and renew IP address
  5. Check DHCP IP pool isn't exhausted
  6. Connect to router during DHCP negotiation
  7. Configure static IP temporarily

"Default Gateway Not Available" (Windows)

Cause: Cannot communicate with router.

Solutions:

  1. Run Windows network troubleshooter (may automatically reset adapter)
  2. Verify default gateway IP is correct: ipconfig
  3. Ping gateway to test reachability
  4. Update network adapter driver
  5. Disable and re-enable network adapter
  6. Reset network stack
  7. Check router is functioning properly

"DNS Server Not Responding"

Cause: Cannot reach configured DNS servers.

Solutions:

  1. Flush DNS cache: ipconfig /flushdns (Windows) or sudo dscacheutil -flushcache (macOS)
  2. Change to public DNS servers (8.8.8.8, 1.1.1.1)
  3. Restart router
  4. Check firewall isn't blocking port 53
  5. Verify internet connectivity with ping 8.8.8.8
  6. Disable VPN temporarily to test

"IP Address Conflict Detected" (Windows)

Cause: Another device is using the same IP address.

Solutions:

  1. Release and renew IP: ipconfig /release then ipconfig /renew
  2. Restart network adapter
  3. If using static IP, choose different IP address
  4. Check for rogue DHCP servers on network
  5. Create DHCP reservation for your device
  6. Restart router to clear DHCP leases

Prevention and Best Practices

Maintain Network Health

Regular maintenance:

  1. Restart network equipment monthly

    • Power cycle modem and router
    • Clears memory and refreshes connections
    • Resolves many intermittent issues

  2. Keep firmware and drivers updated

    • Router firmware updates fix bugs and security issues
    • Network driver updates improve compatibility
    • Operating system updates include network stack improvements

  3. Monitor DHCP scope utilization

    • Ensure sufficient IP addresses available
    • Remove old/unused DHCP leases
    • Expand DHCP range if needed

  4. Document network configuration

    • Record static IP assignments
    • Note custom DNS server settings
    • Keep list of port forwards and firewall rules

Use Reliable DNS Servers

Recommended DNS providers:

For speed: Cloudflare DNS (1.1.1.1, 1.0.0.1) For filtering: OpenDNS (208.67.222.222, 208.67.220.220) For reliability: Google DNS (8.8.8.8, 8.8.4.4)

Configure at router level for network-wide consistency.

Implement Network Segmentation

For advanced users:

Monitor Network Performance

Test connectivity regularly:

Use monitoring tools:

When to Contact Your ISP

Some IPv4 connectivity issues require ISP intervention. Contact your ISP if:

  1. Modem cannot obtain IP address from ISP

    • Modem WAN interface shows no IP or 169.254.x.x
    • Modem connection status shows disconnected
    • All troubleshooting steps failed

  2. Frequent connection drops

    • Modem frequently loses sync
    • Connection drops multiple times daily
    • Signal quality issues

  3. Cannot reach ISP gateway

    • Traceroute fails immediately after your router
    • Cannot ping ISP's first-hop gateway
    • ISP-side routing problems

  4. Service outage in your area

    • Check ISP status page or social media
    • Call to confirm outages
    • Ask for estimated restoration time

Information to provide ISP support:

Testing Your IPv4 Configuration

After troubleshooting, verify IPv4 connectivity is fully restored:

Comprehensive Testing

  1. Visit test-ipv6.run

    • Confirms IPv4 connectivity working
    • Tests dual-stack behavior
    • Measures latency
    • Provides readiness score

  2. Verify IP configuration

# Windows
ipconfig /all

# macOS/Linux
ip addr show

Ensure valid IP address, gateway, and DNS servers.

  1. Test gateway connectivity
ping <your-gateway-ip>
  1. Test external connectivity
ping 8.8.8.8
  1. Test DNS resolution
nslookup google.com
  1. Test web browsing
  1. Test specific services

Conclusion

Troubleshooting IPv4 connectivity requires a systematic approach, starting with verification at test-ipv6.run and working through physical connections, IP configuration, DHCP, gateway connectivity, DNS, IP conflicts, and firewall rules. Most IPv4 connectivity issues stem from DHCP failures, gateway problems, or DNS misconfigurations, which are straightforward to resolve with the proper diagnostic steps.

By following this guide step-by-step and using the platform-specific commands provided, you can diagnose and resolve the vast majority of IPv4 connectivity problems. For persistent issues that survive all troubleshooting attempts, the problem likely lies beyond your network with your ISP or upstream providers.

Remember: Always test your connectivity at test-ipv6.run after each troubleshooting step to verify whether the issue is resolved. This immediate feedback helps you identify which specific change fixed the problem and confirms your network is functioning properly.

Regular maintenance, keeping firmware and drivers updated, and using reliable DNS servers will help prevent many IPv4 connectivity issues before they occur. When problems do arise, methodical troubleshooting combined with the diagnostic tools outlined in this guide will help you quickly restore connectivity.