How to Fix Microsoft Tunnel Gateway Internal Network Accessibility Error
Question details
Users are experiencing internal network accessibility failures when connecting mobile devices through Microsoft Tunnel Gateway.

- Product
- Microsoft Tunnel Gateway / Microsoft Intune
- Device & OS
- Android and iOS
- Scenario
- Connecting mobile devices to internal corporate network resources via Microsoft Tunnel Gateway.
- Observed behavior
- Devices successfully connect to the gateway but cannot reach internal resources. The gateway health check reports an internal network accessibility failure indicating that return traffic is missing.
Before making configuration changes, ensure you have administrative access to the Microsoft Intune admin center, SSH access to the Linux server hosting the Tunnel Gateway, and the ability to view your internal network's routing and firewall logs.
Verify Network Routing and Firewall Rules
The most common cause of missing return traffic is improper routing or a firewall blocking the internal resources from communicating back to the Tunnel Gateway.
When the health check reports missing return traffic, it means the request from the mobile client is reaching the internal network, but the response is either not generated or cannot find its way back to the gateway.
Review your network firewall policies to ensure bidirectional traffic is allowed between the Microsoft Tunnel Gateway host and the target internal subnets.
Confirm that your internal network routers or switches have the correct static or dynamic routes configured so that internal resources know how to route return traffic back to the gateway's IP address.
Access the Linux server hosting the Tunnel Gateway and confirm that IP forwarding is enabled in the kernel settings (sysctl).
Check your Network Address Translation (NAT) configurations to ensure traffic is correctly translated between the mobile clients, the gateway, and the internal network.

Validate Microsoft Tunnel Configuration and Prerequisites
Ensure the gateway configuration in Intune correctly defines the target internal networks and that your server meets Microsoft's prerequisites.
Review Gateway Logs and Seek Advanced Support
If network settings appear correct, exporting and reviewing the gateway logs can identify specific container or traffic drop issues.
Simplify Your Workflow with a Lightweight Office Alternative
While resolving enterprise network and gateway routing issues can be highly technical and time-consuming, your everyday document tasks shouldn't be. WPS Office is a highly compatible, free, and lightweight alternative to Microsoft Office, perfect for seamless cross-platform document management without complex configurations.
- 1. Download the Installer: Visit the official WPS Office website and download the free installer for your operating system.
- 2. Install and Launch: Run the installer, follow the simple on-screen instructions, and launch the application.
- 3. Open Your Documents: Drag and drop your existing Microsoft Office files directly into WPS Office to start working immediately.

Frequently Asked Questions
Why does the Microsoft Tunnel health check report missing return traffic?
This error typically occurs when the internal network lacks a proper route back to the Microsoft Tunnel Gateway server, or when an internal firewall is blocking the return network packets from reaching the gateway.
What are the OS requirements for hosting Microsoft Tunnel Gateway?
Microsoft Tunnel Gateway requires a supported Linux distribution, such as Red Hat Enterprise Linux (RHEL) or Ubuntu, and utilizes container runtimes like Podman or Docker depending on Microsoft's current prerequisites.
Can split tunneling misconfigurations cause accessibility errors?
Yes. If the internal IP ranges are not correctly specified in your Intune split tunneling configuration, the mobile devices will not route the traffic through the VPN tunnel, resulting in an inability to reach those internal resources.
How do I export logs for Microsoft Tunnel Gateway?
You can export the logs by connecting to the Linux server hosting the gateway via SSH and running the 'mst-cli server logs' command. This generates an archive of diagnostic data that can be analyzed or sent to Microsoft Support.




