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
LVL 1
snoopaloopAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

bas2754Commented:
First off can you ping 10.1.1.1 (default gw for your nat network)?

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?
Cliff GaliherCommented:
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.
snoopaloopAuthor Commented:
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
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

Cliff GaliherCommented:
As I said, the gateway should be .2. Have you tried that?

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
snoopaloopAuthor Commented:
Yes, i've attached a screenshot of my ip configurations
labip3.JPG
Cliff GaliherCommented:
Try setting everything back to dynamic and the  checking connectivity. You may have other things going on. Walk before running and all that.
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
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.
snoopaloopAuthor Commented:
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.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.