Distinct consumer questions
Home networking troubleshooting
Browse home networking by the symptom the customer actually sees. Each record has its own observation, isolation test, correction, verification and stop condition; manufacturer names are not swapped into generic copy.
Browse by platform
623 complete records in this directory2.4 GHz Wi-Fi behaves incorrectly or produces the wrong result
A wrong result requires checking inputs, mode, calibration and output separately; a working control path can still be configured for the wrong state. This record isolates 2.4 GHz Wi-Fi through radio coverage versus channel congestion, security compatibility and interference.
Open record Home networking · 2.4 GHz2.4 GHz Wi-Fi fails only on one device, band, room or service
When a network feature works elsewhere, isolate the client, radio band, location or service path before touching router-wide settings. This record isolates 2.4 GHz Wi-Fi through radio coverage versus channel congestion, security compatibility and interference.
Open record Home networking · 2.4 GHz2.4 GHz Wi-Fi is not working
A complete failure should be separated into power or eligibility, the external path, and the component itself before any reset. This record isolates 2.4 GHz Wi-Fi through radio coverage versus channel congestion, security compatibility and interference.
Open record Home networking · 2.4 GHz2.4 GHz Wi-Fi is unusually slow or delayed
A delay can come from capacity, weak signal, background work, protection or a service wait; measuring the exact stage prevents the wrong repair. This record isolates 2.4 GHz Wi-Fi through radio coverage versus channel congestion, security compatibility and interference.
Open record Home networking · 2.4 GHz2.4 GHz Wi-Fi keeps disconnecting or working intermittently
Intermittent behavior is diagnosed by the trigger—movement, heat, load, sleep, distance or time—not by repeating broad resets. This record isolates 2.4 GHz Wi-Fi through radio coverage versus channel congestion, security compatibility and interference.
Open record Home networking · 2.4 GHz2.4 GHz Wi-Fi stopped working after an update, outage or hardware change
A failure immediately after a known change should be checked for new defaults, stale pairing, power sequencing or compatibility before factory recovery. This record isolates 2.4 GHz Wi-Fi through radio coverage versus channel congestion, security compatibility and interference.
Open record Home networking · 5 GHz5 GHz Wi-Fi behaves incorrectly or produces the wrong result
A wrong result requires checking inputs, mode, calibration and output separately; a working control path can still be configured for the wrong state. This record isolates 5 GHz Wi-Fi through range/walls versus DFS channel support, width and client capability.
Open record Home networking · 5 GHz5 GHz Wi-Fi fails only on one device, band, room or service
When a network feature works elsewhere, isolate the client, radio band, location or service path before touching router-wide settings. This record isolates 5 GHz Wi-Fi through range/walls versus DFS channel support, width and client capability.
Open record Home networking · 5 GHz5 GHz Wi-Fi is not working
A complete failure should be separated into power or eligibility, the external path, and the component itself before any reset. This record isolates 5 GHz Wi-Fi through range/walls versus DFS channel support, width and client capability.
Open record Home networking · 5 GHz5 GHz Wi-Fi is unusually slow or delayed
A delay can come from capacity, weak signal, background work, protection or a service wait; measuring the exact stage prevents the wrong repair. This record isolates 5 GHz Wi-Fi through range/walls versus DFS channel support, width and client capability.
Open record Home networking · 5 GHz5 GHz Wi-Fi keeps disconnecting or working intermittently
Intermittent behavior is diagnosed by the trigger—movement, heat, load, sleep, distance or time—not by repeating broad resets. This record isolates 5 GHz Wi-Fi through range/walls versus DFS channel support, width and client capability.
Open record Home networking · 5 GHz5 GHz Wi-Fi stopped working after an update, outage or hardware change
A failure immediately after a known change should be checked for new defaults, stale pairing, power sequencing or compatibility before factory recovery. This record isolates 5 GHz Wi-Fi through range/walls versus DFS channel support, width and client capability.
Open record Home networking · 6 GHz6 GHz Wi-Fi behaves incorrectly or produces the wrong result
A wrong result requires checking inputs, mode, calibration and output separately; a working control path can still be configured for the wrong state. This record isolates 6 GHz Wi-Fi through client/radio eligibility versus WPA3, band visibility and range.
Open record Home networking · 6 GHz6 GHz Wi-Fi fails only on one device, band, room or service
When a network feature works elsewhere, isolate the client, radio band, location or service path before touching router-wide settings. This record isolates 6 GHz Wi-Fi through client/radio eligibility versus WPA3, band visibility and range.
Open record Home networking · 6 GHz6 GHz Wi-Fi is not working
A complete failure should be separated into power or eligibility, the external path, and the component itself before any reset. This record isolates 6 GHz Wi-Fi through client/radio eligibility versus WPA3, band visibility and range.
Open record Home networking · 6 GHz6 GHz Wi-Fi is unusually slow or delayed
A delay can come from capacity, weak signal, background work, protection or a service wait; measuring the exact stage prevents the wrong repair. This record isolates 6 GHz Wi-Fi through client/radio eligibility versus WPA3, band visibility and range.
Open record Home networking · 6 GHz6 GHz Wi-Fi keeps disconnecting or working intermittently
Intermittent behavior is diagnosed by the trigger—movement, heat, load, sleep, distance or time—not by repeating broad resets. This record isolates 6 GHz Wi-Fi through client/radio eligibility versus WPA3, band visibility and range.
Open record Home networking · 6 GHz6 GHz Wi-Fi stopped working after an update, outage or hardware change
A failure immediately after a known change should be checked for new defaults, stale pairing, power sequencing or compatibility before factory recovery. This record isolates 6 GHz Wi-Fi through client/radio eligibility versus WPA3, band visibility and range.
Open record Home networking · carrier NATCarrier-grade NAT and public inbound access behaves incorrectly or produces the wrong result
A wrong result requires checking inputs, mode, calibration and output separately; a working control path can still be configured for the wrong state. This record isolates carrier-grade NAT and public inbound access through router forwarding versus provider CGNAT, IPv6 and service listening state.
Open record Home networking · carrier NATCarrier-grade NAT and public inbound access fails only on one device, band, room or service
When a network feature works elsewhere, isolate the client, radio band, location or service path before touching router-wide settings. This record isolates carrier-grade NAT and public inbound access through router forwarding versus provider CGNAT, IPv6 and service listening state.
Open record Home networking · carrier NATCarrier-grade NAT and public inbound access is not working
A complete failure should be separated into power or eligibility, the external path, and the component itself before any reset. This record isolates carrier-grade NAT and public inbound access through router forwarding versus provider CGNAT, IPv6 and service listening state.
Open record Home networking · carrier NATCarrier-grade NAT and public inbound access is unusually slow or delayed
A delay can come from capacity, weak signal, background work, protection or a service wait; measuring the exact stage prevents the wrong repair. This record isolates carrier-grade NAT and public inbound access through router forwarding versus provider CGNAT, IPv6 and service listening state.
Open record Home networking · carrier NATCarrier-grade NAT and public inbound access keeps disconnecting or working intermittently
Intermittent behavior is diagnosed by the trigger—movement, heat, load, sleep, distance or time—not by repeating broad resets. This record isolates carrier-grade NAT and public inbound access through router forwarding versus provider CGNAT, IPv6 and service listening state.
Open record Home networking · carrier NATCarrier-grade NAT and public inbound access stopped working after an update, outage or hardware change
A failure immediately after a known change should be checked for new defaults, stale pairing, power sequencing or compatibility before factory recovery. This record isolates carrier-grade NAT and public inbound access through router forwarding versus provider CGNAT, IPv6 and service listening state.
Open record Home networking · roamingDevices stay connected to a far-away mesh node
Client devices decide when to roam, so a phone may cling to a usable distant node. Excessively close mesh points, transmit power and stale client state can worsen it.
Open record Home networking · migrationDevices will not connect after replacing the router with the same Wi-Fi name
Reusing an SSID/password can reconnect many devices, but changed security, band steering, DHCP or cached network parameters can block others.
Open record Home networking · NATDouble NAT and router chaining behaves incorrectly or produces the wrong result
A wrong result requires checking inputs, mode, calibration and output separately; a working control path can still be configured for the wrong state. This record isolates double NAT and router chaining through gateway router mode versus downstream router, mesh and modem bridge capability.
Open record Home networking · NATDouble NAT and router chaining fails only on one device, band, room or service
When a network feature works elsewhere, isolate the client, radio band, location or service path before touching router-wide settings. This record isolates double NAT and router chaining through gateway router mode versus downstream router, mesh and modem bridge capability.
Open record Home networking · NATDouble NAT and router chaining is not working
A complete failure should be separated into power or eligibility, the external path, and the component itself before any reset. This record isolates double NAT and router chaining through gateway router mode versus downstream router, mesh and modem bridge capability.
Open record Home networking · NATDouble NAT and router chaining is unusually slow or delayed
A delay can come from capacity, weak signal, background work, protection or a service wait; measuring the exact stage prevents the wrong repair. This record isolates double NAT and router chaining through gateway router mode versus downstream router, mesh and modem bridge capability.
Open record Home networking · NATDouble NAT and router chaining keeps disconnecting or working intermittently
Intermittent behavior is diagnosed by the trigger—movement, heat, load, sleep, distance or time—not by repeating broad resets. This record isolates double NAT and router chaining through gateway router mode versus downstream router, mesh and modem bridge capability.
Open record Home networking · NATDouble NAT and router chaining stopped working after an update, outage or hardware change
A failure immediately after a known change should be checked for new defaults, stale pairing, power sequencing or compatibility before factory recovery. This record isolates double NAT and router chaining through gateway router mode versus downstream router, mesh and modem bridge capability.
Open record Home networking · EthernetEthernet is connected but there is no internet
A link light shows electrical connection, not a valid IP route. Compare cable/port, DHCP address, router LAN status and another wired device.
Open record Home networking · switchingEthernet switching loop behaves incorrectly or produces the wrong result
A wrong result requires checking inputs, mode, calibration and output separately; a working control path can still be configured for the wrong state. This record isolates Ethernet switching loop through one cable/path versus unmanaged switch topology and spanning-tree support.
Open record Home networking · switchingEthernet switching loop fails only on one device, band, room or service
When a network feature works elsewhere, isolate the client, radio band, location or service path before touching router-wide settings. This record isolates Ethernet switching loop through one cable/path versus unmanaged switch topology and spanning-tree support.
Open record Home networking · switchingEthernet switching loop is not working
A complete failure should be separated into power or eligibility, the external path, and the component itself before any reset. This record isolates Ethernet switching loop through one cable/path versus unmanaged switch topology and spanning-tree support.
Open record Home networking · switchingEthernet switching loop is unusually slow or delayed
A delay can come from capacity, weak signal, background work, protection or a service wait; measuring the exact stage prevents the wrong repair. This record isolates Ethernet switching loop through one cable/path versus unmanaged switch topology and spanning-tree support.
Open record Home networking · switchingEthernet switching loop keeps disconnecting or working intermittently
Intermittent behavior is diagnosed by the trigger—movement, heat, load, sleep, distance or time—not by repeating broad resets. This record isolates Ethernet switching loop through one cable/path versus unmanaged switch topology and spanning-tree support.
Open record Home networking · switchingEthernet switching loop stopped working after an update, outage or hardware change
A failure immediately after a known change should be checked for new defaults, stale pairing, power sequencing or compatibility before factory recovery. This record isolates Ethernet switching loop through one cable/path versus unmanaged switch topology and spanning-tree support.
Open record Home networking · EthernetGigabit Ethernet link speed behaves incorrectly or produces the wrong result
A wrong result requires checking inputs, mode, calibration and output separately; a working control path can still be configured for the wrong state. This record isolates gigabit Ethernet link speed through device capability versus cable pairs, wall jack, switch and power saving.
Open record Home networking · EthernetGigabit Ethernet link speed fails only on one device, band, room or service
When a network feature works elsewhere, isolate the client, radio band, location or service path before touching router-wide settings. This record isolates gigabit Ethernet link speed through device capability versus cable pairs, wall jack, switch and power saving.
Open record Home networking · EthernetGigabit Ethernet link speed is not working
A complete failure should be separated into power or eligibility, the external path, and the component itself before any reset. This record isolates gigabit Ethernet link speed through device capability versus cable pairs, wall jack, switch and power saving.
Open record Home networking · EthernetGigabit Ethernet link speed is unusually slow or delayed
A delay can come from capacity, weak signal, background work, protection or a service wait; measuring the exact stage prevents the wrong repair. This record isolates gigabit Ethernet link speed through device capability versus cable pairs, wall jack, switch and power saving.
Open record Home networking · EthernetGigabit Ethernet link speed keeps disconnecting or working intermittently
Intermittent behavior is diagnosed by the trigger—movement, heat, load, sleep, distance or time—not by repeating broad resets. This record isolates gigabit Ethernet link speed through device capability versus cable pairs, wall jack, switch and power saving.
Open record Home networking · EthernetGigabit Ethernet link speed stopped working after an update, outage or hardware change
A failure immediately after a known change should be checked for new defaults, stale pairing, power sequencing or compatibility before factory recovery. This record isolates gigabit Ethernet link speed through device capability versus cable pairs, wall jack, switch and power saving.
Open record Home networking · guest isolationGuest Wi-Fi cannot see the printer, TV or speakers
Guest networks usually block local-device discovery by design. Internet may work while printers and casting remain isolated.
Open record Home networking · guest Wi-FiGuest-network isolation behaves incorrectly or produces the wrong result
A wrong result requires checking inputs, mode, calibration and output separately; a working control path can still be configured for the wrong state. This record isolates guest-network isolation through internet access versus local discovery, casting and printer sharing.
Open record Home networking · guest Wi-FiGuest-network isolation fails only on one device, band, room or service
When a network feature works elsewhere, isolate the client, radio band, location or service path before touching router-wide settings. This record isolates guest-network isolation through internet access versus local discovery, casting and printer sharing.
Open record Home networking · guest Wi-FiGuest-network isolation is not working
A complete failure should be separated into power or eligibility, the external path, and the component itself before any reset. This record isolates guest-network isolation through internet access versus local discovery, casting and printer sharing.
Open record Home networking · guest Wi-FiGuest-network isolation is unusually slow or delayed
A delay can come from capacity, weak signal, background work, protection or a service wait; measuring the exact stage prevents the wrong repair. This record isolates guest-network isolation through internet access versus local discovery, casting and printer sharing.
Open record Home networking · guest Wi-FiGuest-network isolation keeps disconnecting or working intermittently
Intermittent behavior is diagnosed by the trigger—movement, heat, load, sleep, distance or time—not by repeating broad resets. This record isolates guest-network isolation through internet access versus local discovery, casting and printer sharing.
Open record Home networking · guest Wi-FiGuest-network isolation stopped working after an update, outage or hardware change
A failure immediately after a known change should be checked for new defaults, stale pairing, power sequencing or compatibility before factory recovery. This record isolates guest-network isolation through internet access versus local discovery, casting and printer sharing.
Open record Home networking · DNSHome-network DNS resolution behaves incorrectly or produces the wrong result
A wrong result requires checking inputs, mode, calibration and output separately; a working control path can still be configured for the wrong state. This record isolates home-network DNS resolution through site/provider outage versus resolver, filter, VPN and cache.
Open record Home networking · DNSHome-network DNS resolution fails only on one device, band, room or service
When a network feature works elsewhere, isolate the client, radio band, location or service path before touching router-wide settings. This record isolates home-network DNS resolution through site/provider outage versus resolver, filter, VPN and cache.
Open record Home networking · DNSHome-network DNS resolution is not working
A complete failure should be separated into power or eligibility, the external path, and the component itself before any reset. This record isolates home-network DNS resolution through site/provider outage versus resolver, filter, VPN and cache.
Open record Home networking · DNSHome-network DNS resolution is unusually slow or delayed
A delay can come from capacity, weak signal, background work, protection or a service wait; measuring the exact stage prevents the wrong repair. This record isolates home-network DNS resolution through site/provider outage versus resolver, filter, VPN and cache.
Open record Home networking · DNSHome-network DNS resolution keeps disconnecting or working intermittently
Intermittent behavior is diagnosed by the trigger—movement, heat, load, sleep, distance or time—not by repeating broad resets. This record isolates home-network DNS resolution through site/provider outage versus resolver, filter, VPN and cache.
Open record Home networking · DNSHome-network DNS resolution stopped working after an update, outage or hardware change
A failure immediately after a known change should be checked for new defaults, stale pairing, power sequencing or compatibility before factory recovery. This record isolates home-network DNS resolution through site/provider outage versus resolver, filter, VPN and cache.
Open record Home networking · IPv6Home-network IPv6 connectivity behaves incorrectly or produces the wrong result
A wrong result requires checking inputs, mode, calibration and output separately; a working control path can still be configured for the wrong state. This record isolates home-network IPv6 connectivity through provider delegation versus router/client firewall, DNS and tunnel/VPN.
Open record Home networking · IPv6Home-network IPv6 connectivity fails only on one device, band, room or service
When a network feature works elsewhere, isolate the client, radio band, location or service path before touching router-wide settings. This record isolates home-network IPv6 connectivity through provider delegation versus router/client firewall, DNS and tunnel/VPN.
Open recordStructured depth, not empty permutations
Every published record carries a direct answer, scope, ordered fixes, risk notes and sources.
Device and manufacturer hubs share a consistent record system, but each answer carries the relevant controls, fault boundaries, consequences and official support entry point for that platform.
See the publication gate