Accepted Solutions
You'll need to go to "Edit -> Virtual Network Manager" and "Add Network" and make it a Bridged type (you'll need Admin privilege). It should look something like this but you'll need to specify the device in your system.
The problem you'll have is when you restart your host OS, Widows will select the best available network interface -and that will most likely be your wired connection. There is a way to set the interface metric but, I haven't gotten around to that. When you shut down the system, you could disable the wired interface and only turn it back on once you're ready to start the VM. Windows might start to automatically use the wired interface once it's turned on so, keep an eye on that. If that happens, you'll need to tweak the interface metric.
Ray C
You'll need to go to "Edit -> Virtual Network Manager" and "Add Network" and make it a Bridged type (you'll need Admin privilege). It should look something like this but you'll need to specify the device in your system.
The problem you'll have is when you restart your host OS, Widows will select the best available network interface -and that will most likely be your wired connection. There is a way to set the interface metric but, I haven't gotten around to that. When you shut down the system, you could disable the wired interface and only turn it back on once you're ready to start the VM. Windows might start to automatically use the wired interface once it's turned on so, keep an eye on that. If that happens, you'll need to tweak the interface metric.
Ray C
Quick update... To force Windows to use a particular interface, change the metrics like what's shown below.
Find this window in your host OS and tweak the metric. Widows will automatically use the interface with the lowest metric. Put the interface dedicated for your host at metric 1 and the VM-dedicated interface to 2. When you boot-up the host, it will not steal the dedicated interface. When you start VMware and subsequently the guest, it will forcibly grab the interface you assigned in the virtual network editor.
Also, for the TCP/IP settings of the interface dedicated to the guest, you can prevent dual homing by leaving the interface enabled and turning off both IPV6 and IPV4 and, leave the interface administratively enabled. When the guest OS is started, it will get assigned an IP address (assuming DHCP is turned on in the guest settings) by the local router or DHCP server. Doing this will prevent the interface from being assigned an IP address first when the host comes up and a second IP address when the VM guest comes up. This ultimately keeps the host more secure with fewer exposed IP addresses.
Ray C