ESXI v7U3 VM W2016 Network Access Problem

[ksdst1]

Hello.  I have a test W2016 VM on a Dell Optiplex 7010 ESXi host with one physical NIC.  The VM did have internet connection with the vNIC configured w/ a static IP, dns, wins, in the same VLAN.  I had to move the PC to another room w/ a different port that "should" be configured the same way/same vlan, and it at least has network access via a remote browser or ssh no problem using its existing IP.  

After the move, the vNIC E1000e (also tried VMXNET3) shows "No network access" for IPv4&6 but shows packets sent/receive.  I've tried to manually set speed/duplex, different static IPs in the VLAN range, get a "there is a conflict IP" when I configure it with the same IP as the ESXi host IP.  I can ping the VMs own IP and the PC ESXi host's IP but not the gtwy, dns or wins.  I've looked through several tutorials about setting up VM networking/switches/port groups, etc., but nothing grabs me as to what might be the problem.

The only change I made was to rename the VM by adding 2016 to its original server01 name.  Help w/ suggestions on how to troubleshoot would be greatly appreciated.

[ggathagan]

I am having a very similar problem, but I'm wondering if the problem is with Windows.

I've been trying to create additional Windows VMs and cannot get any combination to work on VMware or ProxMox ( another virtualization platform).
I've tried:
Starting from scratch with the same Windows 10 ISO file I've used for years.
Starting from scratch with a Windows 11 ISO file.
Cloning a working VM.
Creating a template from that same VM and using that to create a new VM.
Using a 2008R2 template to create a new VM.

In all cases, the VMs are being creating on the switches and subnet that are used by all of my servers.
This subnet does not have DHCP support, so all attempts deal with static IP addresses.

With the starting-from-scratch attempts, I can look at the status window of the virtual ethernet adapter and see traffic.
There's an older WD DX4000 NAS on that subnet and I can connect to its web interface by what appears to be an IPv6 address.
This is also true of the VMs created from templates

With the various cloning methods, I can access the VM up until the point where I change the IP address. Name change does not have an impact.

The problem does not occur when I create a VM on VMware Workstation Pro

I have none of these problems with a VM running any distro of Linux you care to mention:
Alma, CentOS, Debian, OpenSUSE, SLES, Ubuntu

All of this is on vCenter Server 8 and with site licenses for the various flavors of Windows.
I will be trying with various Windows Server versions today.

[ksdst1]

Thanks for your input and experience you are having.  Mine should be very straight forward.  I have an ESXi host w/ one physical NIC where the VM W2016 server is using the default vSwitch0, in the default VM Network port group, with the same vVlan ID 0 as the Management Network where vmk0 is configured with an IP in the physical wall-port's assigned VLAN and the VM W2016 server also has an IP (dns, wins) in that same VLAN IP range.  I can access the ESXi host and work with it using its IP in a web browser.  I can see send/receive traffic on the W2016 configured E1000e NIC, can open a cmd window and ping its own IP, the IP of the ESXi host, itself, but not the IP range's GTWY, or any other physical network host or resource.