Troubleshooting
Same Wi-Fi, still not connecting: the network problems that hide in plain sight
Nefarius Apps11 min read
When a phone and a TV are on the same Wi-Fi but not connecting, they are usually on the same Wi-Fi name without being on the same local network — or on the same network with the router stopping its devices from talking to each other. The usual causes are a guest network, client isolation (also called AP isolation), a mesh system or second router handing out a different range of addresses, a separate network for smart-home devices, and a VPN on the phone. Comparing the two devices' IP addresses tells you which kind of problem you have in about a minute.
This is the network half of the checklist for a TV that won't show up in a remote app. Check the iPhone's Local Network permission first: a denied permission empties the device list just as completely, with no error. Everything below assumes it's on.
Why won't a phone and TV on the same Wi-Fi connect?
A phone and a TV on the same Wi-Fi fail to connect because a remote app needs two things from the network, and "same Wi-Fi" guarantees neither. The first is discovery: the TV has to be heard announcing itself, or found by being asked. The second is a direct connection: the phone has to open a connection to the TV's own IP address and keep it open while you press buttons. There's no server in the middle to stand in if the network won't carry traffic between them.
The two halves fail in different ways. Bonjour discovery runs on multicast DNS, sent to the shared address 224.0.0.251, and multicast DNS is link-local by design: routers don't pass it from one network to another. A direct connection is ordinary one-to-one traffic, which a router can pass between networks — or block, if it has been told to keep devices apart. Every cause in this article breaks one half or both.
How do you check that the phone and TV are really on the same network?
Checking that a phone and a TV are on the same network means comparing their IP addresses, not the names of the Wi-Fi they joined. Prerequisites: the TV fully on with the picture up, and the phone on Wi-Fi rather than cellular.
Read the iPhone's address
Settings › Wi-Fi, then the ⓘ beside the connected network. Note three rows: IP Address (for example
192.168.1.34), Subnet Mask, and Router.Read the TV's address
Look in the TV's network settings for a status or information screen, or open your router's app and find the TV in its list of connected devices.
Compare them
With a subnet mask of
255.255.255.0— the usual one at home — the first three numbers have to match.192.168.1.34and192.168.1.87share a network.192.168.1.34and192.168.0.12don't.
If the subnet mask is wider, such as 255.255.252.0, the third number can differ and the devices can still share a network. Some mesh systems and larger routers are set up this way. It mostly matters for LG TVs, for reasons covered in why LG TVs are slower to appear on a network.
| Result | What it means | Where to look |
|---|---|---|
| Addresses on different networks | The phone and the TV were given addresses by different networks | A guest network, a second router or mesh in router mode, or a separate smart-home network |
| Addresses on the same network | They share a network, and something on it is blocking traffic between them | Client isolation, multicast filtering, or a VPN on the phone |
Why do some TVs appear and others don't?
When some TVs on a network appear and others don't, the pattern usually points to the half of the network that's failing, because remote apps don't find every brand the same way. Tivi, a universal TV remote app for iPhone from Nefarius Apps, finds Samsung and Android TV sets over Bonjour — they announce _samsung-remote._tcp and _androidtvremote2._tcp — and finds LG webOS sets by asking each address in the phone's block whether port 3001 is open. That makes the list itself a diagnostic.
| What you see | Likely cause | Section |
|---|---|---|
| Nothing at all, every time, anywhere in the house | Local Network permission denied, or the phone isn't on Wi-Fi | The Local Network permission |
| An LG appears; a Samsung or Android TV on the same network doesn't | Bonjour multicast isn't reaching the phone, while direct connections work | Mesh systems, below |
| Samsung and Android TV appear; an LG doesn't | The LG is outside the phone's block of addresses, or its remote port is closed | Why LG TVs are slower to appear |
| A TV is listed but won't connect, or a saved TV "isn't responding" | Direct connections are blocked, or the TV has moved to a new address | Client isolation, VPNs and changed addresses, below |
Is the phone on a guest network?
A guest network is a separate Wi-Fi network built to give visitors the internet and nothing else, so a phone on it can't reach a TV on the main network — that separation is the guest network's whole purpose. It's the most common reason two devices are on "the Wi-Fi" and can't see each other, because the guest name is often the house name plus a suffix, and phones join whichever known network is strongest.
To confirm, check the network name in Settings › Wi-Fi. To fix it, move the phone to the main network, then tap the guest network's ⓘ and turn off Auto-Join so it doesn't drift back.
Does the router have client isolation turned on?
Client isolation is a router setting that stops devices on the same Wi-Fi from talking to each other while still letting each one reach the internet, and with it on, a phone can't connect to a TV even with matching addresses. Routers call it AP isolation, client isolation, wireless isolation or station isolation. It is usually on in hotels, student halls, offices and other shared networks, and it can be switched on in a home router's settings without anyone remembering.
The giveaway is matching addresses with nothing working: the TV doesn't appear, or a saved TV appears and won't respond. Remote control needs the phone to reach the TV's own ports — 8001 and 8002 on a Samsung, 3001 on an LG, 6466 and 6467 on an Android TV — and isolation blocks exactly that. Find the setting in the router's wireless or advanced settings and turn it off for the network the TV is on. On a network you don't control, such as a hotel's, there's nothing a phone or a TV can do to get around it.
Do 2.4 GHz and 5 GHz networks matter?
The Wi-Fi band rarely matters on its own: on most home routers, the 2.4 GHz and 5 GHz networks are two radios bridged into one local network, so a phone on 5 GHz reaches a TV on 2.4 GHz without trouble. Separate names such as Home and Home-5G usually still mean one network underneath.
The band becomes the cause when the second name is really a separate network, or on routers that don't pass multicast between the two radios, so discovery fails while connections work. To rule both out, put the phone on whichever name the TV uses and scan again.
Is a mesh system, extender or second router splitting the network?
A mesh system, extender or second router splits a home network when it runs as a router of its own instead of a bridge, which is the most common way a house ends up with two networks under one roof. A typical example: a mesh system plugged into the ISP's router, both in router mode, both broadcasting Wi-Fi. A TV on the ISP router's Wi-Fi and a phone on the mesh get addresses from different ranges, and the mesh's Bonjour traffic never reaches the TV.
- Confirm it. The address check shows different networks, and the Router row on the iPhone points to a different address from the one the TV reports.
- Fix it. Put either the mesh or the ISP router in bridge mode, sometimes called access-point mode, so only one device hands out addresses. Or turn off the ISP router's Wi-Fi and move the TV onto the mesh.
- Extenders. An extender that creates its own network instead of repeating the main one does the same thing. Set it to extend the existing network, and give it the same name and password.
Mesh systems can also cause the subtler failure from the table above: one network, one address range, but multicast filtered or thinned out between nodes or between wireless and wired devices. Bonjour-announced TVs then turn up intermittently or not at all, while an LG found by direct connection still appears. Where the mesh app has a setting for multicast or IGMP handling, that's the place to look.
Is the TV wired, or on a separate network for smart-home devices?
A TV plugged in by Ethernet is normally on the same network as the Wi-Fi, because a home router bridges its wired ports and wireless radios into one. The cable only becomes a problem when it runs to a different box from the one the phone's Wi-Fi comes from — the split network from the previous section.
A separate network for smart-home devices is the deliberate version of the same split. Some routers offer an IoT network, and some households put TVs on their own VLAN. That keeps them apart from the remote app too: Bonjour won't cross into another segment unless the router forwards it — often called an mDNS reflector or Bonjour gateway — and the router's firewall has to allow the phone to connect to the TV. LG discovery in Tivi checks only the phone's own block of addresses, so an LG has to share the phone's segment to be found at all.
Is a VPN on the phone in the way?
A VPN on an iPhone usually leaves connections to the local network alone, but some configurations send them into the tunnel, where the TV can't be reached. Apple gives VPN apps a setting, excludeLocalNetworks, that keeps local connections out of the tunnel when a VPN routes all other traffic through it, and on iOS it defaults to on. A VPN blocks the TV when its app turns that exemption off — often as part of a strict "kill switch" or "block LAN traffic" option — or when a work VPN claims the same address range your home network uses.
The test is quick: turn the VPN off in its app or in Settings › VPN, then scan again. If the TV appears, look in the VPN app for a setting that allows local network access while connected, or turn the VPN off while you're using the remote.
Why does a TV that worked yesterday now say it isn't responding?
A saved TV that worked yesterday and doesn't today has usually changed address or isn't fully on. Routers hand out addresses on a lease, and a TV that was off overnight or restarted after an update can come back at a different one. Tivi keeps a TV it has connected to in its saved list along with the address it was found at, and before reconnecting it checks whether the TV answers on its own remote ports there. If nothing answers within a couple of seconds, it shows "Device Offline": the TV "isn't responding. Make sure it's turned on and connected to the same Wi-Fi network, then try again."
Make sure the TV is fully on
A TV in standby has usually left the network, whatever the light on the front says.
Rescan
Stay on the TVs screen and let the scan run — Tivi gives it up to 15 seconds. A TV at a new address is found there and can be connected from the list.
Reserve the TV's address in the router
Routers call it a DHCP reservation, a static lease or an address reservation. A fixed address keeps the saved entry pointing at the right TV, and it stops an LG asking for its pairing PIN again after its address changes.
Common questions
Will restarting the router fix it?
Only if the problem is a stale address lease or a mesh that has stopped passing multicast properly. A restart doesn't change a guest network, client isolation, a second router in router mode, or a VPN on the phone, so run the address check first and restart only if it points nowhere else.
Why won't a remote app work on hotel or dorm Wi-Fi?
Shared networks usually turn on client isolation, so guests can reach the internet but not each other's devices — including a TV in the room. Some hotel TVs are on a separate network entirely. A phone has no way around either, so the TV's own remote is the answer there.
Does iCloud Private Relay block the connection to the TV?
Apple describes iCloud Private Relay as protecting your browsing in Safari, and connecting to a TV on your own network isn't browsing. If you want to rule it out anyway, turn it off under Settings › your name › iCloud › Private Relay and scan again.
Can the phone use cellular data to reach the TV?
No. Cellular connects the phone to the internet, not to your home network, so there's no route to the TV. Where the Wi-Fi is weak, the phone can drop to cellular without making it obvious, so check for the Wi-Fi symbol in the status bar.
The short version
When a phone and a TV are on the same Wi-Fi but not connecting, compare their IP addresses. Different networks point to a guest network, a second router or mesh in router mode, or a separate smart-home network. The same network with nothing working points to client isolation, multicast filtering on a mesh, or a VPN on the phone. A saved TV that has stopped responding has usually moved to a new address, and a rescan finds it.
If the network checks out, the cause is on the phone or the TV — the checklist for a TV that won't show up covers those, and why a phone remote needs Wi-Fi at all covers what the connection is made of. For the groundwork on every brand, start with how to use your iPhone as a TV remote. The rest of the troubleshooting guides and the frequently asked questions cover what comes next.