Microsoft Teams Shows Your Real Location on a GL.iNet Travel Router VPN? Fix It

The moment every traveling remote worker dreads

You are working from a hotel in Lisbon. Your little GL.iNet travel router is plugged in, the VPN tunnel back to your home connection is up, and every IP check you run shows your home city. You feel invisible. Then you join the morning Teams standup, and your manager asks, “Hey, why does your meeting invite say 2 PM Lisbon time?” Or a colleague messages you: “Your Teams profile shows a different time zone than the rest of us.”

Your stomach drops. The whole point of the travel router was that nobody would know. So what went wrong?

Take a breath. This is one of the most common surprises remote workers discover on the road, and it is almost never the router’s fault. Your GL.iNet did exactly what you bought it for. The leak is somewhere else entirely, and it is sitting right under your fingers: the clock inside your work laptop.

Why Teams knows where you are even when your VPN says “home”

Here is the thing most people misunderstand about VPNs. A VPN changes one thing: your IP address, which is the internet address websites and apps see when your traffic arrives. Everything else about your laptop stays exactly the same. The apps on your machine, your system settings, your files, your clock, none of that changes when the VPN connects.

Microsoft Teams does not figure out your location from your IP address alone. It also reads your laptop’s own settings, and the loudest of those is the system time zone. If your laptop thinks it is in Lisbon, Teams happily tells everyone it is in Lisbon, even while your traffic exits through your home connection in Ohio. The VPN tunnel is working. Your laptop is simply ratting you out through a side channel the VPN was never designed to cover.

This distinction matters for everything else too. If you want the full picture of how employers detect VPN use, it helps to think of location as several separate signals, not one. Your IP address is only the first signal. The device settings on your laptop are the second, and Teams happens to listen to that one closely.

And to be clear about what you actually bought: if you are still fuzzy on what a home IP VPN is, it is a tunnel to your real home internet connection, so the internet sees your genuine home address instead of a commercial VPN server. That part is doing its job perfectly. The problem is the laptop behind the tunnel.

Step 1: Check your laptop’s time zone with timedate.cpl

The fastest way to see what your laptop believes about your location is the old Windows date and time panel. It takes about twenty seconds.

1. Press the Windows key + R. The little Run box appears.
2. Type timedate.cpl and press Enter. (That is a classic Windows command that opens the Date and Time window directly. It works on Windows 10 and Windows 11, even on machines where the newer Settings app behaves oddly.)
3. Look at the time zone listed. If it shows the city you are actually sitting in, or anything that is not your home location, you have found the leak.
4. Click “Change time zone” and pick your home time zone, the one that matches your home IP VPN location. Click OK.
5. Stop Windows from switching it back. Open Settings, go to Time and language, then Date and time, and turn off “Set time zone automatically”. When that switch is on, Windows uses your real location to guess the time zone, and it will quietly flip the setting back to wherever you actually are.

That is the core fix, and for most people it is the whole story. Teams reads the system time zone when it formats your meeting times and shows your local time to colleagues. Once the laptop believes it is at home, Teams believes it too.

One note: this changes the clock your whole laptop uses, which is what you want. Your calendar invites will now show home times, which is the point. If you also travel with a personal phone, keep its clock on the local time so you know when the taxi comes. Confusing the two is a rite of passage for new nomads.

Step 2: What to do when the time zone setting is greyed out

Now for the harder version of this problem. You open timedate.cpl, you click “Change time zone”, and nothing happens. The button is greyed out. Or you manage to change it, and the next time you reboot, the laptop flips it right back. This is the moment a lot of people email us in a panic.

Here is the honest truth: if you cannot change the time zone on your office laptop, that laptop is managed by your company’s IT department. The setting is locked by a policy (companies usually use Group Policy or a management tool like Microsoft Intune), which means your employer controls that laptop at a level you cannot override from your user account.

That lockdown is itself the answer to your question. Teams is not hacking past your VPN. Your company controls the device, the device reports its real time zone, and Teams simply reads it. The restriction that stops you from fixing it is the same restriction that keeps detecting you. On a fully managed laptop, this one is genuinely hard to work around on your own, and I am not going to pretend otherwise.

So what can you actually do? You have a few honest options:

• Ask IT, framed as a scheduling problem. You do not need to mention the travel router or the VPN. A reasonable request is: “I am traveling for a few weeks and my meeting times keep showing the wrong zone. Could you set my laptop’s time zone to [your home zone]?” Some IT teams will do this without a second thought. If yours refuses, you have learned something useful without confessing anything.
• Join Teams calls from a personal device. A personal laptop or tablet where you control every setting is free of the company lockdown. Change its time zone to home, and Teams on that device will show home. Keep the work laptop for the actual work behind the VPN tunnel.
• Use the Teams web app on a personal machine. If you cannot install the desktop app somewhere, the browser version of Teams works fine for most calls and respects the device it runs on.
• Check whether your account has admin rights. Some “managed” laptops still let a local admin account change the time zone through timedate.cpl even when the Settings app hides the option. Microsoft’s own support notes confirm the older panel can work when the newer one will not. If your account is a standard user, this door is closed, and that is by design.

If you want to read Microsoft’s own words on this, their support community covers why the time zone option appears greyed out and what causes it. The explanation is the same: on a company-managed machine, the setting belongs to IT, not to you.

Step 3: Plug the other location leaks

The time zone is the big one, but a careful setup checks a few more settings that can quietly give away where you are. Run through this list once before your trip and you will have covered almost everything.

• Windows location services. Go to Settings, Privacy and security, then Location. You can turn off Location services entirely, or at least turn off “Let apps access your location”. If Windows does not know where you are, it cannot tell anyone else either. Note that turning this off is also what disables the “set time zone automatically” feature, which is exactly what you want.
• Teams’ own location permission. In Windows 11, Teams can appear as a separate entry under Location permissions. Even with general location services on, you can deny Teams specifically. If Teams never gets a location reading, it falls back to the system time zone, which you have already set to home.
• Language and region. In Settings, Time and language, check “Language and region”. If the country or region flipped to where you are traveling, set it back to your home country. Some apps peek at this setting too.
• Corporate management apps. If your laptop runs your company’s device management software (the usual one is called Company Portal, from Microsoft Intune), understand what it does: it can report the device’s approximate location to your IT department directly, regardless of any VPN. No router setting changes this. If your laptop is enrolled in management, assume IT can see roughly where the device is, and plan accordingly.
• Your IP address itself. This part the router handles. Connect through your GL.iNet, then check your public IP on any “what is my IP” site and confirm it shows your home address. If it does not, fix the tunnel before you worry about anything else.

What your GL.iNet travel router can and cannot do

It helps to set expectations clearly, because the travel router marketing sometimes implies more magic than any router can deliver.

What it can do: give every device connected to it your real home IP address, encrypt your traffic between the hotel and your home, and keep hotel and cafe networks from snooping on what you do. A home ip vpn setup through a travel router is genuinely the strongest way to make your internet connection look like home, far better than any commercial VPN app whose server addresses are known and flagged.

What it cannot do: reach inside your laptop and change its clock, its language settings, or its company management policies. The router sits between your laptop and the internet. Everything that happens inside the laptop, the time zone, the location permissions, the management software, is outside the router’s reach. That is not a flaw in the router. No network device can do that.

If you have not picked a travel router yet, or you are wondering whether your model is up to the job, our comparison of choosing between the Slate AX and Beryl AX walks through the two most popular GL.iNet options for remote workers.

Your pre-travel checklist

Do this the evening before you fly, from home, while everything is calm. It takes ten minutes and it will save you a panicked hotel-room debugging session.

1. Verify your tunnel. Plug the travel router into your home network, connect your laptop through it, and confirm your public IP shows your home address.
2. Check the time zone. Run timedate.cpl and confirm it shows your home time zone. Turn off “set time zone automatically” in Settings.
3. Check location permissions. Confirm Windows location services are off (or at least denied to Teams) and your region still shows your home country.
4. Do a test Teams call. Call a friend or a second account and ask what they see: your local time, your meeting invite times. If anything looks off, you are still at home with time to fix it.
5. Pack the router admin app. Keep the GL.iNet app on your phone so you can check the tunnel status from anywhere without digging out the laptop.

Want this handled before your next trip?

Sorting out time zones, location permissions, tunnel settings, and a managed laptop takes some fiddling, and getting one detail wrong can undo the rest. If you would rather have someone set the whole thing up with you and test it before you fly, book a Pre-Travel Audit & Advisory session. It takes 1 hour, it costs $79, and that fee comes straight off the $379 Secure Home IP VPN System session if you decide to go ahead with it. We will walk through your laptop, your router, and your Teams setup together until everything looks like home.

Frequently asked questions