Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I am new to using ESXi and vSphere, I currently have ESXi 5 running with a win 2008 server VM on it. I am trying to set it up so that the VM can access the internet by setting up NAT. I cannot find the option in vSphere and all of the documentation I have found doesn't offer much help. I don't really understand the virtual switches and port groups and things like that.

I know in vmWare it was as simple as bridging the virtual adapter to the physical one.

Sorry if this is too in depth of a question.

EDIT: Adding more information. I currently only have the one vm on the server. In the future I might be adding more to it and I would like all VM based traffic to look like its coming from the ESXi ip address (through NAT).

share|improve this question
    
Are you trying to put your VMware ESXi host actually onto the Internet unprotected? I would let the firewall do the NAT instead. –  Mei Feb 16 '12 at 18:40
    
I am not too sure what you mean. I am trying to set it up so that the windows VM generates traffic that looks like it is coming from the ESXi's ip address. –  amazinghorse24 Feb 16 '12 at 18:44
    
If your ESXi server is protected from the Internet by a firewall, then you don't need to make the Windows VM act that way; VMware creates its own interfaces for each of the VMs separately. You don't need to NAT the way you are suggesting. However, if you are trying to put this host on the Internet without protection, then you are asking for trouble: you should put ESXi behind a firewall. –  Mei Feb 16 '12 at 18:47
2  
That's not how it works. –  MDMarra Feb 16 '12 at 18:48
    
Put another way: why do you want to NAT the Windows VM? It will work just fine on any network without NAT. –  Mei Feb 16 '12 at 18:48
show 3 more comments

1 Answer

up vote 3 down vote accepted

The IP of the management interface has nothing to do with the IPs of the VMs on it. The fact that, in your setup, the vmkernel port may also be on the same physical port as the vmnetwork doesn't mean anything. Basically, you can't do what you think you can do.

share|improve this answer
    
Thanks, I guess i'll just have to wait until I have our IP address list to figure out which ones aren't in use. –  amazinghorse24 Feb 16 '12 at 18:58
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.