|
|
| Author: 123456789 |
As a CompTIA Network+ exam candidate, you're probably familiar with DHCPbut just in case, we're going to review DHCP basics here and then go into a discussion of DHCP Relay Agents.
When it comes to assigning an IP address to all the PCs on our network, along with their network mask, DNS server location, and more, we've got two choices on how to do it:
? Go to every workstation and configure the workstation statically
? Go to every workstation and configure them all to use DHCP
What we have here is the classic "static vs. dynamic" argument. I don't want you to think I'm lazy, but I'll take the dynamic way of doing things almost every single time.
You may wonder why it matters, since both methods involve visiting each workstation. You're right about that, and even though it's a lot quicker to configure a workstation to get its IP address and mask from a DHCP server than it is to configure the entire IP address and mask statically, the real benefits come in when the network changes.
And take it from me - your network will change. You'll remove hosts, you'll add hosts, and if the previous network manager didn't plan for future growth, the day may come when you've got to change the IP numbering scheme for your network. The choice that was made originally between static configuration and DHCP will then determine how easy the change will be.
? If the network was statically configured, you will now have to go to every single workstation and change their IP addressing to the new scheme.
? If the network is using DHCP, you simply change the networking scheme on the DHCP server and allow the workstations to get their new addresses dynamically.
Believe me, I've performed IP address changes in both fashions, and I'll take DHCP every time! Avoiding static IP address assignments also cuts down on the chances of two hosts in your network being assigned the same IP address.
When hosts receive an IP address from DHCP, it does not belong to that host permanently. The address is actually leased from a DHCP server. Let's walk through the DHCP process from the host's point of view.
First, the DHCP Client boots up, and sends a DHCP Discover packet onto the network. The host does this in order to "Discover" a DHCP server or servers. This Discover packet is a Level 3 broadcast, which has a destination IP address of 255.255.255.255.
Every DHCP Server that hears this broadcast will respond with a DHCP Offer, and it's an IP address and mask that is being offered. The DHCP Offer also includes a subnet mask, the IP address of the DHCP Server sending the response, and how long the host can keep this address (the DHCP lease duration).
If multiple DHCP Servers happen to hear this broadcast, they will each offer an IP address.
The DHCP Client will accept the first offer it receives. It does so by sending another broadcast, a DHCP Request packet.
The DHCP Server that made the offer that's being accepted will now send a DHCP Acknowledgement, which contains the rest of the information the host needs to function, including the location of a DNS server. The DHCP Server that made the offer that was not accepted will return the offered IP address to its range of assignable addresses, its address pool.
I made several mentions in this section about these DHCP packets being broadcasts. Do you remember which network connectivity device does not forward broadcasts? That's right, it's our old friend, the router!
If a PC is on one side of the router and the DHCP Server is on another side, we've got a problem. The initial DHCP Discover packet is a broadcast, and the router will not forward that broadcast to the DHCP Server. Luckily, this doesn't mean that we need a DHCP server on every single subnet on the network, because we can configure the router as a DHCP Relay Agent.
A DHCP Relay Agent will forward DHCP Requests to the DHCP Server. You can also configure a Windows server as a DHCP Relay Agent. Naturally, the Relay Agent must be on the same physical segment as the hosts that cannot reach the DHCP Server - never put it on the same segment as the DHCP Server itself.
Configuring a router as a DHCP Relay Agent is a lot different than configuring a Windows server, and your Network+ exam will not require you to configure either. You should know why the need for a Relay Agent exists, though, and should you need to configure one on your network, always check the vendor's documentation. |
Author Bio:
123456789 is an expert in this field. 123456789 has written several articles in the past on this topic. |
| You can also reach this article by using: search engine optimization certification, microsoft certification, computer security certification |
|
|
|
|
| |
|
With all the buzz going on about the importance of a site's link popularity, the "look and feel" of ... - Bob Hampton |
| |
|
You may have high ranking at the search engines yet see low conversion rates Why? Discover the 'secr ... - Gerrick W |
| |
|
While there exists a rather large potential for profit when marketing for a specific audience, the p ... - Jordi Shoman |
| |
|
|
| |
|
The goal is to build up a reputation for your blog that reflects positively on your company. If you ... - James Kendall |
| |
|
I've seen many fishermen at our pier fish for hours with shrimp and not catch a thing. My thinking i ... - Dave Jackson |
| |
|
When you get an e-mail from SEO Company with content similar to this: "We submit your site on X00.00 ... - Zoran Makrevski |
| |
|
Free inventory management software has an increased presence on the web, following the persistent gr ... - Alison Cole |
| |
|
Good content ghost writers for hire are worth their weight in gold. But only if they have the follow ... - Christopher Kyalo |
| |
|
| |
|
|
