Our friend DHCP, so now you have Server 2003 installed and you want to install a dhcp server. Well here is a basic setup that will not get you internet on all the computers, but it will get the other computers pulling the correct IPs. Lets begin.

DHCP information

DHCP's name is Shadow.local

NIC is 192.167.7.120 outside of the range of course.

Gateway is 192.167.7.0

Range: 192.167.7.1 - 192.167.7.100

How to Install the DHCP Service Before you can configure the DHCP service, you must install it on the server. DHCP is not installed by default during a typical installation of Windows Standard Server 2003 or Windows Enterprise Server 2003. You can install DHCP either during the initial installation of Windows Server 2003 or after the initial installation is completed.

**Note here that the router is not dishing out dhcp and its ip has been redesignated to 192.167.7.0

Start > Manage Your server then add or remove a roll. Nothing exciting here:)

I'll assume you have done the basic typical install and a domain controller has been installed. You will need it for the DHCP server.

Select it and hit next.

Self explanitory, a picture is worth a thousand words

Here put in the scope ( what you want to do, much like a set of rules ) and its description.

Here insert the range of ip addresses you want to assign and their subnet mask.

Exclusions and things such as servers, network printers and the like, which do not need to be reassigned IPs.

The length of the lease here.

Assign here the gateway that will be dishing the DHCP out.

Not neccessary but add your information here if you are using this.

Same as above.

Hoped you'd never ask Windows:)

How to Configure the DHCP Service Now HCP is installed, create a scope, which is a range of valid IP addresses that are available for lease to the DHCP client computers on the network. Microsoft recommends that each DHCP server in your environment have at least one scope that does not overlap with any other DHCP server scope in your environment.

SO now we want to manage this golith machine called DHCP and where would we do such a thing other than manage your server.

Up pops this lovely lil' msc and your going to right click on DHCP and go to manage authorized servers.

At the prompt type in the ip of the server. IN our case its 192.167.7.120

Plus its name at this following prompt. Rather repetitive isn't it.

Now here get the local connection that is giving the DHCP to the router click properties. click tcP/IP and properties for that baby as well. In here set the address to static, not dynamic and your set. Release renew IPS on the other computer and presto you should be pullin the correct IP if you have configured the router correctly.

Server Setup

This diagram once again showing how I would set this experiment up with DHCP. The Lines connecting them together with cat 5 or some sort of Ethernet cable as well.

The Wan port going to the Internet ( big cloud of doom ) and the DHCP server doing into any of those normal ones.

Backup and Restore information

OF course now since you did such a wonderfull job at settin this baby up, you want your hinny protected in case of disaster. Right click on the DHCP server icon/title where we did the authorization and clickbackup.

Restore right click then restore and kabam goodness all over again!

Recovery and Backup stratagy

I would use a commercial product called acronis to backup such wonderfull things such as our dhcp backup. For configuration files it would be twice a week and be rotated through a process of 4 weeks or one month. If any changes were made a new backup would be made BEFORE those changes and a new one immediatly after the changes. A log would also be kept of changes/updates/brokeness and all such things as well as who did the changes. That log would also be stored in a safe place as well, in both paper form and digital.

If the server went down hopefully I had identical hardware to replace it, and since I had those handy dandy backup files we'd be up in a jiffy.

Removing a certain IP or Mac address off of a DHCP server

For IPs, just check the leases and kick the dude or dudette off.

The DHCP Panel::

The DHCP Process Capture::