#52 VMware workstation: one Network card, two IPs, bridged connection

Reading Time: 2 minutes

Recently I purchased two VPS (Virtual Private Servers). One with Windows 2008 R2, the other one with FreeBSD. After a month,  I’ve decided to combine them since both of these servers are my test servers.

First, I’ve purchased another public IP for the Windows server and then I made sure that I can ping both IPs. Then, I installed VMware Workstation on the Windows server and then installed FreeBSD as a VM. Then I already had a problem. I was able to ping the Windows box, but not the BSD VM.

This was my configuration for the network for the BSD VM.


As you can see, I am using a Bridged connection. Bridged network connection means that my VM is using the same NIC adapter as the Windows box. Since the Windows box is already trunked in the back end to accept two IPs in two different VLANs, I was hoping that once I assign the second IP to the BSD box, I should be able to ping it. But I couldn’t. If I assign the second IP to the Windows NIC adapter, I was able to ping both IPs.


Do ipconfig /all on the Windows box and find the MAC address. In my case it is 52:54:00…etc.


In VMware Workstation click on the Advanced button (see the first screenshot), and copy and paste the MAC from Windows.


The idea is to have the same MAC for both Windows and the FreeBSD VM. Once you reboot the FreeBSD box, you’ll have the same MAC and be able to ping both IPs (one assigned to Windows, the other to FreeBSD). If you want to test before reboot, do:

ifconfig em0 ether 52:54:00:B6:B5:F8

Where em0 is my NIC name under FreeBSD. Your name may vary.

NOTE: The same scenario can be applied to any other OS running as a VM. Just make sure that the MACs are the same.

#34 Upgrading VMware Tools fails on Windows Server 2008 with the message “Error 1316. A network error occured while attempting to read from the file C:\Windows\Installer\VMware Tools.msi”
#50 vSphere: Upgrade from 5.0 to 5.1
#49 Install vCenter 5.0
There are currently no comments.