The Hotel Wi-Fi Connected One Device at a Time—One Verification Code Got All Three Ready for Deadline

My laptop was uploading the match footage, but my phone and tablet both said No Internet. I was in a Toronto hotel room after a World Cup match, with thirty-seven minutes left to deliver a post-game package to the newsroom. The laptop held the edited video. My phone carried the producer call and the authentication app required to approve the upload. The tablet displayed my timecoded notes so I could correct captions before the files went live. Only the laptop was properly connected. The hotel Wi-Fi appeared on all three devices with full signal, and my VPN was active on the laptop, yet the phone could not load email and the tablet could not open our production workspace. I assumed the hotel login had failed, forgot the network on both devices, and joined it again. The Wi-Fi symbols returned. Internet access did not.

The upload had reached 18 percent.

The producer asked whether I could still deliver before the next bulletin.

I said yes before I had worked out how.

One room login did not authorize every device

The hotel had been busy throughout the tournament. Recent reporting found that the World Cup had lifted travel demand and hotel revenue across host markets, particularly in major cities serving international visitors.

That evening, nearly every table in the lobby held a laptop, a phone charger, or someone refreshing a flight itinerary.

The network itself was not unusually slow. Once my laptop was online, the footage uploaded at a workable speed.

The problem was that the hotel did not treat “Room 814” as one connected guest. It treated the laptop, phone, and tablet as separate devices.

Hotel Wi-Fi often works in two stages: a device joins the network, then a browser page asks for a room number, password, payment, or acceptance of the terms before internet access begins.

My three devices had joined the Wi-Fi.

Only the laptop had completed the second stage.

That explained the misleading icons. The phone and tablet were connected to the hotel’s network, but the hotel had not yet authorized them to reach the internet.

I disconnected the VPN on my phone and opened a browser.

The hotel portal appeared.

I entered my surname and room number, accepted the terms, and waited for the confirmation page.

Email began loading.

One device down.

The tablet should have followed the same pattern.

Instead, it became trapped between the hotel login and the VPN.

Automatic protection blocked the page that had to come first

My established VPN provider was configured to connect automatically whenever it detected public Wi-Fi.

That was normally useful. I had chosen the service partly because it was familiar, mature, and available on every platform I carried.

On the tablet, automatic protection created a loop.

The tablet joined the hotel Wi-Fi.

The VPN immediately tried to connect.

The hotel would not provide normal internet access until I completed its portal.

The VPN could not reach its server without internet access, while its protection prevented the browser from reaching the hotel’s local sign-in page.

The tablet displayed Connecting.

The browser displayed No Internet.

Each was waiting for the other.

I disabled automatic connection, turned off the VPN, forgot the hotel network, and joined it again.

This time the portal opened.

I entered the room details for the third time.

The tablet reached the internet.

That solved the hotel side of the problem, but it left me with a new one.

The laptop was protected.

The phone and tablet were not.

The producer call had already moved to voicemail while I worked through the portal screens. I called back and put the phone on speaker.

“Upload status?” the producer asked.

“Thirty-one percent.”

“We need the interview clips and the caption file together.”

I opened the established VPN app on the phone.

It asked for my email and password.

I opened the password manager, approved the login, waited for a verification email, copied the code, returned to the app, and connected.

The producer’s voice disappeared for several seconds while the phone changed routes.

When the call returned, the laptop upload had paused at 34 percent.

The tablet presented the same account screen.

I had eighteen minutes left.

The service supported several devices. That was not the same as making several devices easy to connect under pressure.

The obvious hardware solution was at home

A travel router could have simplified the hotel side of the problem. It could sign in to the hotel network and create one private Wi-Fi network for the equipment behind it.

Travelers often use that approach because it avoids repeating captive-portal setup across every phone, tablet, laptop, and streaming device.

It was a sensible answer.

It was also sitting in a drawer at home.

Buying or configuring extra hardware would not help before the bulletin.

By then, all three devices already had hotel internet. What remained was getting the same protected service onto them without repeating passwords, email codes, and account approvals.

That distinction changed my decision.

I did not need another way to share Wi-Fi.

I needed a faster way to share the VPN.

The smaller app used the working laptop as the starting point

I stopped the upload, closed the established provider, and opened OnlydogVPN, which I had installed as a backup before the trip.

The smaller app offered a hotel-work preset rather than beginning with a server map.

I connected the laptop and restarted the upload.

Then I opened the device-sharing screen.

A short verification code appeared.

On the phone, I opened the smaller app and entered the code. There was no email field, password prompt, or separate account confirmation.

The phone connected.

The producer call stayed open.

I repeated the process on the tablet.

Code entered.

Device approved.

Connection active.

All three devices were protected before the restarted upload reached 7 percent.

That was the first result that mattered.

Not that three apps had been installed.

Not that three VPN icons had turned green.

The production workflow was finally operating as one system.

The laptop uploaded the interview clips.

The phone kept the producer call connected and received the newsroom’s approval request.

The tablet opened the shared caption sheet and synchronized my notes.

I corrected the first speaker’s name.

Then the second.

The producer asked me to check a quote at 02:18.

I found the timecode on the tablet, played the clip on the laptop, and confirmed the wording without disconnecting anything.

The upload reached 46 percent.

Then 63.

The hotel network slowed as guests returned from the stadium, but none of the devices demanded another VPN login.

At 82 percent, the newsroom sent an authentication request to my phone.

I approved it.

The laptop continued uploading.

At 9:53 p.m., the progress indicator reached 100 percent.

The caption file finished syncing a few seconds later.

The producer opened the package.

“We have video, captions, and notes,” she said. “You’re clear.”

The bulletin began seven minutes afterward.

One code removed the setup I was repeating

Once the deadline passed, the difference became easy to describe.

The hotel still required each device to complete its own portal. The smaller app did not erase that step.

It removed the second round of setup.

Once the laptop had a working protected connection, its verification code brought the phone and tablet into the same service without forcing me to rebuild the account session on each one.

That mattered because the devices were not interchangeable.

The laptop held the media.

The phone handled authentication and conversation.

The tablet held the notes.

Protecting only one of them would have left part of the workflow exposed or unusable.

The established provider could run on multiple devices, but it treated each installation as another login. At home, that would have been a minor inconvenience.

With a captive portal, a live producer call, and a deadline, every credential screen consumed time and attention I needed for the files.

The smaller app treated the devices as parts of the same task.

The phone remained connected when I left the room

After delivery, the producer asked me to stay available while the editors checked the footage.

I closed the laptop and carried the phone downstairs to collect food.

The hotel Wi-Fi weakened inside the elevator. Mobile data took over before I reached the lobby.

The call softened briefly but did not drop.

The connection recovered without asking for another verification code or account login.

I could not observe every internal rule used by the hotel network or each routing decision made inside the VPN applications. The visible comparison was clear: the established provider required a separate credential and approval sequence on each device, while the smaller app linked the phone and tablet from the working laptop and kept the production tools available through the deadline.

By the time I returned to the room, the editor had posted the finished segment.

I watched it on the tablet while answering the final production message on my phone.

The laptop remained closed.

All three devices had done their part.

Fewer setup steps mattered more than more server locations

The smaller service has fewer server locations, a shorter public history, and fewer independent reviews than the established provider.

That limitation matters when a traveler needs a specific exit city.

It did not decide whether my files reached the newsroom.

The established provider had broad coverage and mature infrastructure. What slowed me down was repeating its account process after completing the hotel portal separately on every device.

The smaller app reduced the part I could control. One working laptop produced a verification code, and that code brought the phone and tablet into the same protected workflow.

The hotel still saw three devices.

I stopped having to configure the VPN as though they belonged to three different trips.