VMware Cloud Community
loomalk
Contributor
Contributor

NO INTERNET ACCESS for my first VM

Hi,


im novice in ESX 5 but i would like to create a private network where i could practice about Windows Server. so i have loan a server.

I would like to create a VM with 2 ethernet card ( one with E1000 and second VMXNET3 , the first to gain acces to internet and the second will communicate with future vm )

i have installed WSERVER 2012 64bit and VMTOOLS on it.

the only network activated settings :

169.254.145.116

255.255.255.0

gateway with ipv6

169.254.28.26

255.255.255.0

gateway with ipv6

I dont know how to gain internet acces from the E1000 interface network ( i would like to set a static ip 192.168.1.25 )

could you tell me how to do it ?

thanks

Reply
0 Kudos
8 Replies
Nick_Andreev
Expert
Expert

The physical host will need a network uplink, which is connected to wherever your internet is. Then you will need to create a vSwitch and connect this uplink to it. And the last step is to create a port group on the vSwitch and connect your E1000 adapter to the port group in VM settings.

This is a basic workflow of how network is set up in vSphere.

---
If you found my answers helpful please consider marking them as helpful or correct.
VCIX-DCV, VCIX-NV, VCAP-CMA | vExpert '16, '17, '18
Blog: http://niktips.wordpress.com | Twitter: @nick_andreev_au
Reply
0 Kudos
fugrat1
Enthusiast
Enthusiast

You will also need to set a valid IP address, Subnet Mask, Default Gateway and DNS Servers on the NIC within Windows unless you have a DHCP server that can provide these settings

Reply
0 Kudos
loomalk
Contributor
Contributor

Thank for you replies.

my physical host have connection to internet but its about network config on my VM.

this is the config of my esx :

the network uplink is connected : vmnic0

ip adress : 91.121.XX.XX

submask : 255.255.255.0

gateway : 91.121.XX.XX

dns server : 213.186.33.99

vmkernel0 : 91.121.91.XX

i have created a portgroup, a vswitch link to vmnic0 ( the column range ip is blank in network adapter tab's on vswitch properties )

and i dont know which network configure i should apply on my VM !!

i have set E1000 adapter but i have seen my network adapter said E1000e ? whats the difference ?

i was thought the dhcp will work et built in into port group when its linked to network adapter but the ip grabbed doesnt work.

for remark, i have purchase a loan of a server on www.ovh.fr !!!

do you have an idea or help me to get a valid ip ?

Reply
0 Kudos
fugrat1
Enthusiast
Enthusiast

OK, it looks like your ESXi Server has a public IP address.  You will need some kind of networking device to perform NAT if you want to use a private IP address internally on your server, maybe look into pfsense.  You can then configure this to supply DHCP addreses to your client machines.  What you will need to do is connect your pfsense public interface to the vswitch connected to the physical NIC that is connected to the public network, and create another vSwitch for your private traffic, and connect the pfsense private interface to this vswitch.  I'm afraid I don't know pfsense but can try to help

Reply
0 Kudos
fugrat1
Enthusiast
Enthusiast

This may help with configuring, it is for VMware Workstation but you can use the same instructions for ESXi

Home Lab with pfSense & VMware Workstation | OutsideSys

Reply
0 Kudos
loomalk
Contributor
Contributor

Thank you fugrat1, its useful !

is it normal to not be able to create new network adapter ? ( i just have one NIC vmnic0 )

because, if i understand well, i would need to have 2 NIC ( one for LAN and one for the WAN ( pfsense )  ???

Reply
0 Kudos
fugrat1
Enthusiast
Enthusiast

You can create any number of Virtual NICs on the ESXi Server, on the pfsense box you can just add another vNIC and have it connected to your new vSwitch that would be for internal traffic with no physical NICs attached.  Basically you will have an external vSwitch that is connected to the Physical NIC and the external vNIC of the pfsense would connect to that, then there will be another vSwitch for internal traffic that will contain the other vNIC from the pfsense and all your VMs will connect to this.

Reply
0 Kudos
fugrat1
Enthusiast
Enthusiast

This diagram may explain better what I am getting at

Untitled.jpg

Reply
0 Kudos