Connected, No Internet? Stop Guessing, Here's the Real Fix That Actually Works
This blog is a professional networking guide that outlines a step-by-step diagnostic protocol to isolate and resolve "Connected, No Internet" errors across routing, DNS, and firewall layers instead of relying on random router reboots. It provides concrete, real-world solutions for local infrastructure bugs and directly addresses carrier fair-usage traps like data cap exhaustion by outlining clear migration paths to unmetered fiber alternatives.
Geofrey Tuhaise
July 29, 2026
Connected to Wi-Fi but there's no internet? Your phone says "Connected" yet WhatsApp won't send messages, websites won't load, YouTube refuses to play, and every app seems frozen.
When your endpoint reports "Connected, No Internet," it is handing you a massive diagnostic clue. It means Layer 1 (Physical) and Layer 2 (Data Link) connections between your device and the access point are flawless. The radio waves are working, and authentication is complete. The failure is happening further up the stack, either at Layer 3 (Routing), Layer 4 (Firewall/NAT), or Layer 7 (DNS/Application).
This guide eliminates the guesswork. Here is the exact real-world diagnostic protocol used by network engineers to pinpoint the failure and restore connectivity instantly.
The Demarcation Line: Is the Failure Local or External?
Before changing a single configuration line, you must isolate the fault domain. Is the issue inside your building, or is it on the ISP's side of the demarcation point?
[Your Device] ----(Local LAN)----[ Edge Router ] ----(Disconnected WAN Link)----[Public Internet]
Run this 5-second test from a terminal or command prompt: ping 8.8.8.8
If you get replies: Your internet connection is actually alive. Your local network is routing packets to the public web perfectly. Your issue is almost certainly a DNS Failure (see Section 3).
If you get "Request Timed Out" or "Destination Host Unreachable": Packets are leaving your device but are dying at the gateway or failing to cross the WAN link to your service provider.
Here are the causes and the real fix:
1. Upstream Carrier Cap Exhaustion
If you are running a business, a busy household, or a remote office on a home usage fiber internet package, this is the single most common cause of "Connected, No Internet" in Uganda. When fiber internet account hits its monthly volume threshold or exhausts its allocated data cap, the router doesn't shut down. The wireless radios keep broadcasting their SSIDs normally, and your devices will connect with full signal strength. However, at the carrier core network, drops your traffic or shapes your bandwidth down to zero.
Real-world solution
The Quick Fix: Log directly into your MyMTN App or dial
*100*23#to verify your active Wakanet bundle status. If it is depleted, top up immediately to re-authenticate the data session. If you're using any other ISP that's not MTN, contact your ISP's support team.Migrate to Uncapped FTTH (Fiber to the Home): Switch your link to dedicated, unmetered fixed-fiber providers operating in Kampala. Make sure that these services offer truly unlimited bandwidth profiles without hidden data ceilings.
2. DNS Server Failures (Layer 7 Resolution Drops)
If your network can ping public IP addresses (like 1.1.1.1) but typing google.com into a browser results in a "Server Not Found" error, your internet isn't broken, your translation layer is. DNS converts human-readable domain names into IP addresses. If it fails, apps appear completely offline.
Real-wrold solution
Stop relying the default DNS servers assigned automatically by your ISP. They are frequently congested and prone to intermittent drops. Log into your router and hardcode your network to distribute reliable, enterprise-grade public resolvers:
Provider | Primary DNS | Secondary DNS |
Cloudflare |
|
|
|
|
3. Your Router Lost Internet From the ISP
Sometimes the ISP is working perfectly, but your router is no longer authenticated. Common causes include: PPPoE authentication failure, DHCP lease expired, WAN cable unplugged, Incorrect VLAN configuration, Modem synchronization problems.
Real-world Solution
Logon to Winbox and navigate to IP > DHCP Client and check whether the status is "bound" and the <Expires After> column shoud be counting. If the status isn't bound, your mikrotik isn't receiving internet.
Reconnect the WAN interface (the first port on your mikrotik in most settings), double check to see whether the cable isn't fault and it's plugged in well.
Restart your ISP router, this renews everything and provides a fresh start to your ISP router.
Check your ISP account or contact your provider to confirm your subscription is active before troubleshooting the network.
4. Expired Hotspot Session
Hotspot networks authenticate users for a limited time. If the voucher expires, time runs out or data quota is exhausted, the device remains connected to Wi-Fi but loses internet access.
Real-world Solution
Log in again using a valid voucher or renew the account.
You forget the network and connect again. If forget doesn't work, try resetting your network settings in phone Settings ⛮ this will require a password to continue with the reset.
5. Weak Signal Quality
A Wi-Fi icon with full bars does not always mean a quality connection. Interference from: walls, metal objects, neighboring Wi-Fi, microwave ovens can severely affect communication.
Real-world solution
Move closer to the access point.
Switch to a less congested Wi-Fi channel.
Upgrade access point placement.
6. DHCP IP Pool Exhaustion
Every client on your network requires an IP address. If your DHCP pool runs out of available addresses, new users may connect to Wi-Fi but won't receive a valid IP configuration, resulting in "Connected, No Internet."
This is common in busy hotspots such as restaurants, hotels, schools, and public WiFi.
Real-world solution
Increase the DHCP pool size.
Remove inactive DHCP leases.
Ensure your subnet can accommodate your expected number of users.
7. A Router in the Chain Starts Running DHCP
Many hotspot owners extend coverage by chaining indoor routers configured as Access Points. However, after a factory reset or firmware upgrade, one of these routers may revert to Router Mode and automatically enable its DHCP server.
This creates multiple DHCP servers on the same network, causing devices to receive incorrect IP addresses, gateways, or DNS settings, leading to "Connected, No Internet," captive portal issues, or intermittent connectivity.
Real-world solution
Ensure every router in the chain is configured as an Access Point, with DHCP, NAT, and routing disabled. Only your primary router or MikroTik should assign IP addresses.
8. Fiber Routers Converted to Access Points Without Disabling DHCP
Many hotspot owners reuse second-hand routers or ISP-supplied fiber routers from brands such as Huawei, TP-Link, Cudy, Tenda, Ruijie, Cambium, XPON, GPON, Wavelink, and others to extend Wi-Fi coverage.
A common mistake is switching the router to Access Point mode or using it as one without disabling its DHCP server. This introduces multiple DHCP servers on the network, causing IP conflicts and internet connectivity issues.
Real-world solution
Disable the DHCP server.
Disable routing and NAT if applicable.
Connect it through a LAN port unless the manufacturer specifies otherwise.
Hotspot Owners Cheat code:
To prevent most "Connected, No Internet" issues:
Keep only one DHCP server on the network.
Verify all indoor routers remain in Access Point Mode.
Monitor DHCP lease usage.
Confirm your ISP subscription is active.
Recheck router settings after firmware upgrades or factory resets.
Many connectivity problems are caused by configuration mistakes, not faulty equipment. Regular network checks can prevent unnecessary downtime and customer complaints. If you follow all the above steps and and still face the same problem, schedule a site visit with a technician
If you have anything to inquire about, put it in the comments below👇. Thank you and let us grow together.
Find out how XenFi helps ISPs grow
Smart billing, automation and management for hotspot providers and ISPs.