So in my nested lab in Workstation 10, I've set all the hosts to use NAT in the virtual network editor to NAT to my host machine network, which has worked completely fine. I've set up the DC to perform DNS, and I'm able to hit google.com from my vCenter server in the nested environment, and am able to ping my hosts from my host PC.
However, when trying to edit the management network settings directly on the ESXi host by pressing F2 after it finishes booting, it will not take the command when working with it from team viewer. I loaded a page on my DC and hit F5 to test if it was getting the key input, and it did refresh the page so the function key is being sent, but for some reason the ESXi host will not accept any function key but does respond if I hit enter (goes from shaded window to lit up indicating it got the key input).
??:
It also actually dropped my wireless router earlier to the point I had to unplug it for 10 minutes to get it back online when trying to send the F2 command to the ESXi host, and that behavior stopped after I disabled the Microsoft Loopback adapter I have bridging my GNS3 environment to my host network, and nothing else seems to be causing this weirdness except the ESXi host.
Tonight is the first time I've tried to access the ESXi directly within team viewer, otherwise everything has mingled perfectly, running GNS3 / Nested Lab concurrently through team viewer and working with both while at a remote location. The ESXi host responds normally to key strokes on the host machine, and I have no connecting to either ESXi hosts using vSphere client.
I cannot figure this out and it's driving me up the wall, any ideas on what could possibly be causing this, or where to even start troubleshooting such an issue?
