We use virtual machines to run our automation software that we use to support production machinery. We have some machines that came into the facility with static IP addresses in the 169.254.200.* subnet, which is used by Windows to assign itself an address after DHCP fails.
Most of our machines have addresses in either the 192.168.0.* subnet or the 10.130.249.* subnet. For those machines, we can use the NAT adapter in the VM and connect with no difficulty. The ones in the 169.254.200.* subnet, however, won't route through the NAT adapter. Instead, we have to use a Bridged adapter. If we only had a few VMs, we could work around that, but we have 6 total host computers, each with 3-5 VMs. That's a lot of IP addresses to allocate in each subnet, and we don't have enough free for that.
Ideally, we would just move the machines from the APIPA range to the 192.168.0.* range, but the machine builder is unwilling to assist and can't provide us with a list of devices within each machine that would be affected. The risk to production is too great to experiment.
Is there a way to let the VM see the devices on the 169.254.200.* subnet through the NAT adapter? The host PC can see them fine and so can the VM through a bridged adapter.
We are running VMWare Workstation Player 12.5.2 build-4638234. The host and guest PCs are all running Windows 7 Professional SP1, 64-bit. We have a couple VMs on each PC that are running Windows XP for legacy software, but they don't need to see these machines.
