carbajgu Tracker

Two user-id's and one email, please fix

carbajgu — Tue, 09 Mar 2021 19:18:10 GMT

Hi all,

I opened this case and it is already solved. Nevertheless i have no idea how to mark it as solved (and close it).

I log in this community with my only email, but somehow, my email has two user-id:

6uillerm0

communities.vmware.com/t5/user/viewprofilepage/user-id/5295360

carbajgu

communities.vmware.com/t5/user/viewprofilepage/user-id/5448971

Does anyone knows how to mark this as solved and closed? or to help me how to log in as the first user and... close it?

Re: After sleep w10 host, can not ping guests (vmware workstation pro 15.5 & 16.0)

carbajgu — Wed, 10 Feb 2021 14:02:53 GMT

Hello Matten,

No workaround needed, just uninstall/install the last version of ncap that is used by wireshark. URL was shared lines above.

This case should be closed, since it was already solved.

Re: After sleep w10 host, can not ping guests (vmware workstation pro 15.5 & 16.0)

carbajgu — Mon, 11 Jan 2021 16:52:36 GMT

Hello Guys,

This npcap issue is tracked in this thread: https://github.com/nmap/npcap/issues/106

They said npcap 0.9989 does work as expected, i downloaded it from: https://nmap.org/npcap/dist/

I confirm, I can have wireshark/npcap coliving with vmware, no workaround required.

Nevertheless, i do not know the improvements that the current version of npcap has... (from 0.9989 to 1.0000 included in wireshark).

I did not attempt to install 1.10 since the issue thread is still not closed.(opened in 19 Apr 2020)

We have to pay attention of this thread if there are news, but i can live with 0.9989.

Re: After sleep w10 host, can not ping guests (vmware workstation pro 15.5 & 16.0)

carbajgu — Thu, 31 Dec 2020 15:10:06 GMT

Hello DAVISTONE, hello all!

I appreciate a lot the information you gave us. I can confirm the problem is not longer bothering me.

Just uninstalled: Wireshark 3.4.0 64-bit / Npcap and after my computer slept/woke up my connection still works.

The only problem will be that... i eventually need to work with wireshark/npcap. Do you suggest an alternative for wireshark/ncap?

Thanks for the chrismas gift and HAPPY NEW YEAR!

Best regards.

Re: After sleep w10 host, can not ping guests (vmware workstation pro 15.5 & 16.0)

carbajgu — Fri, 11 Dec 2020 17:40:22 GMT

Hello Fendywoo,

I tried with no luck. I am sharing the change done just in case i confused something.

I was not sure about my physical network port, I took my Ethernet connection from the list (this is the way i am currently connected)

After update this configuration, I suspended and resumed my host. The issue was still there.

Thanks / BR

Re: After sleep w10 host, can not ping guests (vmware workstation pro 15.5 & 16.0)

carbajgu — Mon, 07 Dec 2020 14:45:30 GMT

Hello Yanw,

From Win10 "Network Connections" I updated "VMware Network Adapter VMnet8" as requested (check before and after screenshots attached).

Besides, since VMware VNE was still considering vm8 as the old subnet, i also updated these values (check after2 screenshot attached) New SubnetIP is 192.168.142.0. (Internally in NAT Settings it set Gateway IP as 192.168.142.2)

After this changes, i started a centos7 with dhcp and check the new IP assigned. Through a putty connection in win10, i connected as expected.

I proceeded to sleep win10, after wake up. Nevertheless, the issue showed up again.

I will restore the VNE backup so, i will can connect to my VMS (that has statics IPs). Any test you want to try let me know, i will perform it as soon as possible.

This is the ipconfig/all for vmnet8, after sleep and the issue showed up.

Ethernet adapter VMware Network Adapter VMnet8:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet8
Physical Address. . . . . . . . . : 00-50-56-C0-00-08
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::1484:f4f4:18dd:8704%11(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.142.1(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 1207980118
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-26-C5-92-99-00-68-EB-3A-BC-53
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled

Re: After sleep w10 host, can not ping guests (vmware workstation pro 15.5 & 16.0)

carbajgu — Fri, 04 Dec 2020 15:50:31 GMT

Hello again,

In my case, IPAddress in VMnet8 does not change.

Check files zipped/attached:

1 After turned my computer on, notice, this time there were no issue.

2. Stop working after sleep/wake up event.

3. Fixed with workaround by restarting only vmnet8. Nevertheless, the configuration that changes is not vmnet8 but vmnet1

Workaround, AS ADMIN:
C:\WINDOWS\system32>netsh interface set interface "VMware Network Adapter VMnet8" disable
C:\WINDOWS\system32>netsh interface set interface "VMware Network Adapter VMnet8" enable

Regards

Re: After sleep w10 host, can not ping guests (vmware workstation pro 15.5 & 16.0)

carbajgu — Fri, 04 Dec 2020 14:18:53 GMT

Hello Yanw,

Win version:

Microsoft Windows [Version 10.0.18362.1016]

Vmware ws:

VMware® Workstation 16 Pro

16.1.0 build-17198959

HW:

HP EliteBook 840 G6

Tell me if you need more information, thanks for your time

Regards

Re: After sleep w10 host, can not ping guests (vmware workstation pro 15.5)

carbajgu — Thu, 12 Nov 2020 21:10:31 GMT

Hello Alexey!

Appreciate a lot your workaround! it works!

Guys, this workaround means that after my computer starts or wakes up and my VMs keep isolated, It is not required to close all of them, reconfigured networks in VNE and start VMs again.

As Alexey said, just disable/enable these network adapters works.

It helps me a lot, thank you Alexey!

(I am 6uillerm0, i have no idea how this platform create a second profile with the same email. Your post was not notified to my mail that is why i did not notice online)