Link to home
Start Free TrialLog in
Avatar of Ben Conner
Ben ConnerFlag for United States of America

asked on

Workstation Pro VM can't see network

Successfully converted a Windows AD from ESXi 7 to Workstation 16 Pro.

Had a couple of glitches requiring updates, etc. but got those taken care of, as well as re-entering the static IP of the nic card.


Problem is it can't see the network.  This machine is on 10.0.0.21/255.255.240.0 and the AD it came from runs fine with that.  


The NIC interface is running in bridge mode.  Pinging the router at 10.0.0.1 returns a timeout.  


arp -a comes back with:

Interface: 10.0.0.21 --- 0x10
  Internet Address      Physical Address      Type
  10.0.15.255           ff-ff-ff-ff-ff-ff     static
  224.0.0.22            01-00-5e-00-00-16     static
  224.0.0.252           01-00-5e-00-00-fc     static


So it really isn't seeing any other IP addresses, including the workstation I'm running it on (10.0.1.101).


Any suggestions?


Thanks!


--Ben

Avatar of Dr. Klahn
Dr. Klahn

More information is needed.  Please post the result of:

ipconfig /all
what IP exists on your LAN?

is the network adapter actually reflected and is it connected?
Avatar of Ben Conner

ASKER

This machine is assigned to 10.0.0.21/255.255.240.0.  I didn't define the entire /8 when I created the lan.   The nic port is powered on and in bridge mode.

Results of the ipconfig command:
Windows IP Configuration

   Host Name . . . . . . . . . . . . : ad1
   Primary Dns Suffix  . . . . . . . : wwi.webworldinc.com
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : wwi.webworldinc.com

Ethernet adapter Local Area Connection 3:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection #2
   Physical Address. . . . . . . . . : 00-0C-29-35-0D-9D
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 10.0.0.21(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.240.0
   Default Gateway . . . . . . . . . : 10.0.0.1
   DNS Servers . . . . . . . . . . . : 8.8.8.8
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{8F6C2AAE-87B9-4C7F-A4BC-F2D1DBE96E04}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 9:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
I only see one physical network adapter in the ipconfig results, but it is described as "Intel(R) PRO/1000 MT Network Connection #2."

a) Are there two physical NICs in the system?
b) Why is the system running in bridge mode?
The configurations a static ip, what do you need the IP to be?
What is the local network?
Media disconnected.

Can you check the network connected at boot?
Have you confirmed that a NON Converted VM, works on this VMware Workstation Host in Bridged Mode, and obtains an IP Address from the LAN via DHCP to confirm, networking is working.

Even creating a new VM quickly, and selecting BOOT from LAN (PXE) should get a DHCP IP Address.
Hm.  Interesting.  Brought up another VM I hadn't used in a good while.  It can't get out either.  Will create one from scratch and see what I can do with it.

--Ben
Threw up a fresh Win 10 copy.  NAT mode works fine on the NIC interface but when I convert it to Bridged mode, it fails.  Couldn't get a DHCP assignment so I gave it a static IP address of 10.0.0.14.

arp -a returns:
C:\Windows\system32>arp -a

Interface: 10.0.0.14 --- 0x6
  Internet Address      Physical Address      Type
  10.0.15.255           ff-ff-ff-ff-ff-ff     static
  224.0.0.22            01-00-5e-00-00-16     static
  224.0.0.251           01-00-5e-00-00-fb     static
  224.0.0.252           01-00-5e-00-00-fc     static
  239.255.255.250       01-00-5e-7f-ff-fa     static
  255.255.255.255       ff-ff-ff-ff-ff-ff     static

ipconfig /all returns
Ethernet adapter Ethernet0:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Intel(R) 82574L Gigabit Network Connection
   Physical Address. . . . . . . . . : 00-0C-29-90-63-ED
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 10.0.0.14(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.240.0
   Default Gateway . . . . . . . . . : 10.0.0.1
   DNS Servers . . . . . . . . . . . : 8.8.8.8
   NetBIOS over Tcpip. . . . . . . . : Enabled
ASKER CERTIFIED SOLUTION
Avatar of Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
LOL.  Will do.  Thanks, Andrew.  Sigh...
I do not think it is an install issue. Uninstall/reinstall often leaves residual items that make the post re-install more tenuous.
If you have an option to use another system all together, follow Andrew's advice install Vmware Workstation on this new system. while the vm is not running, copy the vm's data to the new system, and see if that makes a difference.
First try the new VM as a test to confirm whether the network bridging works.
consider enabling bridging.
delete the network interface. add a new one marked ......
and see whether the new network interface in bridging mode works.
Once confirmed that it works. Copy the VM in question.
Delete/read the network inteface and see if it works in bridging mode.
If it does,  you know what you need to do on the current system (delete the network interface and readd a network interface to the VM) after you turned off the VM on the newly installed VMWARE workstation system.
In this case I R&R Workstation Pro and tried the test Win 10 machine again.  It was able to see the network.  The NIC settings got reset to DHCP, so I set them back to the static address I was testing from and it still worked.

No idea what was causing the grief before, in truth.  But it now works, as does the AD VM.

Thanks to all who participated in this discussion.

--Ben