topic Re: Unable to Connect to and from VM in VMware Workstation Pro Discussions

Unable to Connect to and from VM

jbwinkel — Tue, 13 Dec 2022 09:50:22 GMT

Dear Users

Since a few weeks i have a problem with connecting to and from my VM's. First i thought has to do with my Windows 11 migration. but now i'm back on windows 10 but the problem still exists. First what is my Configuration:

VMware workstation 16.2.4 (No i can't upgrade to 17 right now)
Network NAT (Brideged mode work but i prefer NAT network)
Windows 10 local
Windows server 2019 on vm
I have access to internet!

I try to give as much as possible information so:

First image of my (NAT) network settings within VMwareVMware NAT network settings

My VM networks on the host:

C:\Users\USER>ipconfig Windows IP Configuration ... Ethernet adapter VMware Network Adapter VMnet1: Connection-specific DNS Suffix . : Link-local IPv6 Address . . . . . : fe80::bc15:bd55:fa1b:e75f%4 IPv4 Address. . . . . . . . . . . : 192.168.130.1 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : Ethernet adapter VMware Network Adapter VMnet8: Connection-specific DNS Suffix . : Link-local IPv6 Address . . . . . : fe80::ddc6:4bc6:cce8:7763%22 IPv4 Address. . . . . . . . . . . : 192.168.122.1 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . :

My networks on the VM:

C:\Users\Administrator>ipconfig Windows IP Configuration Ethernet adapter Ethernet0: Connection-specific DNS Suffix . : localdomain Link-local IPv6 Address . . . . . : fe80::4db6:3441:cda6:dd6%14 IPv4 Address. . . . . . . . . . . : 192.168.122.130 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.122.2

If i ping from host to VM:

C:\Users\USER>ping 192.168.122.130 Pinging 192.168.122.130 with 32 bytes of data: General failure. General failure. General failure. General failure. Ping statistics for 192.168.122.130: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

If i ping from VM to host

C:\Users\Administrator>ping 192.168.122.1 Pinging 192.168.122.1 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 192.168.122.1: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), C:\Users\Administrator>ping 192.168.122.2 Pinging 192.168.122.2 with 32 bytes of data: Reply from 192.168.122.2: bytes=32 time<1ms TTL=128 Reply from 192.168.122.2: bytes=32 time<1ms TTL=128 Reply from 192.168.122.2: bytes=32 time<1ms TTL=128 Reply from 192.168.122.2: bytes=32 time<1ms TTL=128 Ping statistics for 192.168.122.2: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms

So I can not connect to host, but i can connect to the gateway.

If i use Host only network:

C:\Users\Administrator>ping 192.168.130.1 Pinging 192.168.130.1 with 32 bytes of data: Reply from 192.168.130.1: bytes=32 time<1ms TTL=128 Reply from 192.168.130.1: bytes=32 time<1ms TTL=128 Reply from 192.168.130.1: bytes=32 time=1ms TTL=128 Reply from 192.168.130.1: bytes=32 time=1ms TTL=128 Ping statistics for 192.168.130.1: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 1ms, Average = 0ms

This workout well too.

And now the most strange part... If i let Nmap do a ping scan i get the following result(s):

Starting Nmap 7.93 ( https://nmap.org ) at 2022-12-13 10:35 W. Europe Standard Time Nmap scan report for domain-on.vm.com (192.168.122.130) Host is up (0.00s latency). MAC Address: 00:0C:29:36:7F:40 (VMware) Nmap scan report for 192.168.122.254 Host is up (0.00044s latency). MAC Address: 00:50:56:FB:5C:A3 (VMware) Nmap scan report for 192.168.122.1 Host is up. Nmap done: 256 IP addresses (3 hosts up) scanned in 37.87 seconds

So all Nmap detects all the (expected) IP-addresses. I'm unable to ping the same addresses and i'm unable to go to the VM's domain.

Basically i don't have any clue anymore where to find a solution.

Re: Unable to Connect to and from VM

jbwinkel — Fri, 30 Dec 2022 17:40:39 GMT

Small update:

Currently i use the VM in Bridged mode. For a big part of the work i need to do with the VM it work out well. But that doesn't mean i don't have any issues...

A few issues i noticed so far while using bridged mode:

- Last time i wrote:

@jbwinkel wrote:
If i use Host only network:
ping results here (somehow i can't quote code...)
This workout well too.

Today i noticed that when I'm in bridged mode the host only connection don't work.

- Also i had issue that i was unable to ping while Nmap was able to ping the VM

@jbwinkel wrote:
And now the most strange part... If i let Nmap do a ping scan i get the following result(s):
Nmap results here
So all Nmap detects all the (expected) IP-addresses. I'm unable to ping the same addresses and i'm unable to go to the VM's domain.

Basically i don't have any clue anymore where to find a solution.

Now i have basically the reversed issue.

I can't ping from VM to host but Nmap is able to ping:

C:\Users\Administrator>ping 192.168.1.33 Pinging 192.168.1.33 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 192.168.1.33: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

and

Starting Nmap 7.93 ( https://nmap.org ) at 2022-12-30 17:01 GMT Nmap scan report for router-name (192.168.1.1) Host is up (0.0020s latency). MAC Address: 28:FF:3E:20:C5:01 (router-brand) Nmap scan report for 192.168.1.2 Host is up (0.065s latency). MAC Address: 48:A9:1C:CF:86:64 (PC-brand1) Nmap scan report for 192.168.1.31 Host is up (0.037s latency). MAC Address: 88:66:5A:23:2D:FC (PC-brand2) Nmap scan report for 192.168.1.33 (192.168.1.33) Host is up (0.0027s latency). MAC Address: 38:7A:0E:A3:4D:C8 (PC-brand3) Nmap scan report for VM-name (192.168.1.43) Host is up. Nmap done: 256 IP addresses (5 hosts up) scanned in 2.15 seconds

So basically still no clue what and why i have these issues... Every tip or idea is welcome

Re: Unable to Connect to and from VM

louyo — Sat, 31 Dec 2022 00:53:07 GMT

Why does your gateway show as blank? Is your adapter set for static or DHCP?

Re: Unable to Connect to and from VM

jbwinkel — Wed, 04 Jan 2023 09:28:42 GMT

I have checked by a coworker and he don't have a gateway either on the VM adapters. But compared to me everything works fine!

I made printscreens from my VMnet and VMnet8 networkadaptersetttings.

Re: Unable to Connect to and from VM

jbwinkel — Fri, 24 Mar 2023 07:53:26 GMT

After weeks using Bridged mode instead of NAT mode. The problem disappeared equally fast as it appears. No clue what is changed but it works again