Setting up Network/VLAN for use with home lab domain
I'm running VMware Workstation 11 in my home lab and have created two Server 2008 r2 boxes. I created a vlan set up for NAT and hoping to configure it to use a private network (10.1.1.0 255.255.255.0). I installed AD DS and promoted the first server 2008 r2 box to be my domain controller and gave it a static IPv4 :
IP 10.1.1.2
Subnet 255.255.255.0
Default Gateway 10.1.1.1
Primary DNS 10.1.1.2
I've set the VMs network adapter to use the vlan for this network (10.1.1.0 - 10.1.1.254) but I am having connectivity issues. I can ping these internal addresses but cannot ping to any external addresses, i.e. google.com or 8.8.8.8 8.8.4.4. I've worked with domain controllers, active directory and servers before but this is the first time I'm trying to set up a new DC and configure a private network/vlan; please help. I've attached screenshots to show my IPv4 configurations and my vlan configuration.
labip.JPG
labip2.JPG
IP 10.1.1.2
Subnet 255.255.255.0
Default Gateway 10.1.1.1
Primary DNS 10.1.1.2
I've set the VMs network adapter to use the vlan for this network (10.1.1.0 - 10.1.1.254) but I am having connectivity issues. I can ping these internal addresses but cannot ping to any external addresses, i.e. google.com or 8.8.8.8 8.8.4.4. I've worked with domain controllers, active directory and servers before but this is the first time I'm trying to set up a new DC and configure a private network/vlan; please help. I've attached screenshots to show my IPv4 configurations and my vlan configuration.
labip.JPG
labip2.JPG
In VMware workstation, .1 is reserved for the host adapter and .2 is used for NAT. So you should set the gateway to .2, not .1, and set the IP address to something higher, like .3. If you are going to use static addresses, I'd also edit the DHCP settings on your virtual network to start at something higher, say .128 for example. You have it starting at .0 (which is not a valid address anyways.)
Finally, don't use the term VLAN to describe a virtual network. Those terms are not interchangeable.
Finally, don't use the term VLAN to describe a virtual network. Those terms are not interchangeable.
ASKER
I've changed the starting IP to 10.1.1.128. Bare with me as I have a beginners understanding of networking. Since this is being used for a lab environment, can you recommend the DC IP and gateway? I tried setting it to 10.1.1.130 but was still having the connectivity issues as before.
iplab2.JPG
iplab2.JPG
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Yes, i've attached a screenshot of my ip configurations
labip3.JPG
labip3.JPG
Try setting everything back to dynamic and the checking connectivity. You may have other things going on. Walk before running and all that.
You have configured VMware Workstations Networking to use these IP Addresses, because they do no look like the default IP Addresses, that Workstation uses, e.g. 192.168.x.x.
ASKER
Thank you, setting the default gateway to 10.1.1.2 and vlan IP range to start at 10.1.1.128 resolved my connectivity issues.
If you can ping between the two servers on the private lan then the likely issue is that your GW ip is not correct. I see on your Vmware config it is set to hand out dhcp to the nat network. Try to set one of the servers to use dhcp temporarily and then run ipconfig from a command prompt and confirm that you have the correct default gw. I think on mine at the office it is something like 10.1.1.28 (if I set the subnet the same as yours). Using Dchp can uou ping out?