+You could try a static
route on the 2nd vmkernel port if you know the consultants source IP,
but I would avoid putting a vmkernel port on the Internet+
192.168.1.x Network is behind a firewall with a Point to Point VPN tunnel to the consultants office. So would I just add the routers internal IP of 192.168.1.254? I'm a newbie on CLI any help on how to add it?
+Instead, you could
create a vswitch with no physical NIC port, then add a NIC from the VM
to it as well as a vmkernel IP so that the host can be managed on that
isolated network only from the VM.+
If the VM isn't ON and functioning then he couldn't manage it. Or am I mssing something? Case in point, he needs to load server 2008. I'd like him to do that. I've already mounted the ISO for 2008 in his VM config.
+I would also review the
permissions granted to the consultant for the VM. I'm not saying they
would be malicious, but if they can edit the vNIC settings for the VM
then they could place the 2nd vNIC onto your LAN.+
I've logged in as him, verified that he cannot edit his own VM, nor can he see any others. He also can't modify any host settings. I'd have to assume other people are having similair situations with shared hosted VM's. The security is very granular under ESX I was very supprised to see the level of control you can grant.