Showing posts with label Agents. Show all posts
Showing posts with label Agents. Show all posts

Friday, November 5, 2010

CompTIA Network + Certification Exam Tutorial: DHCP and DHCP relay agents

CompTIA Network + exam as a candidate, you're probably familiar with DHCP - but just in case, here we will review bases DHCP, and then a discussion of DHCP relay agents to go.

When it comes to assign an IP address of all PCs in our network, along with their network masks, DNS server location, and more, we have two choices on how to do it:

Or go to each workstation and statically configure the workstation

Or go to each workstation andall set to use DHCP

What we have here is the classic argument "static vs. dynamic". I do not want you think I'm lazy, but it will be a dynamic way of doing things almost every break.

One might ask why it matters, because both methods include a visit to every workstation. You're right about this, and although it's much faster to configure a workstation to mask gets its IP address from a DHCP server and then configure the IP address and the entirestatic form, the real benefits come when the network changes.

And from me - the network will change. The hosts clear, add the host, and if the previous operation did not plan for future growth, the day may come when you have the numbering system for IP network for change. The choice was originally between the static and DHCP configuration will determine how easy the change will come.

o If the network is statically configured, younow every workplace and their IP address to the new regime to change.

o If the network with DHCP, you only need to change the pattern of the network on the DHCP server and allow the workstations to get their new addresses dynamically.

Believe me, I run IP address changes, both in fashion and I assume DHCP every time! Avoid static IP address assignments also cuts the likelihood that the two machines on your network are assigned the same IPaddress.

As host gets an IP address via DHCP is not a permanent part of the host. The address is actually leased from a DHCP server. We walk through the DHCP process from the point of view the array of view.

The primary DHCP client boots and sends a DHCP Discover packet on the network. The landlord does to "discover" a DHCP server or servers. Explore this packet is a transmission of a Layer 3 IP destination address is255.255.255.255.

Each package includes a DHCP server responds with this broadcast a DHCP server, and is an IP address and a mask that is offered. The proposal also includes a subnet mask DHCP, the IP address from the DHCP server sending the response and how long the host can) keep this address (the DHCP lease time.

If multiple DHCP servers happen to hear this broadcast, each have an IP address.

The DHCP client to accept the first offer isreceives. It does this by sending another broadcast a DHCP request packet.

The server that the DHCP server offer is accepted, it will send an acknowledgment DHCP, DNS, which contains the rest of the information that the host to the demands of work, including the location of one. The DHCP server pool made the offer was not accepted, it returns the IP address offered to its range of assignable addresses, the address.

I made several referencesIn this chapter on DHCP packets are broadcast. Remember that the device forwards broadcast network connectivity? That's right, it's our old friend, the router!

If a PC is on one side of the DHCP server and router is on the other hand, we have a problem. The first is a broadcast DHCP Discover packet, and sends the router does not broadcast to the DHCP server. Fortunately, this does not mean that we all need a DHCP serversubnet in the network, because we can configure the router as a DHCP relay agent.

A DHCP Relay Agent DHCP server DHCP requests to send. You can also configure a Windows server as a DHCP relay agent. Of course, the relay agent on the same physical segment as the hosts can not reach the DHCP server - not on the same segment as the DHCP server itself.

Configuring a router as a DHCP relay agent is very differentconfiguration of a Windows server and the network + exam does not require the user to configure it. Need to know why the need for a relay agent there, and you need to configure your network, always check the vendor documentation.

Related : Corrugated Plastic Compare Price Store Spark Energy

Wednesday, September 1, 2010

CompTIA Network+ Certification Exam Tutorial: DHCP and DHCP Relay Agents

As a CompTIA Network+ exam candidate, you're probably familiar with DHCP - but 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:

o Go to every workstation and configure the workstation statically

o 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.

o 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.

o 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.

Related : PDA Mobiles Spark Energy