Problem - VMware - Windows 2008 R2 - Internet connection

Greatness · 26 Apr 2012

Hi guys.

Im very new to VMware, so the answer might be super easy or I might need to give you more info.

I use VMware Workstation 8.0.1.

I have installed 2 windows 2008 R2 machines in VMware.

Server 1: DHCP, DNS, AD
Server 2: DNS, AD - Neither is installed on server 2 yet.

Server 1: IP: 192.168.100.5 - DNS: 8.8.8.8
Server 2: IP: 192.168.100.6 - DNS: 8.8.8.8

I used 8.8.8.8(google DNS) for the AD, so it was autoset as DNS in the server role for DNS.
I have 8.8.8.8 set manually aswell in the LAN for the NIC.

The Network connection settings I use in VMware are:

Bridged: Connected directly to the physical network
and I have the box checked for "Replicate physical network connection state"

I tried running dcpromo on server 2 and add it to an existing forrest(server 1). But I get an error, an DNS error, cant connect to the existing forrest.

And to the second and more important problem. I cant seem to connect to the internet on either machine.
What settings should I use? Am I doing something wrong with the DNS or the settings in vmware?

Im very thankfull for all help.

Regards
Greatness

pparks1 · 26 Apr 2012

Whenever you set up a Windows Server as a domain controller, you want to point the DNS on that server to itself. You can set a forwarder within that DNS server, to forward to 8.8.8.8 if you wish.

On your second server, you want to set it's DNS server to be the first server. From there, dcpromo should work.

The "replicate physical connection state" is used to auto renew an IP address when you move from one wired or wireless network to another. This is really for mobile computers, where the host may go from one network to another.

can you ping from your Server 1 to something on the internet, for example, 8.8.8.8? This will help tell if you are actually getting out, and not having having a name resolution problem.

Greatness · 26 Apr 2012

Thank you for your reply.

So I have changed the DNS records to the server 1 IP(192.168.100.5) and I set that IP as DNS for server 2 and yes, now I can add server 2 as a domain controller. Thank you.

For the second problem. I set 8.8.8.8 as a forwarder, just to get a server I know works as a backup.
But I still cant access the internet from either of the servers.

I removed the "replicate" option.

I should have "bridge" for the servers right? then I can add just "host only" for the clients and they recive IP from server 1(the dhcp server)

Thanks again for your help.

EDIT:

I pinged 8.8.8.8 and I get "Destination host unreachable" as a reply.

EDIT 2:

Just installed a Win 7 client in Vmware, but I choose "NAT" as a connection type. And that machine could connect to the internet. But when I put the servers on "NAT" aswell they still cant access the internet and the DHCP dont give an IP to the client =/

Regards
Greatness

pparks1 · 26 Apr 2012

Bridge means that the VM's would get IP's just like any other machine on your network. And that is what I would use. They really should be able to able to get to 8.8.8.8.

I would check to be sure that your Default Gateway is correct with your bridged adapter. Also ensure your subnet mask is correct for your network as well. Sounds like there is just a routing issue on the network preventing you from getting out.

Greatness · 26 Apr 2012

I think you are right.

So, allright.

I want 2 servers:
1 with DNS, DHCP, AD with IP: 192.168.100.5
1 with DNS and AD with IP: 192.168.100.6
I want both servers to be able to reach the internet.

X clients with Win 7 that recives IP from the DHCP and can access the internet aswell

What Network option should I use in VMware?
What Gateway should I put on the servers?

I feel like im missing something, thats why I wrote everything down and asked the 2 questions.

Thanks again for the help mate =)

Regards
Greatness

pparks1 · 26 Apr 2012

What is your actual IP address range on your home network? It's probably something like 192.168.1.x. So, if you want your VM's to run on 192.168.100.x...then you cannot use bridged mode. You would need to use NAT. The issue here would be that VM's can get out to the INternet, but other hosts machines won't get back in.

If your home network is 192.168.100.x...then you can set these VM's to .5 and .6 and you would want bridged. You would set the AD server to itself for DNS and set a forwarder to a real DNS server like 8.8.8.8. Client machines would set their DNS to be your DC's, which would then forward out to 8.8.8.8 for anything not local.

Everything should be able to hit the Internet.

Greatness · 26 Apr 2012

Ah allright.

I have 192.168.0.X as a home network.
So I set the 2 servers to 192.168.0.10 and .11. And used the home network as a gateway.
And I used briged connection type in vmware.

And now I can access the internet

- Thank you..

But what about the clients? What connection type in vmware should they have? so they get DHCP from my vmware server. If I put briged on the client aswell, the client get an IP from the DHCP in my home network(outside the vmware)

Regards
Greatness