How to Configure Custom Specific Virtual Network in VMware!

In this article, we’ll examine step by step how to configure the Virtual Network connection. Specifically, this is one of the VMware Workstation network settings.

Configuring Custom Specific Virtual Network in VMware

How to Configure a Specific Virtual Network in VMware Workstation/Player

When you install the VMware virtualization program, it creates VMnet connections. For example, these connections support Bridged, NAT, and Host-Only modes on the Virtual Network Editor.

Once you create a new virtual machine on VMware, check the Virtual Network Editor first. After that, select Bridged, NAT, or Host-Only from the network adapter’s settings. You can find these options for your virtual machine.

This VMware virtual network configuration is the same as other VMnet network settings. Still, in some cases, you can configure Custom Networking. This helps you add a virtual machine to a 3rd party program. Moreover, it helps you avoid complexity.

For example, you created a new VMnet5 on the Network Editor. Then you configured it as Bridged. Therefore, you should configure the virtual machine network configuration as VMnet5.

How to Use Custom-Specific Networking on VMware Workstation 12/14/15

The first default configuration on the Network Editor is as follows. VMware Workstation automatically configures VMnet0, VMnet1, and VMnet8.

In this window, VMware Workstation configures VMnet1 as Host-Only.

Virtual Network Editor

Follow the steps below to configure the custom-specific network on VMware Workstation.

Step 1

Name the two machines you installed on VMware: Client1 and Client2. Then click Network Adapter. This lets you configure the Client1 machine’s network card configuration.

When you select the Custom Specific Network option, you will see the VMnets you created. Specifically, these appear as shown below. Select VMnet1 for the Client1 machine.

Add Virtual Machine to VMnet1

Step 2

Select VMnet1 for the Client2 machine.

VMnet1 Configuration

Step 3

After configuring the Custom Specific Network, test the network connection. Then ping Client2 from the Client1 machine.

If Ping fails, disable Windows Firewall on both VMs.

Testing Network Connection

Step 4

Likewise, check the network connection by pinging Client1 from the Client2 machine.

Pinging from Client2 to Client1

Step 5

Since you configured Client1 and Client2 on the same VMnet1, both virtual machines communicate. Moreover, they can connect with each other. However, if you configured the Client2 VM on another VMnet6/Host-Only, the VMs would not connect.

You can think of the VMnet/Host-Only setting you created. This setting acts as a Switch on the Virtual Network Editor. Therefore, you can create advanced network topologies by configuring a Custom Network on VMware. For example, in GNS3, you can connect virtual machines on two different networks. Use a Cisco Router for this.

VMware Network Mastery: 6 Questions About Custom Virtual Networks

Why should I use a custom network when VMware already has standard modes like Bridged, NAT, and Host-Only?

Flexibility is the key here. The default modes are ready-made templates. Custom networks give you unlimited freedom.

Let’s say you want to create 3 different virtual networks. You can assign different IP ranges to each one. You can even isolate them completely from each other.

When working with simulators like GNS3, a custom network is essential. It’s the only way to mimic real-world topologies.

How do I create a new network other than VMnet0, VMnet1, and VMnet8 in the Virtual Network Editor?

It’s very easy, let’s do it together. Open the Virtual Network Editor. Click the ‘Add Network’ button.

Select an unused VMnet number from the list. For example, VMnet2, VMnet3, or VMnet5. Then click ‘OK’.

Now your new network is ready. You can make it Host-Only or Bridged. You can even create a completely isolated private network. It’s entirely up to you.

I connected two virtual machines to the same custom network, but they can’t ping each other. What should I do?

Don’t panic, this is a situation I encounter quite often. The first thing to check is the Windows Firewall.

Yes, temporarily disable the firewall. Then try pinging again. This usually solves the problem.

If it still doesn’t work, check the IP addresses. They must be on the same subnet. For example, if one is 192.168.1.10, the other should be 192.168.1.20. The subnet masks must also match.

What is the difference between a custom network and Host-Only? Aren’t they the same thing?

You might think they are the same, right? But the truth is different. Host-Only only communicates with the host machine. It is closed to the outside world.

A custom network is much more flexible. It becomes whatever you want it to be. You can configure it as Bridged, NAT, or Host-Only.

For example, you can take VMnet5 and make it Bridged. Or create a completely isolated private network. Host-Only offers only a single option.

How do virtual machines on different VMnets communicate with each other?

By default, they cannot communicate directly. Each VMnet acts like its own switch. They exist in separate worlds.

But there is a solution. You can use Windows’ Routing and Remote Access feature. Or you can set up a virtual router.

The most professional way: make a Linux virtual machine act as a router. Connect it to two different VMnets. Then let it route the traffic. This is a true network engineering topic.

Can I automate custom network configuration from the command line?

Absolutely yes! VMware has you covered. There is the ‘vmnetcfg.exe’ tool, but the real power lies in the ‘vmware-vnetlib’ commands.

For example, you can create a new VMnet with ‘vmware-vnetlib –create’. You can make it Host-Only with ‘–set-hostonly’.

I always tell my clients: if you have more than 10 virtual machines, write a script. Don’t waste time on manual configuration every time. Your time is too valuable.

Conclusion

In this article, we discussed step-by-step instructions. Specifically, these instructions show how to use Specific Network on VMware. With VMware Specific Networking, you can assign IP addresses. For example, you can assign them from different IP blocks to virtual machines.

How to Configure Custom Specific Virtual Network in VMware