Server 2008 lab

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

I am setting myself up a basic server 2008 r2 lab with 3 vm's created, all of them are set in the VM properties to the same internal network name "vm_int".

The 3 VMs are:
server 2008r2 (ad-ds, dns) static ip: 192.168.0.10, subnet: 255.255.255.0, default gateway: 192.168.0.1, primary dns: 192.168.0.10 (as the dns is on this server).
dhcp-2008r2 (dhcp) static ip: 192.168.0.11, subnet: 255.255.255, default gateway: 192.168.0.1, primary dns: 192.168.0.10
win7pro - this is just a standard windows client which should grab an IP from the DHCP VM.

Server2008r2 can see that it's on the domain: "wigston.leicester.com" however is not communicating to the other machines, and no dhcp clients are being handed out, which I presume is due to dhcp2008r2 not seeing the wigston.leicester.com domain, and therefore cannot hand out any DHCP addresses to clients.

The sod's law of all this is that I had it working perfectly before Christmas, but I lost all my data and so am having to start from scratch, and as is the way, it's not working.

- - - Updated - - -

update: windows 7 client now sees its on wigston.leicester.com and is picking up an address from DHCP.

so just need to figure out why dhcp-2008r2 is not seeing wigston.leicester.com, as the network adapter shows "unidentified network".

- - - Updated - - -

further update:
a reboot seems to have fixed everything.

arghh... time for a beer!

 

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

You mean you didn't try turning it off and turning it on again? ... what has the IT World come to..

 

And to think that a reboot solved all the issues... Windows eh!

 

I would never have thought that a reboot would ever solve anything

Just as a side note, I had been trying by rebuilding VMs in VMWare Player for days and would never work, but then I tried it in Virtual Box and worked fine as above. I will import in to VMWare Player and continue from there with my 70-680 studies from the Don Poulton book.

 

Shadowwebs, I'm just curious why you prefer VMWare Player over Virtual Box??

 

Out of interest what did the event logs say??

As far as VMware Player is concerned I find it just 'works', added to that it tends to be the product that has the most readily available VM's available for it (VMware MarketPlace as well as other locations that make OVF\OVA as well as VMDK and VMX files available). There are also tools out there that allow you to convert the odd VHD into VMDK's as well should you ever find the need.

 

Virtual PC by Microsoft was the first one I used, then I moved over to virtual box, but yes I have recently moved to VMware player as my overall preference now.

oh, and just set them all up on VMware player and is working fine, all I can think is that I was typing something repeatedly wrong when it wasn't working, and wasn't the fact of what the virtualisation software was.

 

just out of curiosity...what's you lab setup spec? Mine drastically needs updating.

 

lab setup:
VMware player
3 x VMs
- Windows Server 2008 r2 x64 (dhcp) - 2gb ram
- Windows Server 2008 r2 x64 (ad-ds, dns) - 2gb ram
- Windows 7 x64 - 1gb ram

each of the VMs are on an internal network named 'vm_net'

within the VMs I have got the network setup as below

Static IPs:
192.168.0.10 (ad-ds, dns VM)
192.168.0.11 (dhcp)
255.255.255.0 (subnet mask)
192.168.0.1 (default gateway)
127.0.0.1 (primary dns server)
Windows 7 client picks up dynamic IP from the DHCP server.

 

Out of curiosity why did you go for DHCP running on a different server? It's not exactly a taxing role and the DC could have handled it just fine (especially in such a small lab environment).

Additionally you would probably have been better to configure forwarding on the DNS server and leave all of the servers pointing to the DC for their DNS, that way you're not using a local host for DNS (which if you configure each client to use 127.0.0.1 as DNS will only mean that they will try to use themselves as the DNS resolver).

 

Simon,

I had set the primary dns to 192.168.0.10 as this is the same as the ad-ds, dns server, however on occasion I find that it has reverted, by itself, to 127.0.0.1

I am not sure why this is happening.

I am in agreement with you to have DHCP on the same server as the DC, I only put it on separate one as a test of setting up separately.

 

Thanks

 

just to update, I have removed the separate dhcp lab, and included dhcp as a role on 192.168.0.10 lab

 

Is this in relation to your 70-680 studies?

 

yes bb88 it is in relation to my 70-680 studies