Windows Server 2008 r2 DNS, DHCP help

[pasqo83]

Hey, Im new to this subject. Just a quick heads up, Im doing a Microsoft course which is starting in 2 weeks, trying to get into this field. I have 10 years experience in fixing peoples computers, building computers, troubleshooting etc... but never did networking or buisness IT until now.

ISSUE

Im trying to create a virtual PC to learn win server 2008 r2 and active directory etc....

I need to create a static IP address so I can connect computers to my domain serveR. I need to setup a DNS & DHCP.

I have a virgin modem connected to my wireless router, that is connected to my PC.

Do I need to create a static IP on my wireless router so that when I create a static IP in my Virtual PC, other computers will find the domain server (when I go to connect them) or can I just do it direct from my Virtual PC?

I am having trouble getting the DNS & DHCP to actually work so that it releases private static IP to new computers.

Any help from the Gurus please. I will be at your service.

Thanks

 

[Speed Daemon]

For a variety of reasons I assign static IP addresses to most of the hosts on my home network. What I've learned to do is set my "router" (I hate that term since nobody uses them for routing) to offer DHCP leases for less than the entire subnet.

Most home and "small business" Internet gateway "routers" are preset to use one of the 192.168.*.* non-routable subnets, which gives a total of 254 available IP addresses. What I do is reserve the first half, from 192.168.*.2 to 192.168.*.127, and a few IP addresses near the end (192.168.*.251-192.168.*.254) for static IP. I do this by setting the DHCP server range from 192.168.*.128 to 192.168.*.250.

For as long as I can remember, it's been traditional to reserve a block of IP addresses at the beginning and end of a subnet for routers, bridges or other networking equipment. You'll see why as you learn more about good practices in large managed networks. For now you can trust that it's a Good Thing.

Another tradition has been to put the servers down low in the range of IP addresses. The biggest benefit of doing it this way is that old-timers are likely to have long-standing networks arranged this way, and it makes it easy to guess the IP address of a host that you can't find by name when there's a problem with DNS and/or WINS.

Here's an example of how my home network is arranged:

Network: 192.168.1.0
Netmask: 255.255.255.0
Broadcast: 192.168.1.255
Gateway1: 192.168.1.1
Gateway2: 192.168.1.2

What's up with the two gateways? A well-designed business network will have one or more alternate paths to the Internet. If one path fails, the router(s) for the alternate path(s) assume the default gateway address automatically (if they're configured that way). Since you're learning the business way, you should be prepared for stuff like that.

I reserve easy to remember IP blocks for various host types:

192.168.0.10 is my printer. (In the workplace, many printers are Ethernet connected.)

192.168.1.11-19 is reserved for servers (file, print etc.)

192.168.1.21-29 is reserved for desktops.

192.168.1.31-39 is reserved for virtual machines running on the desktops.

192.168.1.41-49 is for more VMs...and so on.

192.168.1.91-99 is reserved for my TV, TiVos and other media devices.

192.168.1.128-250 are DHCP-assigned addresses that is used by new machines before I've configured a static IP address for them, and for my wirelessly connected devices.

192.168.1.251-254 is reserved by tradition. My Slingboxes take these addresses without asking, so it was good that I reserved that space!

-----

The above is only an example. You can assign static IP addresses and DHCP ranges that suit you. When you set up a local DNS server, you'll probably find times when it's really helpful to know (more or less) the IP address of a host when you can't reach it by name. Being able to ping an address, or a small number of IP addresses to verify that a host is up saves time.

I've seen some Internet gateway "routers" that allow you to use DHCP to assign fixed IP addresses using DHCP. This is not the same as configuring a true static IP address! For your purposes you'll want to have an IP block that doesn't get DHCP assignments, and therefore can be used to configure your machines with a static IP address on.

Good luck!

 

[SUroot]

How are you actually hosting this virtual machine? Firstly you would do well to ensure the VM Guest Network interface is NAT'd not bridged.

Once you have done this, boot up the server. 2008 R2 is like Win 7, so go to the network icon in the sys tray, right Click > Open network and sharing centre > Change Adapter settings > double click the adapter >properties > Highlight IP V4 > Properties and set the IP here

Restart

You can also (depending on your router) allocate the address permanently. Its not a problem if you have set the static on the server, but if the server is off, the router could easily give the ip out to another device, so best to reserve it.

Also, make sure this domain controller is only Active Directory, DNS and DHCP. Do not promote it to handle any other roles. If you need other roles, commission other servers.


Edit > Don't forget you'll need to turn DHCP off on the router too, otherwise you'll be getting IP Addresses assigned by the router. Really for testing this, you want wired devices on a switch, isolated from the router.

 

[pasqo83]

Thanks both of you, I am still new to the world of IP and sub-nets, although I have done alot on hardware and software support, I have never touched networking or learnt IP'S so this is all very foreign to me but I am starting to have a better understanding.

SU Root - you have helped me out big time, it was really easy to understand that. I am easier to work by being shown and I know what I am doing after. I often struggle reading books as although it is good, I learn better visually (on the job) so your explanation has helped me massively

I am on track now and configued - wooo hooo