In this article

When the Windows Roaming Client runs on a computer with Windows Subsystem for Linux (WSL), WSL can have recurring connectivity issues, such as:

• "No route to host" errors
• WSL networking that works for a while after a restart, then fails again

These issues occur because the Roaming Client interferes with the default NAT networking mode in WSL. There are two methods to resolve this issue.

Method 1: Use mirrored networking (recommended)

Switching WSL to mirrored networking mode resolves the conflict.

This method requires Windows 11 version 22H2 or later and WSL version 2.0.9 or later.

1. Create or edit a .wslconfig file in the Windows user directory (C:\Users\<UserName>\.wslconfig).

2. Add these lines:

   [wsl2]
   
   networkingMode=mirrored

3. Save the file and restart the WSL distributions.

WSL can then reach the network without the "no route to host" error.

Method 2: Configure DNS manually

Use this method if mirrored networking is not supported. With this method, DNS queries from the WSL distribution go directly to 1.1.1.1 and 8.8.8.8, and DNSFilter does not filter them.

1. Open the WSL distribution.

2. Remove the automatically generated resolv.conf file:

   sudo rm /etc/resolv.conf

3. Create a new resolv.conf file:

   sudo nano /etc/resolv.conf

   Add these external DNS servers and save the file:

   nameserver 1.1.1.1
   nameserver 8.8.8.8

4. Create an additional file to keep the DNS setting permanent:

   sudo nano /etc/wsl.conf

   Add this network setting and save the file:

   [network]
   generateResolvConf = false

5. Restart WSL:

   wsl --shutdown

   The WSL instance now uses the alternate DNS settings. Verify the settings with this command:

   cat /etc/resolv.conf

Additional resources

• Microsoft WSL troubleshooting
• Microsoft WSL configuration