Virtual Network Editor is a VMware network configuration program used to configure the network settings of multiple VMs. In this article, we shall discuss steps to resolve “Network Cable Unplugged: Fix VMware “Warning – Multiple default gateways are intended to provide redundancy to a single network”. Please see how to View RDP Configuration Settings: Connect automatically on an RDP session, how to Test Network Connection to Windows Admin Center Gateway, and System check found some issues during MBAM encryption: Fail, the Power cable must be connected.
In subsequent articles, I will show you how to configure Bridged, Network Address Translation (NAT), and Host-Only networks in VMware Workstation. The short guide will address both error 1 and error 2 below.
Error 1: Windows Warning – Multiple default gateways
The image below is the error prompted when you wish to configure TCP/IP to reflect the right network parameters due to the following issue “Active Directory Domain Controller (AD DS) for this domain could not be contacted“.
When you change network providers, you are likely to encounter this issue when you wish to reassign a new IP addresses to virtual machines (VMs). As you can see, this is just a warning message that can result in the second error below or the Windows Yellow Triangle Network icon.
You may be interested in these: Secure FTP Login Issue: NAT Router Configuration Needed for Passive Mode and Port Forwarding, and how to create and delete a DHCP reservation in Windows Server 2019.
Error 2: The reason for this error “Network Cable Unplugged”
Also, you can see under the network connection properties, that the Network cable is unplugged as shown below.
This error is because the VM does not have a valid network connection
Therefore, follow the steps employed here to resolve these VMware Workstation issues.
VMware Network Settings
Note: When you install VMware Workstation on your PC, the virtual network card configuration programs are also installed. And by default, some virtual network adapters are added to the Network Connections section of your PC. These adapters are called VMnet. There are 3 options for VMware Workstation network settings. They are as follows below.
- Bridged: The virtual machine connects to the real network using the host’s network adapter of the host computer.
- Network Address Translation (NAT): NAT converts the IP addresses on the LAN to a single global IP address to connect the PCs on the network to the Internet.
- Host-Only: This virtual network enables VMs to communicate with themselves
Solution 1 Using Bridged Connection to solve VMware Multiple Default Gateways
In order to ensure that there is only one active default gateway for our network settings. We will have to reconfigure the VMware Workstation network settings in the bridge mode. In this article, I will also show you how to use NAT to resolve this issue.
Open the virtual network editor in the VMware workstation as shown below.
Note: Administrator privileges are required to modify network configuration.
Now, switch from the VMnet to the Bridged connection as shown below. As you can see in the vNetwork Editor, the VMnet0 is in Bridged mode. VMnet0 will work between your physical computer and the virtual PC.
Lastly, you will also have to change this on the VM guest level as shown below. Select the VM and right-click on it. Select settings as shown.
Under the hardware menu, select the Network Adapter. On the right pane, select Bridged: Connected directly to the physical network. This will ensure that the VM is directly connected to the physical network
Please see How to Set Up a WatchGuard XTM and Access WSM, Cyclic Redundancy: Resolve Data Error on Inaccessible Hard Drive, and How to fix “The process cannot access the file because another process has locked a portion of the file”.
Solution 2 Using Network Address Translation (NAT) to Fix VMware Multiple Default Gateways
The second option I will be showing you today is how to resolve this issue via NAT. When a Virtual Machine is created in VMware Workstation, the settings of the virtual machine are automatically set to NAT. VMs configured with NAT obtain their IP addresses from a virtual DHCP server managed by VMware Workstation.
When you move the VM to a new network, it might not be able to obtain an IP address from the new DHCP server, and when it does, this might result in issues in your network as mentioned above. Since the NAT configuration has changed, there is a need to reconfigure NAT settings. Please follow the steps below to achieve this.
Open the virtual network editor in the VMware workstation as shown below.
Restore the default NAT Settings
Click on the “restore default” button at the bottom left of the editor since we wish to reconfigure NAT.
Note: The VMs must be shut down or powered off. Otherwise the error “All Virtual network settings cannot be restored while virtual machines are powered on. Power off all virtual machines first” will be prompted.
This will uninstall and reinstall the network components. I did not have to re-enter the IP ranges. I am okay with the defaults.
Note: If you followed the first steps above, please double-check on the guest OS Network Adapter as shown below
With the right networking settings in place, you would have resolved the following errors “Network cable Unplugged”, and “VMware “Warning – Multiple default gateways are intended to provide redundancy to a single network”
If you run into the following “Windows Yellow Triangle icon in the systray of the LAN Network” when using NAT. Then, you should reset your network.
Please perform a network Reset as shown below. Otherwise, kindly ensure you have paid attention to all the configuration steps I have discussed above.
Conclusion on Network cable Unplugged: Fix VMware Multiple default gateways
Since I prefer the Bridged option and I want my VMs to obtain IP addresses in the address range of my local network, I will revert these settings to the first option. In this way, the VMs can get DHCP-assigned IPs (automatic IP addresses). Also, see how to install Windows Server 2022 on VMware Workstation.
FAQ on VMware Workstation Virtual Network
Bridged networking in VMware Workstation allows a virtual machine to share the host computer’s physical network connection. It essentially connects the virtual machine directly to the external network, as if it were another device on your network. You should use bridged networking when you want the virtual machine to have its IP address on your local network, making it accessible to other devices and services.
Network Address Translation (NAT) in VMware Workstation provides your virtual machine with network access through your host’s IP address. It allows your VM to communicate with external networks but isolated from your local network. On the other hand, Host-only networking creates a private network shared only between the host and its virtual machines. Use NAT if you want internet access, and Host-Only if you need an isolated network for your VMs.
To recap, In VMware Workstation, you can configure virtual networking through the “Edit” menu and then select “Virtual Network Editor.” From there, you can create and manage virtual networks, set up custom network configurations, and specify which physical network adapter to bridge with.
I hope you found this article useful on “Network cable Unplugged: Fix VMware Multiple default gateways are intended to provide redundancy to a single network (such as an intranet or the Internet). They will not function properly when the gateways are on two separate disjoint networks (such as one on your intranet and one on the Internet)”. Please let me know in the comment section if you have any questions.