DHCP Enabled: One Windows Server 2019 and Another Windows 10 Pro VM - No Internet Access

Both Windows Server 2019 and Windows 10 Pro virtual machines fail to access the internet despite having DHCP enabled in VMware Workstation. This issue typically stems from incorrect virtual network adapter configurations, misconfigured DNS settings within Active Directory, or host firewall restrictions blocking outbound traffic. The following guide provides a systematic approach to diagnosing and resolving these connectivity failures by verifying network adapters, IP allocation, and DNS resolution paths.

Verify Virtual Network Adapter Configuration

The most common cause of internet loss in virtualized environments is an improperly configured virtual network adapter. In VMware Workstation, you must ensure that both the Windows Server 2019 and Windows 10 Pro VMs are connected to a network type that provides NAT (Network Address Translation) or Bridged connectivity. NAT is generally recommended for isolated lab environments where you want the VMs to share the host's IP address while maintaining security. Open the VMware Workstation interface and navigate to the virtual machine settings. Select the network adapter and check the connection status. If the adapter is set to "Host-Only," it will not have internet access because this mode isolates the VM from the external network. Switch the setting to "NAT" or "Bridged." After changing the setting, restart the virtual machine to allow the guest operating system to re-initialize the network stack. This simple change often resolves immediate connectivity issues without requiring deeper configuration changes.

Check IP Address Allocation and Subnet Mask

Once the network adapter is correctly configured, verify that the VMs are receiving valid IP addresses via DHCP. Open Command Prompt on both the server and the client and run ipconfig /all. Look for the IPv4 address, subnet mask, default gateway, and DNS servers. If the IPv4 address starts with 169.254.x.x, the VM has failed to obtain an IP from the DHCP server and is using a Link-Local address. This indicates a communication failure between the VM and the DHCP service. If the IP address is valid but the default gateway is missing or incorrect, check the VMware virtual network editor. Go to Edit > Virtual Network Editor in the main VMware menu. Ensure that the NAT subnet matches the expected range for your environment. Verify that the DHCP service is enabled for the selected virtual network. If you are using a custom subnet, ensure that the gateway IP falls within that subnet range. Incorrect subnet masks can also prevent routing, so confirm that the mask (typically 255.255.255.0) aligns with your network design.

Validate DNS Settings in Active Directory

Since Active Directory is installed, DNS plays a critical role in name resolution. Misconfigured DNS settings can make it appear that there is no internet access, even if basic ping commands to IP addresses work. On the Windows Server 2019 domain controller, open the Network Connections panel and right-click the active adapter. Select Properties and then double-click Internet Protocol Version 4 (TCP/IPv4). Ensure that the preferred DNS server points to the local IP address of the Windows Server 2019 machine. On the Windows 10 Pro client, perform the same check. The client should point to the domain controller for DNS resolution. If the client is pointing to an external DNS server like 8.8.8.8, it may bypass internal AD records, causing authentication and connectivity issues. To test if DNS is the root cause, try pinging an external IP address like 8.8.8.8 from both VMs. If the ping succeeds but browsing fails, the issue is likely DNS-related. Flush the DNS cache on both machines using ipconfig /flushdns and retry.

Inspect Host Firewall and Routing Rules

The host computer running VMware Workstation may have firewall rules that block traffic from virtual network interfaces. Check the Windows Defender Firewall on the host machine. Ensure that inbound and outbound rules allow traffic for the VMware virtual adapters. Sometimes, third-party antivirus software or corporate firewalls interfere with virtual network drivers. Temporarily disable the host firewall to test if connectivity is restored. If it works, create specific exceptions for VMware processes rather than leaving the firewall disabled. Additionally, verify that the host itself has internet access. If the host cannot reach the internet, the VMs certainly will not. Check the host's network connection and ensure it is not behind a restrictive proxy. If the host uses a proxy, configure the VMs to use the same proxy settings in their TCP/IP properties. This step is crucial in enterprise environments where direct internet access is restricted.

Review VMware NAT Service Status

For NAT-based networks, the VMware NAT Service must be running on the host machine. Open the Services console (services.msc) on the host and locate "VMware NAT Service." Ensure its status is "Running" and the startup type is "Automatic." If the service is stopped, start it manually and observe if the VMs gain connectivity. Restarting the VMware networking services can also reset any stuck connections. Navigate to Edit > Virtual Network Editor, click "Restore Defaults," and apply the changes. This action resets all virtual network configurations to their factory state, which often resolves complex configuration drift issues.

Check for IP Conflicts and Lease Renewal

Occasionally, IP conflicts arise if multiple devices claim the same address. Use arp -a in the command prompt to view the ARP table and identify duplicate entries. If you suspect a conflict, release and renew the IP address on the VMs by running ipconfig /release followed by ipconfig /renew. This forces the DHCP client to request a fresh lease from the server. Monitor the DHCP server logs on Windows Server 2019 to see if the renewal requests are being processed correctly. If the server rejects the requests, check the DHCP scope options and exclusions to ensure the requested IP is available.

Frequently Asked Questions

Why does my VM show a 169.254 IP address?

A 169.254 address indicates that the VM could not contact a DHCP server. This usually happens when the virtual network adapter is disconnected, the VMware DHCP service is stopped, or the network type is set to Host-Only instead of NAT or Bridged.

Can I use Bridged mode instead of NAT?

Yes, Bridged mode connects the VM directly to the physical network, giving it its own IP address on the LAN. However, this requires that your physical router assigns IPs dynamically and that your network allows new devices to connect, which may not be permitted in secure corporate environments.

How do I reset VMware virtual network settings?

You can reset the settings by opening the Virtual Network Editor in VMware Workstation, clicking the "Restore Defaults" button, and applying the changes. This process reinstalls the virtual adapters and resets the NAT and DHCP configurations to their original state.

What if ping works but web browsing fails?

This symptom strongly suggests a DNS resolution problem. Verify that the VMs are pointing to the correct DNS server, which should be the Windows Server 2019 domain controller. Clear the DNS cache with ipconfig /flushdns and ensure that the DNS forwarder settings on the server are configured to resolve external names.

Does disabling the host firewall help?

Temporarily disabling the host firewall can help determine if it is blocking virtual network traffic. If connectivity returns, you should create specific inbound and outbound rules for VMware executables rather than leaving the firewall permanently disabled, as this poses a security risk.