Open v-dantch opened 4 years ago
Hi @v-dantch,
Thanks for your work as usual. Is this the same issue that we resolved last night before I left the office?
In any case, I think that this is probably being caused by deleting and reusing VM names. The .ssh config isn't cleared when you delete a VM, so the entry becomes stale. There should be a warning indicating that the Host or HostName already exists.
This bug also can be reproduced on the new build 20200414.1. We test this scenario using different regions, but changing the regions can't fix this issue.
This issue also reproduce on the latest build 20200629.1.
Verified on the latest build 20200819.1, this issue still reproduces for now. I will continue to track this issue.
@v-mengwe Could you check your network security group policies? It's possible that your account automatically denies outgoing ports.
You can see on this screenshot that the priority of the deny rule is higher than the SSH rule, which was preventing me from connecting to the VM.
@nturinski I checked the vm's network security group policies, the "Action" is indeed "Deny", and I manually changed the status "Deny" to "Allow", which can fix this issue. But we can connect to the same vm without changing the above "Action" on the Mac OS. We are confused the different behaviors on Windows and Mac. Could you help to clarify this?
OS: Windows Build Version: 20200226.22
Repro Steps:
Expect: Succeed to connect the host.
Actual: [Unstable] Fail to connect the host with error "The process tried to write to a nonexistent pipe".