VPN Blocking NAS Access? Fix Local Network Issues Fast

Quick answer: If your VPN is blocking NAS access, the most common fixes are enabling “allow LAN access” in your VPN app, using split tunneling, disabling the VPN kill switch temporarily, checking subnet conflicts, using the NAS IP address instead of its hostname, and making sure SMB, Plex, Synology, QNAP, or local discovery traffic is not being routed through the VPN tunnel.

If your NAS, Plex server, shared folders, printer, media server, or local devices disappear when you connect to a VPN, the problem is usually not the NAS itself. It is usually caused by how the VPN handles local network traffic.

A VPN changes your device’s network route. That is useful for privacy because internet traffic goes through the encrypted VPN tunnel. But if the VPN app is configured to block local network access, force all traffic through the tunnel, use a strict kill switch, or create a subnet conflict, your computer may no longer be able to reach devices on your own LAN.

This guide explains why a VPN can block NAS access and how to fix local network issues without turning your VPN off completely.

Why Your VPN Blocks NAS Access

Your NAS is usually on your local network, also called your LAN. It might have an address like:

192.168.1.50
192.168.0.20
10.0.0.15

When your VPN connects, your device may create a new virtual network adapter and change the default route. Depending on the VPN settings, your computer may start sending traffic through the VPN tunnel instead of directly to your local network.

That can break access to:

• Synology NAS
• QNAP NAS
• TrueNAS / FreeNAS
• Unraid servers
• Western Digital My Cloud
• Plex servers
• Jellyfin or Emby servers
• SMB / Windows file shares
• Network printers
• Local web dashboards
• Router admin panels
• Home Assistant
• Docker services on your LAN

The fix depends on whether your VPN is blocking all LAN traffic, breaking local name resolution, creating an IP/subnet conflict, or interfering with discovery protocols.

Common Signs Your VPN Is Blocking Local Network Access

Fix 1: Enable “Allow LAN Access” in Your VPN App

The first setting to check is local network access. Many VPN apps include a setting with names such as:

• Allow LAN access
• Allow local network access
• Local network sharing
• Allow access to local devices
• Bypass VPN for local network
• Invisible on LAN / visible on LAN

If this setting is disabled, your VPN may intentionally block communication with local devices. That can be useful on public Wi-Fi, but it can break NAS access at home.

What to do:

1. Open your VPN app.
2. Go to Settings.
3. Look for local network, LAN, or network access settings.
4. Enable local network access.
5. Reconnect the VPN.
6. Try accessing your NAS again.

This single setting fixes many cases where a NAS becomes unreachable as soon as the VPN connects.

Fix 2: Use the NAS IP Address Instead of the Hostname

If your NAS works by IP address but not by name, the VPN is probably breaking local name resolution rather than blocking the NAS itself.

For example, this may fail:

\\synology-nas
http://qnap.local:8080
http://truenas.local

But this may work:

\\192.168.1.50
http://192.168.1.50:5000
http://192.168.1.50:32400

Local hostnames often rely on mDNS, NetBIOS, local DNS, or router-based name resolution. A VPN can interfere with those lookups because it may push its own DNS servers or route DNS queries through the tunnel.

What to do:

1. Find your NAS IP address in your router admin panel or NAS interface.
2. Try accessing the NAS directly by IP address.
3. If it works, bookmark the IP-based URL.
4. Consider setting a static IP or DHCP reservation for the NAS.

For long-term reliability, give your NAS a fixed local IP address. That way, your mapped drives, Plex server, and admin dashboard do not break when the router assigns a new address.

Fix 3: Check Split Tunneling

Split tunneling lets you decide which apps or traffic go through the VPN and which stay on your normal local connection. This is one of the best fixes when a VPN blocks NAS, Plex, SMB, or local dashboard access.

For example, you may want:

• Your browser to use the VPN.
• Your torrent client to use the VPN.
• Your NAS dashboard to stay local.
• Your Plex server to stay reachable on the LAN.
• Your backup software to connect directly to the NAS.

If your VPN supports split tunneling, exclude apps that need local access. Depending on your setup, this might include:

• File Explorer / Windows Explorer
• Finder on macOS
• Plex Media Server
• Plex desktop app
• Synology Drive Client
• QNAP Qsync
• Backup software
• Docker desktop tools
• Browser used only for local admin pages

Split tunneling can be powerful, but it needs to be configured carefully. If the wrong app is excluded, or if only part of the connection is excluded, you can create inconsistent routing. For more background, see What is VPN split tunneling and how to make it work.

Fix 4: Disable the VPN Kill Switch Temporarily

A VPN kill switch is designed to block traffic if the VPN disconnects. That is useful for privacy, but some strict kill switch modes also block local network traffic or create firewall rules that interfere with NAS access.

Temporarily test this:

1. Open your VPN app.
2. Find the kill switch setting.
3. Disable it temporarily.
4. Reconnect the VPN.
5. Try accessing your NAS.

If NAS access works after disabling the kill switch, the kill switch rule is likely too strict. Some VPNs let you keep the kill switch enabled while still allowing LAN traffic. That is the ideal setup.

Do not leave the kill switch off permanently if you rely on the VPN for sensitive traffic. Instead, look for a setting that allows local network access while keeping internet leak protection active. See also: Why you need a VPN kill switch.

Fix 5: Check for Subnet Conflicts

A subnet conflict happens when your local network and VPN network use overlapping IP ranges. This can confuse routing and make your NAS unreachable.

For example, your home LAN might use:

192.168.1.0/24

And the remote VPN network may also use:

192.168.1.0/24

When both networks use the same range, your device may not know whether 192.168.1.50 is your local NAS or something on the VPN side.

Common home router ranges include:

• 192.168.0.x
• 192.168.1.x
• 192.168.50.x
• 10.0.0.x
• 10.0.1.x

If you regularly use VPNs, it can be smart to move your home LAN to a less common subnet, such as:

192.168.77.0/24
192.168.88.0/24
10.10.10.0/24

Changing your router subnet is a bigger step because it affects every device on your network. But for persistent NAS and VPN routing problems, it can be the cleanest long-term solution.

Fix 6: Add a Static Route to Your Local Network

Advanced users can fix local access issues by adding a static route. This tells your device that traffic to your LAN should go through the local gateway instead of the VPN tunnel.

Example local network:

Local LAN: 192.168.1.0/24
Router: 192.168.1.1
NAS: 192.168.1.50

The goal is to make sure traffic to 192.168.1.0/24 stays local.

On Windows, this may look like:

route print

Then add a route if needed:

route add 192.168.1.0 mask 255.255.255.0 192.168.1.1

On macOS or Linux, you may inspect routes with:

netstat -rn
ip route

Static routes can fix stubborn NAS access issues, but they should be used carefully. Incorrect routes can break connectivity. If your VPN app already has an “allow LAN” option, use that first.

Fix 7: Check SMB and File Sharing Settings

If your NAS dashboard works in a browser but mapped drives or shared folders do not work, the issue may be SMB/file sharing rather than general NAS access.

SMB is used by Windows file sharing and many NAS systems. VPNs can interfere with SMB if local discovery is blocked or if the device treats the VPN as a public/untrusted network.

On Windows

1. Make sure Network Discovery is enabled.
2. Make sure File and Printer Sharing is enabled.
3. Set your home network as Private, not Public.
4. Try connecting by IP address: \\192.168.1.50
5. Re-map the network drive using the NAS IP.

On macOS

Use Finder > Go > Connect to Server and enter:

smb://192.168.1.50

If the IP-based SMB path works, the issue is probably local name resolution rather than SMB itself.

Fix 8: Allow Plex, Jellyfin, or Emby on the Local Network

Media servers can be especially sensitive to VPN routing. Plex, Jellyfin, and Emby may rely on local discovery, server advertisement, and specific ports. If the VPN routes everything through the tunnel, local clients may stop finding the server.

For Plex, the common local port is:

32400

Try accessing Plex directly:

http://192.168.1.50:32400/web

If Plex works by IP but not through discovery, the VPN is likely interfering with local discovery rather than blocking the server completely.

Recommended fixes:

• Enable LAN access in the VPN app.
• Exclude Plex Media Server from the VPN tunnel if needed.
• Exclude the Plex client app from the VPN tunnel.
• Use the server’s local IP address.
• Make sure the server and client are on the same subnet.
• Check firewall rules for Plex ports.

If you run Plex on the same machine as the VPN, split tunneling may be necessary. Otherwise, Plex may advertise the VPN IP instead of the LAN IP, causing local devices to fail when discovering the server.

Fix 9: Check Firewall Rules Created by the VPN

Some VPN apps create firewall rules to prevent leaks. These rules can block local inbound or outbound traffic, especially when the VPN is active.

On Windows, check:

• Windows Defender Firewall
• Third-party firewall software
• VPN-created firewall rules
• Network profile type: Public vs Private

On macOS, check:

• System Settings > Network
• Firewall settings
• Local network permissions
• Security software network filters

If the NAS is reachable when the firewall is disabled temporarily, create a proper allow rule rather than leaving the firewall off.

Fix 10: Change DNS Settings Carefully

DNS can break NAS access when local hostnames depend on your router or local DNS server. When the VPN connects, it may push VPN DNS servers and ignore your router’s DNS.

This can break names like:

• synology.local
• qnap.local
• nas.home
• truenas.local
• plex.local

Ways to fix it:

• Use the NAS IP address directly.
• Add a local hosts file entry.
• Use split DNS if supported.
• Keep local DNS for LAN traffic and VPN DNS for internet traffic.
• Disable custom DNS temporarily and test again.

DNS issues can also create privacy leaks if misconfigured. If you are changing DNS settings, understand the tradeoff. See DNS leaks explained.

Fix 11: Check IPv6 Behavior

Some local networks and NAS setups use IPv6. Some VPNs block IPv6 to prevent leaks, while others support it only partially. If your NAS discovery relies on IPv6 or mDNS behavior, the VPN may interfere.

Try these tests:

• Access the NAS by IPv4 address instead of hostname.
• Disable IPv6 temporarily on the client device and test.
• Check whether your VPN blocks IPv6 traffic.
• Check whether the NAS has both IPv4 and IPv6 enabled.

For most home NAS setups, a stable IPv4 address is the simplest and most reliable method.

Fix 12: Reconnect in the Right Order

Some local network issues happen because apps are already open before the VPN route changes. Reconnecting in the right order can reset the session.

Try this order:

1. Disconnect the VPN.
2. Close the NAS app, file manager, Plex app, or browser tab.
3. Reconnect Wi-Fi or Ethernet if needed.
4. Connect to the VPN.
5. Open the NAS by IP address.
6. Then test hostname or mapped drive access.

This is not a deep configuration fix, but it can clear stale routes and broken sessions.

Synology NAS Not Accessible with VPN: Fixes

If Synology DSM is unreachable when your VPN is active, try these steps:

• Open DSM by IP address, for example http://192.168.1.50:5000 or https://192.168.1.50:5001.
• Enable LAN access in your VPN app.
• Check whether Synology Drive Client is routed through the VPN.
• Disable split tunneling temporarily to test, then configure it correctly.
• Check firewall rules in DSM.
• Make sure your Synology NAS has a static IP or DHCP reservation.

If DSM works by IP but not by hostname, fix local DNS or use the IP address permanently.

QNAP NAS Not Accessible with VPN: Fixes

If your QNAP dashboard or file shares stop working after connecting to a VPN, check:

• QNAP IP address and port.
• SMB access by IP address.
• VPN LAN access setting.
• QNAP firewall/security settings.
• Router DHCP reservation.
• Whether Qsync is excluded or included in split tunneling correctly.

Try opening QNAP directly by IP instead of using local discovery tools.

TrueNAS, Unraid, or Home Server Not Reachable with VPN

For TrueNAS, Unraid, Proxmox, Docker hosts, and self-hosted dashboards, the issue is often routing or subnet conflict.

Check:

• Local IP address of the server.
• Whether the VPN uses the same subnet.
• Firewall rules on the server.
• Docker bridge networks that overlap with VPN ranges.
• Whether the service is bound to the LAN interface or VPN interface.
• Whether the app is advertising the wrong IP address.

Self-hosted environments can be more complex because Docker, virtual machines, and VPN clients may all create their own network adapters.

Best Setup: Keep Internet Traffic on VPN, Keep NAS Traffic Local

For most home users, the ideal setup is:

• Internet traffic goes through the VPN.
• Local NAS traffic stays on the LAN.
• DNS does not leak unnecessarily.
• SMB and Plex stay reachable locally.
• The kill switch protects internet traffic but does not block local devices.

That usually means enabling local network access in the VPN app and using split tunneling only when needed.

Security Warning: Do Not Expose Your NAS Just to Fix VPN Access

Do not solve local VPN problems by exposing your NAS admin panel directly to the public internet. Opening NAS ports to the internet can create serious security risks, especially if the NAS firmware, apps, or passwords are weak.

Avoid unnecessary public exposure of:

• DSM admin ports
• QNAP admin ports
• SMB ports
• FTP ports
• Unraid dashboards
• TrueNAS admin panels
• Docker admin tools

If you need remote NAS access, use a safer method such as a properly configured VPN server, Zero Trust tunnel, Tailscale-style mesh VPN, or vendor-supported secure relay. For many users, remote access security matters more than convenience.

Fast Troubleshooting Checklist

1. Try accessing the NAS by IP address.
2. Enable “allow LAN access” in your VPN app.
3. Switch VPN server and reconnect.
4. Disable the kill switch temporarily to test.
5. Turn off split tunneling temporarily.
6. Check whether your LAN and VPN subnets overlap.
7. Re-map SMB shares using the NAS IP address.
8. Check firewall rules on your computer and NAS.
9. Disable custom DNS temporarily.
10. Test Plex or NAS dashboard by direct IP and port.

When the VPN Is Installed on the NAS Itself

Some users install the VPN directly on the NAS rather than on their computer. That creates a different set of problems. If the NAS itself connects to a commercial VPN, it may route outbound traffic through the VPN tunnel while local clients expect the NAS to remain reachable on the LAN.

Common problems include:

• NAS web interface becomes unreachable.
• Plex remote access breaks.
• Docker containers route through the wrong interface.
• Download clients work but local apps cannot connect.
• The NAS advertises the VPN IP instead of LAN IP.

In that case, check routing rules on the NAS, Docker network settings, service binding, and whether the NAS firewall allows local subnet access. You may need policy-based routing so only selected apps use the VPN while the NAS management interface stays on the LAN.

Should You Turn Off Your VPN to Access Your NAS?

You can turn off the VPN as a temporary workaround, but it is not the best long-term fix. If you regularly use a NAS, configure the VPN properly so local traffic remains available while internet traffic stays protected.

The best long-term solution is usually one of these:

• Enable LAN access in the VPN app.
• Use split tunneling for NAS-related apps.
• Use static IPs for local devices.
• Fix subnet conflicts.
• Add local routes for advanced setups.

If your VPN frequently breaks more than just NAS access, see VPN connected but no internet and VPN not connecting.

FAQ: VPN Blocking NAS and Local Network Access