June 8, 2026

How I Fixed WSL 2 Network Timeouts on a Strict Corporate Network

If you use WSL 2 on a corporate laptop, you have likely run into this frustrating issue:

Souvede Inshuti

1 min read

  • git clone or other commands that need network to run timeout.
  • Your regular Windows terminal (cmd) works perfectly fine.
  • WSL works flawlessly at home or on a phone hotspot.

Here is the quick explanation of why this happens and how to fix it permanently using a single configuration file. (This is what worked for me)

The Problem

By default, WSL 2 uses NAT (Network Address Translation) mode [wsl]. It creates a hidden, isolated virtual network inside your machine.

Why Home Networks Work

  • Consumer routers are permissive.
  • They accept nested traffic coming from WSL's virtual IP addresses.

Why Corporate Networks Block It

  • Strict Firewalls: Enterprise firewalls drop unrecognized virtual IP packets to prevent security spoofing.
  • DNS Isolation: Offices block public DNS servers like 8.8.8.8. WSL's isolated sandbox cannot see your company's private internal DNS servers.

The Solution

We will use Mirrored Networking Mode (exclusive to Windows 11) [wsl]. This forces WSL to mirror your Windows internet connection exactly [wsl]. To your corporate firewall, WSL traffic looks completely identical to your authorized Windows traffic.

Step 1: Update the Windows WSL Config

  1. Press Win + R, type %USERPROFILE%, and hit Enter.
  2. Create or edit a file named exactly .wslconfig.
  3. Paste this configuration block and save:
[wsl2]
networkingMode=mirrored
dnsTunneling=true
  • networkingMode=mirrored clones your Windows connection into Linux [wsl].
  • dnsTunneling=true securely routes Linux DNS lookups through Windows corporate DNS servers [wsl].

Step 2: Clear Out Legacy Linux DNS Conflicts

Switching network modes can sometimes leave old, cached networking files stuck inside your Linux environment. We need to tell Linux to let Windows manage the DNS address resolution cleanly.

  1. Open your WSL Linux terminal.
  2. Run this command to delete any broken or hardcoded DNS files:
sudo rm -f /etc/resolv.conf
  1. Open (or create) the core WSL configuration file:
sudo nano /etc/wsl.conf
  1. Paste the following lines to ensure WSL automatically regenerates a clean network profile on launch:
[network]
generateResolvConf = true
  1. Save and exit the file (Ctrl + O, Enter, Ctrl + X).

Step 3: Flush Network Caches and Restart

Finally, completely reset the environment from your Windows host so the new settings take effect.

  1. Close your WSL window.
  2. Open a standard Windows PowerShell or Command Prompt (CMD) window.
  3. Run the following commands to forcefully shut down the active Linux subsystem and wipe the local network cache:
  • wsl — shutdown
  • ipconfig /flushdns

The Result

Reopen WSL and test your connection:

curl -Iv https://github.com

Linux environment will instantly pull down the data payload. Because your network identity is now perfectly mirrored from Windows [wsl], all your existing Git configurations, and local development scripts will work seamlessly without any manual terminal switching or duplicate setup.

Best of all, this configuration is completely set-and-forget — when you head home or jump on a hotspot, Windows will automatically mirror your new connection profiles straight down to WSL without you ever needing to toggle a setting again.