Can't connect to WSL with VPN/disabled ipv6

• VSCode Version: 1.5.1.1
• Local OS Version: Windows 10
• Remote OS Version: WSL2/Ubuntu 18
• Remote Extension/Connection Type: WSL

Similar to this issue https://github.com/microsoft/vscode-remote-release/issues/1611, but not completely fixed. The fallback ::1 doesn't work because ipv6 is disabled, either because of the VPN or because of Windows settings.

At least I think that's whats going on.

Here I believe is the relevant log section

[2020-11-16 01:50:53.480] IP Address: 192.168.25.110
[2020-11-16 01:50:53.480] Extension host agent listening on 41405
[2020-11-16 01:50:53.480] 
[2020-11-16 01:50:53.480] 
[2020-11-16 01:50:53.480] [17:50:52] Extension host agent started.
[2020-11-16 01:50:53.485] Pinging 192.168.25.110:41405...
[2020-11-16 01:50:53.489] 192.168.25.110:41405 no response
[2020-11-16 01:50:53.490] WSL resolver response: ::1:41405
[2020-11-16 01:50:53.490] To debug connection issues, open a local browser on http://[::1]:41405/version

Steps to Reproduce:

1. Start up VPN with disabled ipv6
2. Open a new remote window

Does this issue occur when you try this locally?: Yes
Does this issue occur when you try this locally and all extensions are disabled?: Yes

Start with the connection logs and the reproduction steps involving a VPN with IPv6 disabled, then compare the behavior with issue 1611. Reproduce the WSL connection failure and trace how the resolver falls back to ::1; done means a remote WSL window connects successfully in this environment.