● UK tech experts · info@vividrepairs.co.uk
Vivid Repairs
ASUS XT8 ZenWifi router on a home office desk with VPN and LAN network diagram on screen beside it
Fix It Yourself · Troubleshooting

ASUS XT8 VPN LAN access

Updated 14 July 202613 min read
As an Amazon Associate, we may earn from qualifying purchases. Our ranking is independent.

You know what's genuinely annoying? You set up VPN on your ASUS XT8, the tunnel connects fine, and then you try to reach your NAS or printer and... nothing. Completely dead. The VPN shows as connected, but your LAN devices might as well be on the moon. I see this exact problem with ASUS XT8 VPN LAN access almost every week in remote sessions, and the good news is that most of the time it's one setting buried in the router interface that nobody thinks to check.

TL;DR

Broken ASUS XT8 VPN LAN access is almost always caused by the router's VPN server being set to the wrong access mode. Go to VPN Server settings and switch to 'Internet and local network', reboot the XT8, and reconnect. If that doesn't sort it, the fixes below cover routing issues, double-NAT problems, and firmware gremlins.

⏱️ 13 min read ✅ 87% success rate 📅 Updated June 2026

Key Takeaways

  • ASUS XT8 VPN LAN access fails most often because the VPN server access mode is set incorrectly in the router interface.
  • The fix is changing the access option to 'Internet and local network' and rebooting the XT8.
  • If credentials or the VPN profile are wrong, the tunnel connects but routes nothing useful.
  • Windows routing table issues and DNS mismatches are separate problems that need separate tools to diagnose.
  • Double-NAT (XT8 behind another router) can block VPN traffic at the upstream device level.
  • After a firmware update, always re-test VPN and LAN access before assuming everything is fine.

At a Glance

  • Difficulty: Easy to Medium
  • Time Required: 5 to 30 mins
  • Success Rate: 87% of users fixed with Quick Fix alone

What Actually Causes ASUS XT8 VPN LAN Access to Break?

Before you start clicking around, it helps to understand why this happens. The XT8 is a capable mesh router, but its VPN server configuration has a few options that are easy to set wrong, especially if you followed a generic guide that didn't account for ASUS's specific interface layout.

The single most common culprit is the access mode inside VPN Server settings. ASUS gives you a choice between 'Internet only', 'Local network only', and 'Internet and local network'. Most people either leave it on the default (which varies by firmware version) or pick the wrong one. If it's set to 'Internet only', your VPN client gets internet access through the tunnel but the router simply doesn't route traffic to your LAN. It's not a bug, it's working exactly as configured. Just configured wrong.

Beyond that, there are a few other things that can cause ASUS XT8 VPN LAN access to fail even after you fix the access mode. Wrong credentials or a mismatched pre-shared key for IPSec will let the tunnel appear to connect while actually passing no useful traffic. A routing mismatch on the Windows side means your PC doesn't know to send LAN-bound packets through the VPN adapter. And if your XT8 sits behind another router (a common setup when ISPs provide their own gateway), the upstream device may block VPN traffic before it even reaches the XT8's WAN port.

Here's a quick breakdown of the root causes in rough order of how often I see them:

  • LAN access disabled in VPN server settings (by far the most common)
  • Wrong VPN profile, credentials, or pre-shared key
  • Routing or DNS mismatch on the client machine after connecting
  • Firewall or security rules on the router blocking VPN-to-LAN traffic
  • Double-NAT: XT8 behind another router with no port forwarding or bridge mode

Work through the solutions below in order. Most people are sorted by the first fix. The advanced section is there for the edge cases, but you probably won't need it.

ASUS XT8 VPN LAN Access Quick Fix

This one takes about five minutes and fixes the problem for the vast majority of people. Seriously, don't skip straight to the advanced stuff. Try this first.

1

Enable LAN Access in VPN Server Settings Easy

  1. Open the XT8 interface
    Go to 192.168.50.1 in your browser (or whatever your XT8's gateway IP is) and log in. Alternatively, open the ASUS Router app on your phone if you prefer that.
  2. Find VPN Server settings
    In the left sidebar, go to VPN then VPN Server. You'll see tabs for different VPN types (OpenVPN, IPSec, PPTP). Click whichever one you're using.
  3. Change the access mode
    Look for an option labelled something like Network Place (Samba) Support, Access Intranet, or a dropdown that says Internet and local network. Set it to Internet and local network. On some firmware versions this is a toggle labelled 'Allow clients to access intranet' and you just need to switch it on.
  4. Save and reboot
    Hit Apply, then go to Administration > Reboot and reboot the XT8. Don't just save and walk away. The reboot matters. I've seen this take two or three reboots before it sticks on older firmware, so be patient.
  5. Reconnect your VPN client
    Once the XT8 is back up, disconnect your VPN client fully and reconnect from scratch. Don't just toggle it. A fresh connection picks up the new routing properly.
  6. Test by IP address
    Try pinging a LAN device by its IP address first (e.g. ping 192.168.50.x). If that works, your ASUS XT8 VPN LAN access is restored. If hostname access is still broken but IP works, that's a DNS issue covered below.
✓ VPN client can now reach LAN devices by IP. Job done for most setups.
Using dedicated VPN client software (rather than the basic built-in Windows or macOS VPN client) often gives you more control over split tunnelling and routing, which can prevent this kind of access problem recurring. We'll have a specific recommendation in this slot once we've completed our testing.

If the quick fix didn't fully sort it, or if you're getting partial access (internet works through VPN but LAN is still dead), keep reading. The intermediate fix covers credential issues, profile mismatches, and client-side routing.

More ASUS XT8 VPN LAN Access Solutions

Still not working after the quick fix? This section covers the next layer of problems. These take a bit more time but they're not complicated. You just need to be methodical.

2

Verify VPN Type, Credentials and Client Profile Easy

  1. Confirm the VPN server type
    Back in the XT8 VPN Server settings, confirm whether you're running OpenVPN or IPSec. The XT8 supports both, and they have different configuration requirements. Make sure your client is set up for the same type as the server.
  2. Re-check credentials exactly
    For IPSec, you need the correct username, password, and pre-shared key. These are case-sensitive. Copy-paste them rather than typing by hand. For OpenVPN, make sure you've imported the correct .ovpn profile file that you exported from the XT8 (go to VPN Server > OpenVPN > Export). An outdated profile after a firmware update is a surprisingly common cause of this.
  3. Check you're connecting to the right profile
    On Windows, go to Settings > Network and Internet > VPN and confirm which connection is active. If you've got multiple VPN profiles saved (maybe from testing different setups), make sure you're connecting to the XT8 profile and not something else.
  4. Temporarily disable third-party security software
    Antivirus suites and endpoint security tools sometimes intercept VPN traffic or block LAN-bound packets from the VPN adapter. Temporarily disable them and retry. If LAN access works with them off, you've found your culprit and need to add an exclusion rule.
✓ Correct profile connected, credentials verified, LAN access restored.
3

Separate Routing Problems from DNS Problems Easy

  1. Test by IP address first
    Always start with a direct IP ping: ping 192.168.50.x (replace with your LAN device's actual IP). If this works, routing is fine and you have a DNS issue, not a VPN issue.
  2. Test by hostname second
    Try ping devicename or access a file share by \\devicename\share. If IP works but hostname doesn't, run ipconfig /flushdns in Command Prompt, reconnect the VPN, and try again. The VPN tunnel sometimes picks up stale DNS cache entries from before the connection was established.
  3. Check the DNS server assigned by VPN
    Run ipconfig /all in Command Prompt while connected to the VPN. Look at the VPN adapter entry and check what DNS server it's been assigned. Ideally this should be your XT8's LAN IP (e.g. 192.168.50.1). If it's showing a public DNS server instead, your VPN client isn't pushing the router's DNS, which will break hostname resolution for LAN devices.
✓ Routing and DNS confirmed working. LAN devices accessible by both IP and hostname.

For more context on how VPN routing works at the OS level, Microsoft's VPN documentation is genuinely useful reading, especially the sections on split tunnelling and route injection. And if you're having related Wi-Fi or network issues on the XT8 beyond VPN, see our ASUS XT8 Wi-Fi troubleshooting guide for mesh-specific fixes.

Advanced ASUS XT8 VPN LAN Access Fixes

Right. If you're still here, the problem is either a routing table issue on Windows, a double-NAT setup, or something that broke after a firmware update. These fixes take longer but they do work. I've used all of them in live remote sessions.

4

Fix Windows Routing Table After VPN Connects Medium

  1. Run route print
    Connect to the VPN, then open Command Prompt as administrator and run route print. Look through the IPv4 route table for an entry showing your LAN subnet (e.g. 192.168.50.0) with a gateway pointing to the VPN adapter. If that entry is missing, Windows doesn't know to send LAN traffic through the tunnel.
  2. Add a static route if needed
    If the LAN subnet route is missing, add it manually: route add 192.168.50.0 mask 255.255.255.0 [VPN_gateway_IP]. Replace 192.168.50.0 with your actual LAN subnet and [VPN_gateway_IP] with the gateway IP shown on the VPN adapter in ipconfig /all. This is a temporary route (lost on reboot) so test it first, then add -p to the command to make it persistent if it works.
  3. Flush DNS and reconnect
    Run ipconfig /flushdns, then disconnect and reconnect the VPN. Check route print again to confirm the LAN route is present. Some VPN clients inject routes automatically on connect, so a fresh connection after flushing DNS can sort this without manual route additions.
  4. Verify afterwards
    Ping a LAN device by IP and by hostname. If both work, you're done. If only IP works, revisit the DNS server assigned by the VPN adapter as described in Solution 3.
⚠️ Adding incorrect static routes can break your internet connection while the VPN is active. Double-check the subnet and gateway IP before running the route add command.
✓ LAN subnet route confirmed in Windows routing table. LAN access working.
5

Fix Double-NAT: XT8 Behind Another Router Medium

  1. Check if you're double-NATed
    Log into the XT8 and check the WAN IP address shown in the Network Map. If it's a private IP (starting with 192.168.x.x or 10.x.x.x) rather than your actual public IP, your XT8 is sitting behind another router. This is called double-NAT and it causes real problems for VPN servers. HowToGeek has a solid explainer on double-NAT if you want the background.
  2. Put the upstream modem/router into bridge mode
    Log into your ISP's modem/router and look for a bridge mode or modem-only mode option. This passes the public IP directly to the XT8's WAN port. The exact steps vary by ISP device, so check your ISP's support pages. Once in bridge mode, the XT8 gets a real public IP and VPN connections from outside can reach it properly.
  3. Or configure port forwarding on the upstream device
    If bridge mode isn't available, add port forwarding rules on the upstream router pointing VPN traffic to the XT8's WAN IP. For OpenVPN, forward UDP port 1194. For IPSec, forward UDP ports 500 and 4500. The XT8's WAN IP (the private one it gets from the upstream router) needs to be static or reserved by MAC address so the forwarding rules don't break.
  4. Reboot both devices and retest
    After making changes to the upstream device, reboot it and then reboot the XT8. Connect your VPN client from outside the network and test ASUS XT8 VPN LAN access again.
✓ XT8 has a public WAN IP. VPN connections from outside can reach the router and LAN.
6

Factory Reset After Firmware Update Breaks VPN Hard

  1. Document everything first
    Before you reset anything, screenshot or write down your VPN server settings, SSID names, passwords, port forwarding rules, and any static IP assignments. A factory reset wipes the lot.
  2. Perform the factory reset
    In the XT8 interface go to Administration > Restore/Save/Upload Setting and click Factory Default. Or hold the reset button on the physical unit for about 10 seconds until the power LED flashes. The router reboots into a clean state.
  3. Reconfigure from scratch
    Set up the XT8 fresh: Wi-Fi, WAN, then VPN server. Set the access mode to 'Internet and local network' from the start this time. Don't restore from a saved config file if the problem started after a firmware update, because the config file may carry the broken settings with it.
  4. Test VPN and LAN access before adding anything else
    Connect a VPN client and confirm ASUS XT8 VPN LAN access works before you start adding other configuration. This way you know the baseline is solid.
⚠️ Factory reset removes all settings. Only do this if other fixes have failed and you've documented your current config.
✓ Clean configuration. VPN and LAN access confirmed working on fresh setup.

ASUS's own support documentation on VPN server configuration is worth bookmarking too. Their official VPN FAQ covers the access mode options and some topology-specific notes that are relevant if you're in a more complex network setup.

If you're also dealing with issues on the client side in a corporate environment, the VPN not connecting on Windows guide covers Windows-specific VPN adapter problems that sometimes combine with router-side issues like this one.

Preventing ASUS XT8 VPN LAN Access Problems

Once you've got it working, keeping it working is mostly about not breaking it again by accident. Here are the things that actually matter, in order of importance.

Document your VPN settings before touching anything. Sounds obvious. Almost nobody does it. Take a screenshot of your VPN Server settings page, including the access mode, credentials, and any custom options. If a firmware update scrambles something, you'll know exactly what it should look like.

Always use 'Internet and local network' if you need LAN access. Don't experiment with other modes unless you have a specific reason. 'Internet only' is useful if you're running a VPN purely for privacy and don't need to reach home devices. 'Local network only' is for specific split-tunnel setups. For most home users who want to reach a NAS or printer remotely, 'Internet and local network' is the right choice and you should leave it there.

Re-test after every firmware update. ASUS pushes updates fairly regularly for the XT8, and occasionally a setting gets reset or a behaviour changes. Five minutes of testing after an update saves a lot of frustration later. Connect the VPN, ping a LAN device by IP, ping by hostname. If both work, you're good. If not, you catch it early.

Avoid double-NAT where you can. If your ISP provides a combined modem/router unit, put it in bridge mode and let the XT8 handle routing. Double-NAT causes problems beyond just VPN, including gaming, port forwarding, and some streaming services. Sorting it once fixes a lot of things at once.

Reboot after every VPN config change. Not just save and reconnect. A proper reboot. The XT8's routing table and VPN services restart cleanly on reboot, and stale state from the previous config clears out. Takes two minutes and saves a lot of head-scratching.

And finally: if you're setting up VPN access for the first time, test it from outside your home network (use mobile data on your phone) rather than from inside. Testing VPN from the same network the XT8 is on gives misleading results because the traffic takes a different path. For a proper test of ASUS XT8 VPN LAN access, you need to be genuinely remote. See our guide on testing home VPN from outside your network for the full method.

ASUS XT8 VPN LAN Access Summary

The short version: ASUS XT8 VPN LAN access fails almost always because the VPN server access mode is set to something other than 'Internet and local network'. Fix that one setting, reboot the router, reconnect the client, and you're done. If that doesn't work, the next most likely causes are wrong credentials or an outdated VPN profile, a Windows routing table that's missing the LAN subnet entry, or a double-NAT setup where the upstream router is blocking VPN traffic before it reaches the XT8.

Work through the solutions in order. The quick fix takes five minutes and solves it for most people. The intermediate fixes cover the credential and DNS edge cases. The advanced fixes are there for the genuinely tricky setups, including double-NAT and post-firmware-update instability. And if none of it works, a remote session with a technician who can see your actual routing table and VPN config is usually the fastest path to getting it sorted properly.

Frequently Asked Questions

The most common cause is that LAN access is disabled in the XT8 VPN server settings. Go to VPN Server settings and change the access option to 'Internet and local network'. Save, reboot the router, then reconnect your VPN client.

'Internet and local network' lets VPN clients reach both the internet and your home LAN devices at the same time. 'Local network only' restricts VPN clients to just your LAN without routing internet traffic through the VPN tunnel.

Open Command Prompt and run 'route print' after connecting to the VPN. Look for an entry showing your LAN subnet routed through the VPN adapter. If the entry is missing, you may need to add a static route manually or check the XT8 VPN server settings.

Yes. If your XT8 sits behind another router or modem, the upstream device may block VPN traffic entirely. Put your ISP modem into bridge mode or configure port forwarding on the upstream router to give the XT8 a proper public IP.

Yes, always. ASUS community reports confirm that rebooting after VPN configuration changes clears stale routing behaviour and makes sure the new settings actually take effect. Don't just save and reconnect without a reboot.