Proton VPN local network

What “Allow LAN connections” does

• Lets your device reach devices on your local network (LAN) during a VPN session.
• Bypasses VPN routing for local network traffic while still using the VPN for internet traffic.
• Works with common LAN tasks like printing, file sharing, or discovering devices by name.

Important note: Not all Proton VPN platforms may label the option exactly the same, but the concept is the same across Windows and other supported clients.

How to enable LAN access on Windows

1. Open the Proton VPN app.
2. Go to Settings. Depending on the version, this may be labeled as ⚙ Settings or a gear icon.
3. Navigate to Connection → Advanced settings.
4. Find the switch labeled Allow LAN connections (or LAN connections) and toggle it on.
5. Restart the VPN connection if necessary and test access to a LAN device.

What you might see after enabling:

• Your VPN connection remains active for internet traffic.
• Local network traffic is routed directly to your LAN devices, rather than going through the VPN tunnel.
• You can connect to devices by name or by IP, depending on how your LAN resolves names.

How to enable LAN access on other platforms

• macOS and iOS: The same general steps apply, open the Proton VPN app, locate Settings or Connection options, and enable LAN connections if available.
• Android: Look for LAN or local network access settings under VPN or connection options, then enable.
• Linux: Proton VPN GUI or CLI may offer an equivalent “LAN access” toggle under advanced settings.

If you don’t see the option, ensure your Proton VPN client is up to date. Some older builds or configurations may not expose the LAN access toggle as clearly. NordVPN turn off auto connect

Access devices by name on the LAN

When LAN access is enabled, you can often reach devices on your local network by their hostnames, rather than by IP address. For example:

• printer.local
• router.local
• MyNAS.local

If your network uses Windows-style naming or.local mDNS, you’ll want to ensure your devices advertise their names properly:

• Enable device name broadcasting on the device (DHCP/DNS settings often control this).
• Make sure your computer’s network discovery and name resolution are configured correctly.

Note: In some environments,.local name resolution may rely on mDNS or a local DNS setup. If Proton VPN’s LAN access doesn’t resolve names, try using the direct IP address of the device to confirm connectivity.

Troubleshooting common LAN access issues

• Problem: VPN seems to block local network devices. Action: Double-check that LAN access is enabled in the Proton VPN app’s advanced settings. Some clients require you to toggle the option on and then reconnect.
• Problem: Devices are not resolving by name. Action: Confirm that mDNS/Bonjour or your LAN DNS is functioning. Try pinging by IP first to verify connectivity, then by hostname.
• Problem: Slow or dropped LAN connections. Action: Ensure your LAN device’s firewall isn’t blocking connections from the VPN subnet. Some home networks isolate devices on different subnets for security.
• Problem: Devices inaccessible across subnets. Action: LAN access typically works within the same local subnet. If you’re on a VPN that assigns a different subnet, ensure your router allows cross-subnet LAN traffic or consider configuring your LAN for wider discovery.

Table: typical behavior with and without LAN access

When LAN access is not an option

• Some corporate or enterprise VPN configurations disable local network access by design. In these cases, LAN access might be blocked by policy or router/firewall rules.
• If you’re using a VPN that handles split-tunneling differently, you may need to adjust router settings or use alternative paths for local device access.
• If you require access to local devices from multiple networks, consider a VPN profile or route that supports selective tunnel and LAN bypass, or consult Proton VPN support for advanced split-tunnel configurations.

Practical tips for a smooth experience

• Keep your Proton VPN client up to date to ensure LAN access features are present and stable.
• Reboot devices if local name resolution stops after enabling LAN access.
• Maintain consistent device naming on the LAN to simplify connectivity (e.g., printer, NAS, TV with predictable hostnames).
• Test with a simple use case first (e.g., print a document or access a file on a NAS) before attempting more complex tasks.
• Document your LAN device names and their IPs for quick reference during VPN sessions.

Real-world scenarios where LAN access helps

• Remote workers wanting to print to a home printer while connected to a corporate VPN.
• Small offices with shared NAS devices that need to be accessible from VPN-connected laptops.
• Home labs where you frequently access lab controllers, switches, or IoT hubs from remote devices.

Final considerations

• Enabling LAN access is a targeted feature designed to bridge VPN usage with local network needs. When properly enabled, it allows you to interact with devices on your LAN as if you were on the same network, even while connected to Proton VPN for external internet traffic.
• If you encounter persistent issues, consult Proton VPN support or community forums for platform-specific guidance and updated recommendations, as the exact UI and feature availability can vary between app versions and operating systems.

Recommendation If your goal is to access local devices (printers, NAS, or other computers) while connected to Proton VPN, enable LAN connections in the Proton VPN app’s advanced settings and test access to a known LAN device. Ensure your LAN device naming is consistent and that your network’s discovery features are enabled. If you rely on name-based access, confirm that your local DNS or mDNS/Bonjour service is functioning properly. Regularly update the Proton VPN client and revisit the LAN access setting after major app updates to preserve compatibility.