DNS problems on WSL with Cisco VPN #7457

Closed
opened 2026-01-31 01:04:32 +00:00 by claunia · 2 comments
Owner

Originally created by @lego963 on GitHub (Apr 17, 2020).

Environment

Windows build number: Microsoft Windows [Version 10.0.18363.752]
Windows Terminal version (if applicable): Version: 0.10.781.0

Steps to reproduce

Connect to Cisco AnyConnect and try to ping named service on wsl and cmd
Connect to FortiClient is ok

Expected behavior

image

Actual behavior

image

When we shutdown VPN client it will become ok

Originally created by @lego963 on GitHub (Apr 17, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: Microsoft Windows [Version 10.0.18363.752] Windows Terminal version (if applicable): Version: 0.10.781.0 ``` # Steps to reproduce Connect to Cisco AnyConnect and try to ping named service on `wsl` and `cmd` Connect to FortiClient is ok # Expected behavior ![image](https://user-images.githubusercontent.com/17201690/79552338-8fdef680-80a3-11ea-87e7-d2ef2d60bcfa.png) # Actual behavior ![image](https://user-images.githubusercontent.com/17201690/79552242-6faf3780-80a3-11ea-8070-56e929c67172.png) When we shutdown VPN client it will become ok
claunia added the Product-WSLNeeds-TriageResolution-ExternalNeeds-Tag-Fix labels 2026-01-31 01:04:32 +00:00
Author
Owner

@zadjii-msft commented on GitHub (Apr 17, 2020):

Does the use of the Terminal change the behavior at all here? I'm going to guess not. I'd think that this issue belongs over at microsoft/WSL instead, where they might be able to help debug this.

Just searching "cisco" on that repo I was able to find https://github.com/microsoft/WSL/issues/4698, which already looks pretty similar.

@zadjii-msft commented on GitHub (Apr 17, 2020): Does the use of the Terminal change the behavior at all here? I'm going to guess not. I'd think that this issue belongs over at [microsoft/WSL](https://github.com/microsoft/wsl) instead, where they might be able to help debug this. Just searching "cisco" on that repo I was able to find https://github.com/microsoft/WSL/issues/4698, which already looks pretty similar.
Author
Owner

@lego963 commented on GitHub (Apr 17, 2020):

Sorry, didn't know about WSL repo. Thanks.

@lego963 commented on GitHub (Apr 17, 2020): Sorry, didn't know about WSL repo. Thanks.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#7457