Home
Username:
Password:
Microsoft Windows Server 2003 (70-291) Tutorials

Implementing/Managing/Maintaining IP Addressing Cont'd / Authorizing; Client Reservations

Subtitles of the Movie

This module focuses on some other DHCP concerns that we need to take care of before we get down to the business of actually handing out IP addresses. The first is we need to authorize the DHCP server. One thing that Server 2003 domains protect against is the addition of rogue DHCP servers in your network. Because as you saw earlier, DHCP clients aren't picky about which offer they respond to, any DHCP server in the network is a potential threat to the communication of that network because if you get an IP address from the wrong DHCP server and the wrong scope, it can really mess up your ability to communicate on the network. Therefore in order for any domain clients to receive IP addresses from a DHCP server, those DHCP servers must first be authorized in Active Directory. In order for a computer to be authorized as a DHCP server it must either be running the DHCP server service, it must be running on a domain controller or a member server in the domain. We can still implement DHCP on a stand-alone computer or a workgroup computer in other words, but it just won't be able to hand out IP addresses in a domain, in an Active Directory environment. So that's something you need to know. To authorize a DHCP server, open up the DHCP MMC snap-in and you can do this in one of two ways, you can select the server itself and then authorize it. You can also right click on the root level console, the root level of the console, and manage authorize servers and then authorize and then type the name of the DHCP server you want to authorize. So this is how it's done, I'm just going to take this route, right click, authorize and that's it, there's really no magic, really that happens, although you should be able to see it in your manage authorize servers dialog box here, window. So that's step 1. The other thing that you might consider doing is adding a client reservation. When you add a client reservation that client for whom the reservation is configured still gets the benefits of automatic DHCP configuration, but it really effectively has a static IP address. It doesn't have a static IP address but for all intents and purposes, it does because it gets the same one every time. So you can ensure that a particular computer, the boss's computer, a print server always gets the same IP address. That is done by choosing the reservations node and right clicking and choosing new reservation. Again this is explained and as you click on reservation, the reservation process, the purpose is explained in the details pane. Here's what you'll need, reservation name and then the IP address you want to reserve and then here is the part you have to go look up, the MAC address, what is the MAC address, MAC is Media Access Control. It is a number that is stamped on to a network card. Unlike IP addresses MAC addresses never change, they're like the thumbprints of a network card But they're not really handy, it's not really handy information. To find out your MAC address, start, run, open up command prompt, IPconfig and then use the all switch. You should get the physical address listed here and you could enter this in and you don't have to use the dashes. MAC address here, description, supported types. BOOTP protocol, DHCP or both When you're done click on add. I'm not going to add one right here but rather just show you where this is done from.

Tutorial Information

Course: Microsoft Windows Server 2003 (70-291)
Author: Brian Culp
SKU: 33478
ISBN: 193207273X
Release Date: 2004-02-26
Duration: 8 hrs / 99 lessons
Captions: For Online University members only
Compatibility: Vista/XP/2000, OS X, Linux
QuickTime 7, Flash 8

VTC Sign up & Benefits

  • Unlimited Access
  • 98,729 Video Tutorials (23,265 free)
  • Video Available as Flash or QuickTime
  • Over 1026 Courses
  • $30 for One Month Access
  • Multi-User Discounts Available