VPN Connected but Wi-Fi Says No Internet: The Green Badge Was Protecting a Network I Had Not Joined

The VPN showed Connected, while Windows insisted the airport Wi-Fi had No Internet. My browser could not open the airline portal, Outlook remained offline, and the presentation I needed for a client call was still in cloud storage. I blamed the crowded lounge network, disconnected and reconnected to Wi-Fi, then chose another VPN server. The green badge returned immediately. The internet did not.

I was at Istanbul Airport with thirty-two minutes before a video call. A client had moved the meeting forward while I was in transit, and the latest presentation was waiting in a shared drive.

The lounge Wi-Fi showed full signal. My laptop had joined the network. The VPN application said the tunnel was active.

Every useful application suggested otherwise.

Teams could not sign in. The shared drive displayed a connection error. Even an ordinary search page refused to load.

I restarted the laptop, joined the Wi-Fi again, and watched the same contradiction return: Wi-Fi connected, VPN connected, no internet.

The mistake was assuming those three labels described the same thing.

They did not.

The VPN connected before the airport let me online

The large VPN provider was one I trusted. It had years of public history, a broad server network, and an automatic-protection feature that activated whenever the laptop joined unfamiliar Wi-Fi.

That feature had always sounded sensible. I wanted the VPN running before any application exchanged data over an airport network.

This time, it started one step too early.

The lounge required passengers to accept its terms through a captive portal. Until that page was completed, the laptop could join the access point but could not reach the wider internet.

The VPN’s kill switch was already blocking traffic outside the tunnel. The tunnel could not reach its server because the airport had not yet authorized the laptop.

The result was a deadlock: the airport wanted me to open its login page, while the VPN refused to let that unprotected page through.

I entered several ordinary web addresses, hoping one would redirect me to the lounge portal.

Nothing appeared.

Then I disconnected the VPN.

The airport’s terms page opened immediately.

That changed the meaning of the warning. “No Internet” did not mean the Wi-Fi radio had failed. It meant I had entered the airport network without completing its final admission step.

Windows checks internet access by sending a few small requests in the background. A captive portal intercepts those requests until the user signs in or accepts the network’s terms.

I entered the access code from my boarding pass, accepted the terms, and confirmed that a normal page loaded.

Only then did I reconnect the VPN.

The green badge appeared.

So did the no-internet warning.

This time, however, a few browser pages opened. Outlook remained offline, Teams stalled during sign-in, and the shared-drive download stopped after 6 MB.

The captive portal had been the first problem. The unstable VPN route was the second.

A different server still had to cross the same airport network

I selected a server in Germany because it showed the lowest load.

The browser stopped responding.

I chose the Netherlands. Outlook downloaded two messages, then returned to “Trying to connect.”

I switched to the United Kingdom. The shared-drive file restarted from zero.

The provider offered plenty of alternatives, but every one of them had to cross the same managed airport network.

That was the detail the server map obscured.

The lounge Wi-Fi was crowded and kept moving my laptop between access points. The VPN could display a successful tunnel while the applications inside it repeatedly lost a usable route.

Travelers describe the same practical frustration on hotel and airport networks: the portal is completed, the VPN says it is connected, but downloads stall or applications keep dropping.

The symptom was common. The important question was not whether the Wi-Fi icon or VPN badge looked correct.

It was whether the connection could carry the work.

I disconnected the VPN and tested the direct route. Teams reached the sign-in screen, but its call-quality check failed. The shared-drive download moved briefly, then froze when the laptop shifted to another lounge access point.

Without the VPN, the internet was available but unreliable. With the established provider, it was protected but still unusable for the meeting.

The client call was nineteen minutes away.

I could continue trying countries and reconnect buttons, but the growing server list was no longer helping me make a useful decision.

I did not need the VPN to report a connection.

I needed the presentation to finish downloading and the call to stay open.

The next connection completed the job

I disconnected the larger provider and opened OnlydogVPN.

Instead of choosing a country, I selected the preset for restricted public Wi-Fi.

Then I reopened the shared drive.

The presentation resumed.

Six megabytes.

Eighteen.

Forty-three.

The laptop shifted to another airport access point. The speed dipped, but the download continued instead of returning to zero.

When it reached 100 percent, I opened the file locally and checked the final slides.

Then I launched Teams.

The sign-in completed. The camera preview appeared. The call-quality warning disappeared.

I joined four minutes early.

During the meeting, the lounge connection weakened twice. The video softened briefly, but the call stayed open. I shared the presentation, answered the client’s questions, and uploaded a revised pricing slide before the meeting ended.

That was the result I had been trying to reach since opening the laptop.

The smaller app combined two things the airport connection needed. Its obfuscation helped it establish a usable route on the managed network, while its HTTP/3-based transport recovered when the laptop moved between access points.

The practical effect was simple: the presentation and call did not restart whenever the Wi-Fi shifted underneath them.

I could not observe the airport’s internal filtering rules or identify the exact rule that disrupted the earlier provider. I could see the outcome: the established app remained green while the download and meeting failed; the smaller app carried both through the same lounge network.

The status badge had stopped being persuasive.

The client speaking through my headphones was better evidence.

“No Internet” was a clue, not the final verdict

After the meeting, I looked again at the Windows taskbar.

For several seconds, the Wi-Fi icon still showed a warning even though Teams, Outlook, and the browser were working. Then it changed to normal internet access.

By then, the delay no longer seemed mysterious.

Windows does not test every application. It checks a few specific destinations. A VPN, firewall, DNS service, or captive portal can interrupt those checks even while real applications are already online.

The reverse can also happen. The icon may look normal because the Windows test succeeded, while a particular VPN route or application remains broken.

That makes the warning useful, but not decisive.

At the beginning, it pointed to a real problem: the airport portal had not been completed. Later, it lagged behind a connection that was already carrying my work.

The established provider complicated both stages. Its automatic protection hid the captive portal, and after authorization its route did not stay useful on the shifting lounge network.

The smaller service turned the same Wi-Fi into a working connection without making me test a string of countries. The preset matched the situation, the tunnel established cleanly, and the session survived the access-point changes.

A smaller benefit appeared after the meeting. While I checked the airport pages and flight board, the app’s blocked-request counter showed that it had stopped a stream of advertising and tracking requests.

That did not rescue the presentation or call. Those jobs were already complete. It simply made the remaining public-network session cleaner without adding another control panel to manage.

The service has fewer locations, fewer independent ratings, and a shorter public history than the established provider. Someone who needs a specific exit city may value the broader network more.

My requirement at the airport was narrower. I needed to enter the Wi-Fi properly, download one file, and remain in one call.

The larger VPN stayed green while my work remained offline. The smaller app made the airport connection useful before the client noticed I was travelling.