1 Reply Latest reply on May 22, 2019 11:26 AM by kks42

    Cannot ping Windows 10 VM when logged out of vSphere console

    kks42 Lurker

      I have a very strange issue. As long as I am logged into a VM via the vSphere console, I can ping and RDP into the Windows 10 VM. As soon as I log off the VM in the vSphere console, I can no longer ping or access the VM (via RDP).

       

      vSphere Web Client: Version 6.0.0 Build 6855238

       

      Below is the result of VMware ticket 19200089805:

      +++++++

      ** Please do not change the subject line of this email if you wish to respond. **

      Hello Paul,

      Thank you for using VMware products and services! It was my pleasure to assist you with this issue. I hope that you were delighted with the service I provided to you.

      As we have agreed, your support request is ready to be archived. I will keep it active for 24 hours in case any additional questions should arise. If I do not hear from you the case will automatically be archived at that time. If the issue should reoccur within 21 days, please contact me and I will be happy to re-activate the case and continue working with you.

      I have provided you with a summary of the key points below for your records.

      Summary:

      =========

      Issue:

      Issue:- Unable to connect to VM, network issues

      =========

      Resolution:

      Summary of our session:
      > VM in question USVADVCL4009 (x.x.x.x) and currently not pingable
      > VM is utilzing a standard switch port group VLAN 40
      > Unable to ping VM USVADVCL4003 (x.x.x.x) that is in the same host and standard switch port group. Note, VM USVADVCL4003 (x.x.x.x) is pingable from customer's computer (x.x.x.x)
      > Perform packet capture to VM USVADVCL4009 from customer's computer (x.x.x.x) via ping test. Observe that packet is making it to the VM and sending packet information to guest O/S. Packet capture results:
      - Network information for VM USVADVCL4009: 33554486 (switchport); xx:xx:xx:xx:xx:xx (mac address); vmnic0 (uplink VM is utilzing which was obtained via esxtop command)
      - pktcap-uw --uplink vmnic0 --capture UplinkRcvKernel --mac xx:xx:xx:xx:xx:xx -o - |tcpdump-uw -enr - (packet entering host network physical adapter)

      15:01:29.118385 xx:xx:xx:xx:xx:xx > xx:xx:xx:xx:xx:xx, ethertype IPv4 (0x0800), length 74: x.x.x.x) > x.x.x.x): ICMP echo request, id 1, seq 55838, length 40
      15:01:34.112595 xx:xx:xx:xx:xx:xx > xx:xx:xx:xx:xx:xx, ethertype IPv4 (0x0800), length 74 x.x.x.x) > x.x.x.x): ICMP echo request, id 1, seq 55844, length 40
      15:01:39.112777 xx:xx:xx:xx:xx:xx > xx:xx:xx:xx:xx:xx, ethertype IPv4 (0x0800), length 74 x.x.x.x) > x.x.x.x): ICMP echo request, id 1, seq 55851, length 40

      - pktcap-uw --uplink vmnic0 --capture PortInput --mac 00:50:56:85:fa:04 -o - |tcpdump-uw -enr - (sending packet into virtual switch)

      15:02:19.956146 xx:xx:xx:xx:xx:xx > xx:xx:xx:xx:xx:xx, ethertype IPv4 (0x0800), length 74: x.x.x.x)> x.x.x.x): ICMP echo request, id 1, seq 55897, length 40
      15:02:24.628820 xx:xx:xx:xx:xx:xx > xx:xx:xx:xx:xx:xx, ethertype IPv4 (0x0800), length 74: x.x.x.x)> x.x.x.x): ICMP echo request, id 1, seq 55903, length 40
      15:02:29.628078 xx:xx:xx:xx:xx:xx > xx:xx:xx:xx:xx:xx, ethertype IPv4 (0x0800), length 74: x.x.x.x)> x.x.x.x): ICMP echo request, id 1, seq 55910, length 40
      15:02:34.624925 xx:xx:xx:xx:xx:xx > xx:xx:xx:xx:xx:xx, ethertype IPv4 (0x0800), length 74: x.x.x.x)> x.x.x.x): ICMP echo request, id 1, seq 55916, length 40

      - pktcap-uw --switchport 33554486 --capture PortOutput --mac xx:xx:xx:xx:xx:xx -o - |tcpdump-uw -enr - (packet leaving virtual switch)

      15:03:46.912209 xx:xx:xx:xx:xx:xx > xx:xx:xx:xx:xx:xx, ethertype IPv4 (0x0800), length 74: x.x.x.x) > x.x.x.x): ICMP echo request, id 1, seq 55996, length 40
      15:03:51.622106 xx:xx:xx:xx:xx:xx > xx:xx:xx:xx:xx:xx, ethertype IPv4 (0x0800), length 74: x.x.x.x) > x.x.x.x): ICMP echo request, id 1, seq 56003, length 40
      15:03:56.628046 xx:xx:xx:xx:xx:xx > xx:xx:xx:xx:xx:xx, ethertype IPv4 (0x0800), length 74: x.x.x.x) > x.x.x.x): ICMP echo request, id 1, seq 56009, length 40

      - pktcap-uw --switchport 33554486 --capture VnicRx --mac 00:50:56:85:fa:04 -o - |tcpdump-uw -enr - (present packet payload to guest O/S)

      15:04:35.211099 xx:xx:xx:xx:xx:xx > xx:xx:xx:xx:xx:xx ethertype IPv4 (0x0800), length 74: x.x.x.x) > x.x.x.x): ICMP echo request, id 1, seq 56053, length 40
      15:04:40.126703 xx:xx:xx:xx:xx:xx > xx:xx:xx:xx:xx:xx, ethertype IPv4 (0x0800), length 74: x.x.x.x) > x.x.x.x): ICMP echo request, id 1, seq 56060, length 40
      15:04:45.127221 xx:xx:xx:xx:xx:xx > xx:xx:xx:xx:xx:xx, ethertype IPv4 (0x0800), length 74: x.x.x.x) > x.x.x.x): ICMP echo request, id 1, seq 56066, length 40
      15:04:50.121324 xx:xx:xx:xx:xx:xx > xx:xx:xx:xx:xx:xx, ethertype IPv4 (0x0800), length 74: 1x.x.x.x) > x.x.x.x): ICMP echo request, id 1, seq 56073, length 40

      > Appears that issue is with the guest O/S

      =========

      +++++++

       

        • 1. Re: Cannot ping Windows 10 VM when logged out of vSphere console
          kks42 Lurker

          Replying to my own post, hoping this will help someone else with the same issue. It was the Cisco AnyConnect Secure Mobility Client included in our Image. I had to uninstall Cisco AnyConnect Diagnostics and Reporting Tool, Cisco AnyConnect Posture Module and Cisco AnyConnect Secure Mobility Client. Now the VM is pingable (and RDP works) when logged out of the VM.