Troubleshooting WSL2 behind a Corporate Proxy on Windows Server 2022 (VM) - No Internet Access

Troubleshooting WSL 2 Behind Corporate Proxy on Windows Server 2022 (VM) – No Internet Access

Microsoft's Windows Subsystem for Linux (WSL) is a valuable tool for developers and system administrators. However, when running WSL 2 on a Windows Server 2022 Datacenter VM that connects to the internet via a corporate proxy, you might encounter issues accessing the internet from the WSL 2 environment. This article aims to help you identify and resolve such issues.

Context and Key Concepts

Before diving into the solutions, let's review the key concepts related to this problem:

• Windows Subsystem for Linux (WSL) – a compatibility layer for running Linux binaries natively on Windows
• WSL 2 – an updated architecture for WSL based on a real Linux kernel
• Windows Server 2022 Datacenter – the server edition of the Windows Server 2022 operating system
• Virtual Machine (VM) – an abstraction of a computer that runs its own operating system
• Corporate Proxy – an intermediate server separating the user from the internet, often used for security and access control purposes

Issue Description

After installing WSL 2 on a Windows Server 2022 Datacenter VM, connecting to the internet through a corporate proxy, you might face issues accessing the internet from WSL 2. Here is an example scenario:

System Details:

• Windows Server 2022 Datacenter (VM)
• WSL 2 installed and configured
• Corporate Proxy for internet access

Problem: Although the host machine (Windows Server 2022 Datacenter VM) can connect to the internet, the WSL 2 environment cannot.

Solution

To solve this problem, you can follow these steps:

1. Ensure the corporate proxy is correctly set up on the Windows Server 2022 Datacenter VM. This typically involves modifying the system's environment variables.

   To do this, press Win + X and choose "System" from the menu. Then click on "Advanced system settings" on the right-hand side. Navigate to the "Advanced" tab, and click the "Environment Variables" button. In the "System variables" section, look for the "HTTP_PROXY" and "HTTPS_PROXY" variables. If they aren't present, you'll need to create them, providing the correct corporate proxy URL and port (e.g., "http://your-corporate-proxy:8080").

2. Verify the WSL 2 distribution's network settings.

   Open a command prompt and run the following command to enter the WSL 2 environment:

   wsl

   Verify that the distribution can connect to the internet using the following command:

   ping -c 4 8.8.8.8

   If the command fails, you might need to update the WSL 2 distribution's network settings according to Microsoft documentation.

• Make sure the corpo ```