Ok, let's verify that network-3 on the host is connected to a properly VLANed physical switch port.
1. enable SSH on ESXi host: Using Tech Support Mode in ESXi 4.1
2. use Putty to SSH to the host, enter root credentials
3. ping gateway on network-1, ping server on network-1, both should return ping times
4. ping server on network-2, like backup-server 192.168.1.22, should be successful
5. ping a known working desktop on network-3
6. ping gateway on network-3, 171.64.Y.1, is this a real physical port? On a router? Switch?
If step 5 & 6 are success and return ping times, the networking on the ESXi host is correct and we have a VM configuration issue. We should clean up ALL old drivers and hardware settings on VM-C that was carried over from the physical box.
1. Log onto VM-C with admin account
2. bring up command-prompt, type in "set devmgr_show_nonpresent_devices=1 <enter>"
3. then "devmgmt.msc <enter>"
4. when the DeviceManager comes up, pull down from menu-bar: View -> Show hidden devices
5. expand each section by clicking the + and inspect the devices listed
6. you'll find a tonne of greyed-out entries that represent the old hardware from Server2 and the physical box you virtualized
7. highlight each greyed-out phantom device and hit DEL key, then click OK to uninstall and remove the old drivers
Most problematic in this case is the old network-drivers from the old box. Windows will still load the drivers on boot and the original IP will still be bound to the old NIC. This can cause problems when you try to assign that same IP to the new E1000 virtual-NIC. Once all the phantom devices have been removed, reboot. During the reboot, verify in VM settings that the E1000 NIC is assigned to network-3 and that both Connect and ConnectAtPowerOn options are checked.
After VM-C reboots, login with admin-account and go to control-panels-> network connections. View -> Details and you should see the following:
status = enabled
device name = Intel(R) PRO/1000 MT Network Connection
type = LAN or High-Speed Internet
name = name of your workgroup or Domain if you have DC on network-3
Now it's just a matter of assigning proper IP and mask for network-3 and VM-C should be on that network.