My Wi‑Fi is not working—what do I do?
First establish whether all devices are offline or only one device/room. Check router/ONT power and lights, then test one device close to the main router.
Type your problem in your own words below. Every answer says what to check, what to leave alone, and when it's time to call someone for help.
132 answers found · last checked 17 August 2026
First establish whether all devices are offline or only one device/room. Check router/ONT power and lights, then test one device close to the main router.
A wired test at the main router separates the incoming service from the wireless layer. If wired works but Wi‑Fi does not, focus on coverage, interference or the client.
If other devices work, the broadband and router are probably live; forget and rejoin the network, verify password, update/restart the device and check it is not paused or blocked.
This can be DNS, VPN, filtering, IPv6 or the destination—not necessarily weak Wi‑Fi. Compare another device/browser, disable VPN temporarily and test a known site.
The device has joined the local wireless network but the router may lack a working internet session, DNS may be failing, or access may be paused.
The package speed is delivered to the router; a wireless device’s result also depends on its radio, band, signal, interference, mesh hop and current traffic. Test the gateway or a capable wired device first.
They may use different servers, routes, test durations, browser limits and load. Use the ISP/router test for line-to-router speed and a reputable nearby server for device speed.
Pause large downloads, turn off VPN, use one modern device near the main router, confirm the band, and repeat three times. Also run a gateway or Ethernet test.
A 100 Mbps Ethernet negotiation commonly produces results near 90–95 Mbps. Check for a damaged/two-pair cable, 100 Mbps port, adapter/dock limit or forced speed setting.
Upload can be consumed by cloud backup, cameras, video calls or malware; Wi‑Fi interference can also affect both directions differently. Test wired with background uploads paused.
More household traffic and neighbouring channel use can raise contention; an ISP network issue is also possible. Compare gateway and client tests at matched times.
The broadband upgrade does not upgrade the laptop’s Wi‑Fi radio. An older 802.11n/one-stream client, driver or 2.4 GHz connection may be the limit.
Idle devices use little internet capacity, but active or chatty devices share airtime and bandwidth. Cameras, backups and streams matter more than the raw device count.
The router test measures internet delivery to the gateway; the phone test includes the Wi‑Fi path, phone capability and location.
Throughput and delay are different. Congestion, bufferbloat, weak signal, retries, VPN routing or game-server distance can raise ping without reducing a headline speed result.
Distance plus walls, floors, foil insulation, metal and glazing reduce signal. A centrally placed node or properly positioned mesh unit is usually better than extra broadband speed.
Put it upright, out in the open, elevated and as central as the fibre/cabling allows—away from cupboards, TVs, radiators, metal, fish tanks and large electronics.
It may work, but cupboards absorb and trap the signal, especially if metal or full of electronics. Moving the Wi‑Fi access point into the open usually improves coverage.
Usually not. Package speed improves capacity to the router; a dead spot is a radio coverage problem needing better placement, mesh or Ethernet.
Place it where it still receives a good signal from the upstream node—often midway toward the weak area, not in the dead zone. Keep it open and away from interference.
Yes. Excess nodes can increase co-channel airtime, poor roaming and unstable backhaul. Add only where measurements show a need.
The client ultimately decides when to roam. Steering can encourage a better node/band but cannot force every device immediately. Toggle Wi‑Fi or move briefly to trigger a rescan.
It may create a separate network, double NAT or poor roaming and can reduce performance. Prefer platform-compatible managed nodes or Ethernet access points designed for the network.
Often yes: it removes the wireless backhaul hop and can improve consistency, especially through dense walls or between floors.
Foil-backed insulation, underfloor heating, dense plasterboard and metal can attenuate radio signals. Multiple well-placed wired nodes may be needed.
2.4 GHz reaches farther and supports more legacy/IoT devices but is usually busier and slower; 5 GHz offers higher capacity at shorter range.
Modern mesh systems commonly use one SSID and steer clients between bands. The bands still exist even though only one name is shown.
Keep the phone on the home Wi‑Fi, enable location/Bluetooth permissions, put the device in pairing mode and temporarily use the platform’s 2.4 GHz onboarding method.
Usually no; one SSID enables steering and roaming. Split only for a demonstrated legacy-device need and document the consequences.
It may not support 5/6 GHz, WPA3, the current channel or SSID settings. Confirm 2.4 GHz is enabled, use WPA2-compatible mode temporarily and update the device.
Wi‑Fi generation and encryption are separate. Some legacy clients fail with WPA3/hybrid modes even when 2.4 GHz exists. A temporary WPA2 compatibility test can confirm this.
No. 6 GHz is a short-range Wi‑Fi band used by compatible Wi‑Fi 6E/7 devices; 5G is a cellular technology.
Higher-frequency 5 GHz signals generally attenuate more through distance and obstacles, so the device may fall back to 2.4 GHz or lose the band.
Legacy rates can consume airtime, but disabling them can disconnect old printers/IoT. Change only after inventorying clients and testing.
Some IoT devices and setup apps handle hidden networks poorly. Temporarily broadcasting the SSID may help; hiding an SSID is not meaningful security.
Check whether the main Q box, Mini boxes or all devices are affected. Restart the affected box, verify it joined the intended network, and test Ethernet to isolate Sky’s wireless link.
Minis depend on a stable path to the main Sky Q box as well as internet. Multicast/mesh topology, interference or a weak inter-box link can affect TV while phones appear fine.
Ethernet is often more stable for fixed TV equipment if correctly installed. If Ethernet is used, review Sky wireless/mesh settings to avoid duplicate paths.
Sky says hotspot capability depends on compatible equipment and setup; with a non-Sky router it may not operate the same way. Treat Sky Q distribution separately from the ISP mesh.
Test another streaming service and the puck near the router or over Ethernet. A good gateway test plus poor puck Wi‑Fi indicates local connectivity; failures across services/devices may indicate broadband.
Check whether one speaker or grouped playback fails, update Sonos, verify all units are on the intended LAN, and assess 2.4 GHz congestion/multicast and mesh topology.
The phone and speakers must be able to discover each other on the local network. Guest isolation, VPN, different VLANs/SSIDs or permissions can block discovery.
It depends on the Sonos models and topology. Follow current Sonos system requirements; modern units may use supported bands, while legacy products and SonosNet have different rules.
Sonos recommends 20 MHz width and, when manually selecting, channels 1, 6 or 11. On managed mesh, automatic channel selection may be preferable.
Grouping multiplies synchronized traffic and exposes weak links, interference or topology problems. Identify the first failing room and test smaller groups.
Yes, in some mixed networks it can alter Sonos topology or expose spanning-tree/loop problems. Wiring can also help when designed correctly.
Many older printers support only 2.4 GHz and WPA2. Confirm its exact model, enable compatible 2.4 GHz onboarding and reset only the printer’s network settings.
The printer may have changed IP address, the laptop may be on a guest network/VPN, or the print queue/driver may be stale.
The SSID/password/security or subnet changed. Reconnect the printer to the new network and remove/re-add it on computers if discovery records are stale.
Only if that exact router supports USB print-server functionality; many modern ISP/mesh routers do not. A small print server or always-on computer may be required.
That points to the Windows driver, print queue, firewall or discovery profile rather than broadband. Verify the PC and printer are on the same LAN and test the printer IP.
Doorbell quality depends on signal and upload at the door, not just package speed. Check Ring RSSI, obstruction, power and whether live view/upload traffic is stable.
Use the bands supported by the exact Ring model. 2.4 GHz often reaches farther through walls; 5 GHz may be faster at short range.
Often the device supports only 2.4 GHz or WPA2, the setup phone lacks location/Bluetooth permission, or the SSID/password contains unsupported characters.
Treat unknown-brand IoT as higher risk: update firmware, change default credentials, review privacy terms and isolate it on a guest/IoT network where that still permits needed functions.
Some setup apps require the phone to be on the same local Wi‑Fi, with local-network/location/Bluetooth permissions. Turn off mobile-data switching temporarily during onboarding.
Remote access depends on the vendor cloud, account, DNS/firewall and sometimes inbound connectivity. Check vendor service status before changing router settings.
IoT devices store the old SSID/password and usually need to be migrated or re-paired. Temporarily restoring the previous credentials may reconnect them if safe.
Night-time interference, scheduled access controls, power/lighting changes, upload congestion or marginal signal can be involved. Correlate exact times.
Guest networks commonly isolate clients from the main LAN and sometimes from each other, which can stop discovery/control. Use a designed IoT network if local communication is required.
Discovery may require the same LAN plus multicast/mDNS, Bluetooth and correct phone permissions; guest isolation or VPN can interfere. Thread devices may also need a compatible border router.
Encryption and the route through the employer’s VPN gateway add overhead and may be congested. Compare the same device with VPN on/off; a fast non‑VPN result points away from the ISP.
Calls need low loss, jitter and latency, not just throughput. Test near the router or wired and check other uploads, VPN and Wi‑Fi retries.
That isolates the issue to the wireless client/path: signal, interference, driver, roaming or band—not the internet service itself.
Some platforms offer device priority/QoS, which may help during local congestion but cannot fix weak signal, packet loss or a congested remote VPN.
Residential public IPs may be dynamic; VPNs show the VPN exit IP. A static IP or DDNS is needed only for specific authorised business uses.
One-way audio commonly points to NAT/firewall or blocked RTP media, not Wi‑Fi speed alone. Test the ATA/phone by Ethernet and review SIP/NAT design.
Packet loss, jitter, latency and upstream congestion cause broken voice. Test wired, pause uploads and capture a failing call time.
Check DHCP/IP, DNS, cabling, SIP credentials and whether double NAT, CGNAT or firewall/ALG behaviour changed.
Usually not unless the ONT/router/phone equipment has backup power. Ofcom requires providers to address emergency-call resilience, especially for at-risk customers.
Often, but compatibility depends on tone/ringing, connectors and the VoIP service. Alarms, fax, lifts and telecare need explicit compatibility testing.
Fax tones are sensitive to packet loss, jitter and codec conversion. T.38 support or an alternative digital document service may be required.
Strict NAT can result from double NAT, CGNAT, disabled UPnP or missing port mappings. First identify the WAN IP and number of routers.
CGNAT lets multiple customers share one public IPv4 address. Normal browsing works, but inbound hosting, some games, VPNs and port forwarding may not.
Only after confirming the exact device, protocol and necessity. Prefer UPnP for compatible games or vendor-cloud/VPN solutions; manual forwarding increases exposure.
UPnP improves automatic NAT traversal for consoles but lets trusted LAN devices request mappings. Keep devices secure and avoid it on untrusted networks.
Weak signal, interference, roaming and contention add delay/retries. Compare Ethernet; if wired is good, optimise Wi‑Fi or wire the console.
IPv6 can provide end-to-end addressing where the ISP, router, game and firewall support it, but it does not automatically improve latency and still requires firewalling.
It encourages compatible clients toward a preferred band, usually 5/6 GHz, but the client makes the final association decision.
The mesh can encourage roaming to a better access point, but clients choose when to move. Poor node placement can make steering ineffective.
DFS channels share spectrum with radar. A router detecting radar must leave the channel, which can briefly interrupt or move compatible clients.
No; eero uses automatic channel selection. Radio Analytics can show busyness, but manual channel selection is not currently offered.
RSSI estimates received signal power; SNR compares signal with noise; noise floor reflects background energy. Stronger signal and adequate SNR generally reduce retries, but thresholds are device/use dependent.
Wider channels can raise peak throughput but consume more spectrum and may be less stable in congested areas. 20 MHz is usually safer on busy 2.4 GHz.
Wi‑Fi is shared and half-duplex: devices take turns. High activity or interference leaves less airtime and can increase latency and reduce throughput.
Strong RSSI does not guarantee a clean channel or healthy path. Interference, driver bugs, congestion, backhaul or WAN issues can still drop packets.
Double NAT occurs when two routers both perform routing/NAT. It can affect gaming, inbound access, VPNs and discovery. Use one routing layer where possible.
Only when another required router is doing routing. Bridge mode keeps eero Wi‑Fi but disables several advanced network/security features.
WPA3 improves security, but some legacy clients struggle with WPA3 or mixed modes. Use current firmware and the least-weakened compatible setting.
Newer standards improve efficiency and capability, but each client uses only what it supports; distance, channel, backhaul and internet tier still matter.
Private addresses are used inside the home; the router’s public address represents the connection on the internet. Under CGNAT even the router WAN may be private/shared.
Most residential services use dynamic addresses that can change after lease/session/network events. Use supported DDNS or a paid static IP for a genuine requirement.
DNS translates names into IP addresses. If it fails, apps using cached/direct addresses may work while websites by name fail.
Only as a controlled diagnostic or informed policy choice. It may bypass provider filtering, alter privacy/performance and not fix weak Wi‑Fi.
Dual stack lets devices reach services over either protocol. IPv6 uses a different address format and is normal when supported.
Common causes are CGNAT/double NAT, wrong internal IP, local firewall, wrong protocol/port, or testing from inside without NAT loopback.
Identify it using manufacturer, hostname, MAC and activity; phones may use private/random MAC addresses. Pause—not permanently block—while confirming with household members.
Private/randomised MAC addressing can make the same phone appear with different identifiers, especially per SSID or after privacy-setting changes.
Paused devices can remain associated to Wi‑Fi while internet access is blocked by a profile or manual control. Resume only with authorised account-holder approval.
Guest networks are normally isolated for safety, so local discovery and device-to-device access may be blocked.
Slow Wi‑Fi is more often coverage, interference or traffic. Check unknown devices and security alerts, change credentials if compromise is credible, and update equipment.
Use a guest network where available; it limits access to trusted local devices. Use a strong unique main password.
Check the router label/model and the management app: eero app, HomePass/WorkPass, or CommandIQ/provider-branded Calix app. Do not rely on colour alone.
No—not as one managed mesh. They are separate ecosystems. Mixing may create multiple SSIDs, routing layers and roaming problems.
Where platform access and consent allow, yes—but support should first inspect telemetry and warn of temporary loss of internet, voice and safety-connected devices.
It is a last resort because it removes configuration and can disconnect every device. Use targeted diagnostics, restart and configuration checks first.
Updates can alter channels, security compatibility or client behaviour; they may also fix defects. Correlate timing, version and affected devices before rollback/escalation.
Support tools may show device/network health and, where a subscribed security service lawfully provides it, limited category/security events—not necessarily full page contents. Access must follow privacy, safeguarding and account authority.
ISP telemetry covers the access network and Wi‑Fi connection; the printer’s driver, cloud account and app belong to the device maker. Support can isolate the layer and hand off evidence.
Discovery protocols are normally local-link. Crossing VLANs needs an intentionally configured reflector/gateway and security policy; simple routing may not be enough.
Incorrect multicast handling can cause flooding or failed delivery. Whether snooping helps depends on switch/router topology and querier behaviour.
Older or region-mismatched clients may not support all DFS channels, and radar events can move the network. Check client regulatory domain and driver.
That is a self-assigned link-local IPv4 address, usually meaning DHCP did not provide a lease. Check association, DHCP scope, VLAN and duplicate servers.
A manually assigned address may overlap DHCP, a stale reservation may exist, or two DHCP servers may be active due to a second router.
The client link may be the bottleneck: weak radio, old standard, power saving, interference or driver. Backhaul and fronthaul are separate links.
Large queues fill during upload/download, increasing latency even without packet loss. Test idle versus loaded latency and manage heavy traffic/QoS where supported.
TCP retransmits and adapts, masking some loss; real-time UDP often cannot recover late/lost packets. Measure loss, jitter and path-specific filtering.
Yes. Encapsulation can make packets too large; broken path-MTU discovery may cause stalls. Test under the VPN/provider’s approved MTU guidance.
Some routers do not support NAT loopback, so the public hostname works externally but not internally. Test from mobile data and consider split DNS.
They may work, but performance depends heavily on electrical circuits, noise and consumer-unit layout. Ethernet is more predictable.
Yes. Microwaves and many consumer devices can raise 2.4 GHz interference; radar triggers DFS channel moves on 5 GHz. Correlate time/location and radio metrics.
Bluetooth shares 2.4 GHz spectrum; poor coexistence drivers or a congested environment can hurt some clients. Try 5 GHz, update drivers and compare.
A same-radio wireless relay can reduce available airtime, but the actual impact varies with radios, backhaul quality, channel use and traffic. It is not a fixed 50% rule.
Wi‑Fi calling relies on the mobile operator’s secure tunnel, DNS/NAT and handset provisioning. VPN, firewall, CGNAT or operator outage can affect it.
Start with the boring one: Sonos speakers and your phone must all be on the same home network. If your phone is on the guest network, or on a different Wi-Fi name from the speakers, the app will keep losing them. Next, unplug any plug-in Wi-Fi extenders and see whether the problem stops — extenders are one of the most common reasons Sonos drops. Then restart the router and the speaker that drops most.
Yes — most Sonos systems work well on mesh, but only when the mesh is set up the way Sonos expects: one network name for the whole home, no guest network for the speakers, and every mesh box part of the same single network. The problems we see are almost always a mesh that's quietly running two networks, or a speaker that has latched onto a far-away box and won't let go.
The BT Smart Hub works with Sonos, but two of its habits cause trouble: it can steer devices between its two Wi-Fi bands, and its default channel can sit right on top of the one your speakers use. Giving your Wi-Fi a single name for both bands and picking a quieter channel fixes most BT–Sonos complaints we see.
Yes — eero is one of the friendliest mesh systems for Sonos, because it runs one network name and passes the background chatter Sonos needs. The settings that matter: keep Sonos on your main eero network (never the guest one), and if speakers disappear, try eero's 'Legacy' or compatibility mode for older speakers.
It can — but Deco needs two settings checked before Sonos behaves. First, keep the speakers on the main Deco network, not the guest one. Second, if speakers keep disappearing, look for Deco's 'AP isolation' and any fast-roaming options and turn them off for the speakers — both can break the constant background contact Sonos relies on.
Check three things in this order. First, your phone must be on the same network you want the speaker to join — setup fails silently if the phone is on mobile data or the guest network. Second, the network must be one Sonos supports: home networks are fine, but hotel-style login pages and many extenders are not. Third, restart the speaker and the router, then try setup again with the phone next to the speaker.
Any mesh that keeps one network name, doesn't isolate devices from each other, and lets you turn off aggressive 'roaming' features will run Sonos well. In our case history, eero and most provider-supplied mesh behave best out of the box; TP-Link Deco and others work fine once AP isolation and fast roaming are switched off. What matters far more than the brand is the setup — one network, no guest network for speakers, no extra extender alongside.
No — and this catches a lot of people out. Guest networks deliberately stop devices from seeing each other, so a speaker on the guest network becomes invisible to the Sonos app on your phone. Sonos itself lists guest networks and networks with login pages (like hotel Wi-Fi) as unsupported. Speakers belong on your main home network.