Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

DNS problems on WSL with Cisco VPN #5391

Closed
lego963 opened this issue Apr 17, 2020 · 2 comments
Closed

DNS problems on WSL with Cisco VPN #5391

lego963 opened this issue Apr 17, 2020 · 2 comments
Labels
Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Product-WSL Issue that should probably go to Microsoft/WSL Resolution-External For issues that are outside this codebase

Comments

@lego963
Copy link

lego963 commented Apr 17, 2020 •
edited
Loading

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
@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Apr 17, 2020
@zadjii-msft
Copy link
Member

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 microsoft/WSL#4698, which already looks pretty similar.

@zadjii-msft zadjii-msft added Product-WSL Issue that should probably go to Microsoft/WSL Resolution-External For issues that are outside this codebase labels Apr 17, 2020
@lego963
Copy link
Author

lego963 commented Apr 17, 2020

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Product-WSL Issue that should probably go to Microsoft/WSL Resolution-External For issues that are outside this codebase
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@lego963 @zadjii-msft