I followed all steps in the following article but cannot connect to the network/internet. Please assist.
In order to be able to help, please provide more details.
André
Thanks for the follow up!
Host OS is Windows 10 x64. Here is ipconfig info:
Ethernet adapter VMware Network Adapter VMnet1:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet1
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.145.1(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter VMware Network Adapter VMnet8:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet8
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.135.1(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Enabled
Wireless LAN adapter Wi-Fi:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom 802.11ac Network Adapter
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.0.130(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Monday, February 27, 2023 11:59:31 AM
Lease Expires . . . . . . . . . . : Monday, February 27, 2023 12:45:47 PM
Default Gateway . . . . . . . . . : 192.168.0.182
DHCP Server . . . . . . . . . . . : 192.168.0.182
DNS Servers . . . . . . . . . . . : 1.1.1.1
1.0.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled
Guest OS is Windows 10 x64 on NAT mode. Here is the ipconfig info:
Windows IP Configuration
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Ethernet0:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) 82574L Gigabit Network Connection
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IPv4 Address. . : 169.254.7.9(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Enabled
According to the guest's output, it doesn't receive a DHCP address.
It should get one from the 192.168.135.0/24 NAT subnet (one between .128 and .254).
Please check whether the "VMware DHCP Service" is running on the host, and if the DHCP service is enabled for the NAT network in the Virtual Network Editor.
ANdré
VMware DHCP Service is running on the host and as per the attached screenshot DHCP is enabled as well. Any other suggestions?
Interesting. Would it be possible to start e.g. a Live-Linux image to see whether that receives a valid IP lease from the NAT range?
André
I could download Red Hat and give that a shot or maybe I can re-deploy another Windows OS and see what happens. I installed a VPN client on there and completely uninstalled it but my suspicion is it corrupted something in the network config as connections were choppy at times when using it.
The VPN client might indeed be related.
However, an option that you may try is to open the Virtual Network Editor, and use the "Restore Defaults" button to reset the virtual network settings. Note that this may result different subnets for Host-Only, and NAT. If you need the current ones, make note of them before you run the restore.
To test the network settings, you may use e.g. the gParted Life ISO (https://master.dl.sourceforge.net/project/gparted/gparted-live-stable/1.5.0-1/gparted-live-1.5.0-1-a.... Simply create a new VM (Debian 6 - 64 Bit), attach the ISO image to the virtual CD-ROM drive, and boot it. You can then run "Network config" from the gParted desktop, and see how DHCP tries to get a lease.
And only to rule this out: Did you double-check that your Windows VM has "Connected" / "Connect at power on" checked in its virtual network adapter settings?
André
