Tuesday, September 7, 2010

Fully Qualified Domain Names

A fully qualified domain name is a specific domain which comes with a trailing dot or has a dot at the end. This dot is however usually ignored. The domain name is very unique and this is the reason leaf node uses it to generate message ID. The message ID is necessary to identify each message or article. A message ID is a header or a title which is usually not visible until you choose to display header, display raw or display source. The internet will give you more information on how to acquire a fully qualified domain. The other information available is on how to configure your fully qualified name. You might encounter some technical language and terms but, all you have to do is keenly follow the instructions so that you can get the domain name you want.

The fully qualified domain name has two parts and they are the host name and the domain name. It is very easy to get a fully qualified domain name. Firstly assuming you are registered to own the domain meat dot com, you can also have the sub domains that will fall under the domain and this means that you can have my dot meat dot com registered as yours. You can also tell your internet service provider to assign you a domain that can be used for message ID. On top of this, you need to ask them for more information about the domains available if you do not fully understand their purpose. They are sure to give you details and also direct you on how to go about configuring the fully qualified domain name.

You can configure the fully qualified domain names using two ways and the first is system wide and the other is local to leaf node. The first thing you should know about the system wide is that it should have the host name entered into your system so that it is made available all over the world. Therefore the first thing that needs to happens is to configure the host name alone and the internet will provide a lot of information on this for you to follow. The second step involves putting the fully qualified host name into the system. The local to leaf node configuration is not complicated at all. The best way to configure is using the system wide.

It is good to know the various kinds of domain names so that you can make the best decision. While you undertake your research on the domains, you will also discover that there is an unqualified domain name and this is the opposite of the qualified names. You will also discover that the fully qualified domains are also known as absolute domain names. You will get to learn about the partially qualified domain names which are different as they imply. Do not forget that a fully qualified name fully and uniquely identifies the node in the domain name system from the root. Knowing all the different features available will enable you to make out which domain is which and you can choose one that will be most suitable for your personal use or for your business or organization.

My Links : Small Network Printers Store. LOWER Prices in The Same Item 8 Port Hub

Monday, September 6, 2010

Network Security - Little Known Threats

Little Known Network Security Threats

There are a number of common network security threats that can damage your network. Some prime examples include remote login capability, SMTP hijacking and backdoor entry to a computer network. There are however dozens of other ways someone can inadvertedly access your network and steal or damage your data. Here are just a few network security threats you should be aware of, whether you operate a private or corporate network.

DNS - DNS or denial of service involves a major attack on Websites. Usually this threat is reserved for large computer networks. When a denial of service attack occurs there is often little a company can do immediately to recover from the attack. When this happens a hacker connects to the server multiple times purposefully even though the hacker is denied access. Over time these repeated requests cause the system to slow and crash.

Macros - This is an application that allows someone to create a script of commands that can run on your network. These macros are capable of crashing computers and destroying data.

Virus - A computer virus is one of the most common threats any private or corporate network user faces. Fortunately viruses can usually be prevented using modern anti-viral software.

OS bugs - Operating system bugs occur when backdoors are accessed to operating systems. Usually a backdoor is left open to attacks when inadequate network security systems are in place. Fortunately adequate network security including use of firewalls can help limit ones exposure to this security threat.

See Also : Bulk Email Friendly

Sunday, September 5, 2010

Top Six Internet Errors and How to Decode Them

Internet errors can frustrate and destroy hopes of an enjoyable net surfing experience. Often you can't open your desired web pages, your web browsers mysterious shut downs, or the web page never loads. Searching for the cause of Internet errors can be just as frustrating as the errors themselves. However having a basic knowledge of these Internet errors can help cut down on the repair time.

By simply examining the digits in the Internet error message, you can easily pinpoint and solve your Internet and email problems. Internet errors are expressed as three digit codes. One of the most common errors "404 Not Found". The three digit code provides a helpful window into the cause of an Internet error. The number four such in 400 errors indicates that the problem is caused mishaps on your end. The number five corresponds to server errors that are caused by the Internet Service Provider (ISP). There is very little you do to fix 500 level errors with the exception of calling to complain.

Here are the top five Internet error messages and how to solve them:

400 Bad Request

This essentially means that your request to access the url that you typed was denied. This error happens most often when you misspelled or mistyped the Web address. The only solution to this problem is to double check the address that you have entered. Recently many websites are becoming upper case sensitive. Another alternative is to return to the company home page. From there, you can navigate your way to your desired page.

401 Unauthorized

When you try to access an encrypted website, you may receive this error if your browser does not support that encryption. Password protected site will also produce this error if the wrong password is entered.. The best way to handle this problem is upgrading your browser. If you are aware of the encryption type you can specifically add this encryption to the browser. Regarding the password, double check to make sure it has been entered correctly.

404 File Not Found.

This Internet error can also easily be produced by improperly typing the web page address. However, it is often a response to a missing link or file on the the website. The website administrator may have purposely removed link. If the site has been updated it, you may be redirected to an alternate link. Also, you can contact the web administrator and request an alternate link or search for an alternate link by navigating from the home page.

Certificate Error: Navigation Blocked

Internet Explorer seems especially prone to this error. The security certificate presented has errors therefore the page will not load. Enhanced settings in the browser does not allow certain pages to load if the security certificate or expected domain does not match up with the one your browser expects. You solve this Internet error by decreasing your security settings.

The Page Cannot Be Displayed

This error can be on your end or the web server's. However, it best to check that your hardware is functioning properly. Your Internet connection could be down or the equipment used to access the net may not be functioning properly. Double check Windows' settings to ensure that your hardware or software is configured correctly. That means that the modem may not be working properly or Firewall/Router is blocking net access. If you are under a network double click the network connection icon to check the settings. After all else fails, contact your Internet service provider and report the Internet errors.

Failed DNS Lookup

Internet Domain Name Sever (DNS) can't translate the requested URL protocol. In essence this Internet error means your computer is unable to translate the human language into computer language. Computer don't understand http://www.google.com. The only understand the numeric code used to produce this address. This internet error occurs usually when the server has crashed.

Another net common problem is overall slowdown when surfing. This can be caused by spyware or simply lack of maintenance. Visit "How to Speed Up Your Computer" page for more tips and tricks to reduce Internet errors and to increase PC speed.

My Links : Digital Cameras Store. LOWER Prices Same Item Mobile Providers

Saturday, September 4, 2010

How to Get a Website Made

If you want to get online and are wondering, "How do I make a website?" you have three choices: hire a Web vendor such as a Web designer to make it for you, use an online template-based turnkey service or make it yourself from scratch. This article is specifically for the Web novice that simply needs a place to begin.

Every website consists of a domain name, a host provider and the website content. To have a live website on the Internet, all three things need to exist.

Today, there are countless services that offer all of this in bundled packages. Yahoo, Earthlink, Go Daddy, Network Solutions, Register, Domain, Host Gator and Domain Direct are just a few examples of companies that offer everything you need to get up and running. These companies can provide you with a domain name, hosting services, and usually a template-based, turnkey website creation service as well. Homestead is an online service that allows you to create a website from a list of templates, customize it and publish it on your own domain name.

And there are websites that allow you to create a blog for instance, and they'll host it for you. Two examples are Wordpress and Blogger. They are very easy to use, even for the novice and you don't need to know any HTML.

The downside to template-based sites is that they are cookie-cutter sites that risk looking a lot like other websites (especially ones in the same industry). And if they don't allow you to have your own domain name (like Blogger.com) then any marketing efforts are severely diluted.

Finally, you could take the time to learn the craft of making websites and make it yourself. This latter scenario is good for two reasons. First, you'll save money in the long run by doing it yourself and second, you'll always be able to manage and update your site since you created it in the first place and you have necessary skills. Of course the downside to this option is that it takes a lot of time and dedication to learn the art and technical skills necessary to make a website that works.

Regardless of the choice you make, you'll fare much better if you understand the fundamentals of making a website. So let's look more closely at the three parts that make up every website.

Domain Names

An example of a domain name is YourWebsite.com. A domain name is unique and contains two parts, the actual unique name and the extension. A domain name is also called a URL (for Universal Resource Locator). In the above example, 'YourWebsite' is the unique name and the '.com' is the extension. The.com extension is the most popular U.S. extension. Other examples of extensions are.net,.org, and.edu. Other countries use different extensions. Britain is.co.uk, Canada uses.ca and Russia uses.ru, for example.

You buy domain names from registrars, basically domain name brokers. There are many registrars in existence today. However, I always use the original company that used to have a monopoly on domain names back in the dawn of the Web, Network Solutions ( http://www.networksolutions.com ).

To determine if a domain name is taken or not (remember, they all have to be unique), just go to Network Solutions and type in the name you are considering and you'll find out immediately if it's available.

An important thing to remember when buying and managing your domain name is that they are "rented" to you for a set period of years. This means they expire. So if you don't stay on top of it and renew, then you risk someone else grabbing your domain name if you let it expire.

Also, it is infinitely better to have your own domain name than it is to use an online service for your website. Online services that offer you a website but the site "lives" on their domain name are not as good because your marketing efforts are wasted. For example, Blogger.com offers a service like this so that when you create a blog, but your new domain name becomes YourWebsiteName.Blogger.com. Notice that it ends in blogger.com, which is different than a site with your own domain name which would be www.YourWebsite.com. If you market the first one, you are actually marketing blogger.com, whereas if you market the second one you are marketing yourwebsite.com.

A Host Computer (Server)

A physical computer where the content of your website is stored is called a host computer or Web server. This server can be one you own or one you rent from a hosting company. I recommend that you use a hosting company since it is far cheaper and much easier to manage. To access the content on a server, you type in the domain name of an Internet-connected website, which then accesses the content stored on the host computer and serves the content back to you. (This is basically the same process as opening up you're My Documents folder on a Windows machine and clicking on a file, except on the Web, the file is located on another computer.)

Simply put, if you want a new website you'll need a computer to store it on that's hooked up to the Internet. There are a huge number of hosting companies out there that will provide this service for you, and often at very low prices. You can expect to pay a set-up fee and a monthly fee. The set-up fee is sometimes waived or could cost up to hundreds of dollars. And the monthly fee can range from a few dollars a month up to hundreds of dollars. Two popular hosting providers are GoDaddy.com and Earthlink.net. For a first website you'll be a lot better off if you use a hosting company.

The Content

The content of the website is the files that make up the site, which can contain text, images, applications and media. Web content can either be static or dynamic. Static content doesn't change or move. Text and images in an HTML page are often static. Dynamic content comes from a database and is processed at the moment the user accesses it.

Media content can be either audio or video files.

Dynamic content is managed by Web applications and usually accesses a database. Examples of website applications are forms that ask the user to give contact information that the user submits by clicking a button, or e-commerce where a user chooses a product and buys it with a credit card. There are many other types of applications on the Web as well.

What's important for you to remember is that creating Web applications is more difficult and more expensive than putting together a simple text and image website. This is because the skill level required is higher for those who write code to create applications and it usually takes more time to do. For a first website, it's best to stay away from dynamic content and Web applications. A simple text and image site will be enough for you to start.

How a Website's Content is Organized and Goes Live

The simplest way to understand this is to consider an example. Let's look at a three-page static website.

This hypothetical website contains a Homepage, an About Us page and a Contact Us page. The homepage is accessed on the Internet by typing the domain name (or URL) into your browser. When you 'arrive' at the homepage you'll see somewhere on the page two hyperlinks (links are the building blocks of websites and the Web as a whole). Links are generally blue and underlined. One link will say 'About Us' and the other will say 'Contact Us'. When you click on each one you'll be brought to that corresponding Web page. Back on the homepage, this list of two links is often called the 'navigation' or Nav bar. Most sites have many pages organized under numerous sections. Their navigation consists of a grouping of links that lead to each main section of the site.

In our three-page website example, the site contains a total of three HTML pages that physically reside on a host computer.

To have gotten this site live on the Internet you would have had to go to a domain name registrar (by going to their website or by calling them) and purchasing an available domain name. You would have then had to have the three static Web pages created (either by someone you hired or yourself), and then you would have had to have purchased a hosting service to provide a permanent place (a server) for the three pages to reside. Finally, you need to make sure that the hosting company associates your domain name with the machine your website resides on. This is called setting the DNS.

These three pages would sit there on the host computer, or server, and await requests from people on the Internet typing in your domain name into their browsers.

So to recap, here are the steps to making a website:


Buy a unique domain name
Buy a hosting service
Create the website content (either by hiring a Web design company, using an online service or doing it yourself) And many online companies offer all three of these for one price
Publish the content to the Internet by putting it on the hosting server that is hooked up to your domain name.
Ensure that the domain name is associated with your website and host computer (setting the DNS, which stands for Domain Name System).

Whether you hire a Web professional to do all these things for you, use an online service or do it yourself, you'll need to have each of these steps completed in order to get your site live on the Web.

If you choose to hire a Web professional or use an online service such as Network Solutions, GoDaddy or Homestead, you should ask them if they take care of each of the above six steps. If so, look at other sites that were made by them to see if they meet your standards. And be sure that the site is built taking into account what you want it to accomplish and who will be the site's audience.

See Also : Encryption Security Plasma TV Store. LOWER Prices in The Same Item Space Gravity

Friday, September 3, 2010

Microsoft Server 2008 Certification - Routing's Not Just For Cisco Exams Anymore!

Knowing routing theory and routing protocols has always been a big part of earning your Cisco CCNA and CCNP certifications. According to Microsoft's exam blueprints for the Server 2008 certification exams, that knowledge will also serve you well on your Microsoft exams.

The topic outline for the Configuring Windows Server 2008 Network Infrastructure exam (70-642) specifically mentions routing and routing protocols as exam topics. Specifically mentioned are RIP, OSPF, and static routing - three topics every CCNA and CCNP candidate will be well prepared to handle!

IPSec isn't part of the CCNA exam, but you'll see it on at least one CCNP exam, and it's also listed as a 70-642 exam topic. IPv6 and IPv4 addressing are both covered on the 70-642 as well.

Microsoft's website lists the following major skills you should expect to see on this exam:

Configuring IP addresses and Services (routing with RIP and OSPF, static routing, persistent routing, addressing, DHCP and DHCP options including relay agents, IPSec policies, Authentication Header and Encapsulating Security Payload, subnetting, supernetting)

Configuring Name Resolution (DNS configuration, zones, records, replication, and integration with Active Directory, and client computer name resolution techniques)

Configuring Network Access (includes NAT, VPNs, RADIUS, 802.1x authentication, MS-CHAP, firewalls, and remote authentication methods)

Configuring File And Print Services (self-explanatory)

Monitoring And Managing A Network Infrastructure (includes SNMP and Windows Server Update Services)

Your CCNA and CCNP preparation will not quite be enough to get you past this exam, but as you can see, it'll give you a great head start!

Friends Link : Blank DVDs Store. LOWER Prices in The Same Item

Thursday, September 2, 2010

Connect To The Desktop Of Your Home Computer Via The Internet

We live in the age of global communication and connectivity. Could you imagine 10 years ago if you had told someone you'd be sitting in a coffee shop, connected to a world wide network, with no wires connected to your laptop, reading the latest news or even playing a game with your friends?

They would have suggested that you are mad! Fortunately, that is not the case and we do live in a world where global communications are standard and almost everyone has their own permanent connection to the internet via broadband.

What if, via this worldwide communications network, you could not only read the latest news or do your grocery shopping online; you could actually remotely control your PC at home! Think about this for a minute, what would this allow you to do? Would it allow you to remotely use any applications you may have installed at home, such as accountancy applications, spreadsheets or documents? Allow you to check any downloads you may have progressing at home? Check on emails that only come in to your email client? The possibilities really are endless. There is a solution at hand, and in this article I will focus on using the inbuilt features of Microsoft Windows XP Professional, namely, Remote Desktop.

If you have never used remote desktop before, don't be worried. It's a simple feature that does what is says, presents you with your desktop via a client. If you look in Start -> Programs -> Accessories -> Communications, you will see a Remote Desktop Client application.

Using this application, you can enter a computer name or IP address to connect to. You can even map your home computers hard drives as well, so that they appear in windows explorer, and even print to the printer beside you, from your home computer, over the internet!

Try it at home if you have two computers. You need to make sure that Remote Desktop is enabled first, and this can be done by selecting System from Control Panel, selecting the remote tab, and ensuring that "Allow users to connect remotely to this computer" is enabled. If you plan to do this at home, take note of the "Full computer name", as this is what you will need to enter into the remote desktop client to connect to this computer.

I know you are worried about security at this point, but don't worry - we'll address that later.

Now, if you do have two computers at home, try it and see what happens! You should be presented with the familiar login box, and once logged in - ta-da! You are now on the desktop of the other computer, using the remote desktop application on your local computer!

Now - what if this functionality could be extended; so that you can connect to your home PC from anywhere in the world provided you are connected to the internet? Fortunately, this can be done! There are seven steps that we need to do in order to achieve this.

1. Ensure that your computer will accept remote desktop requests

2. Make sure your password is strong!

3. Note down your IP addresses

4. Change the port number that remote desktop responds on (this will aid with security)

5. Ensure any local firewalls are not blocking the Remote Desktop Port.

6. Create the necessary port forwarding rules on your home router

7. Sign up to a Dynamic DNS service (ignore if you have a static IP address from your ISP)

Let me explain these steps and how to perform each one.

1. Ensure your computer will accept remote desktop requests. As above, you need to select the System icon from Control Panel, and, from the remote tab, ensure that "Allow users to connect remotely to this computer" is enabled.

2. Make sure you password is strong! If your password is not very secure, make sure you change it so that it has at least 8 characters, at least one uppercase character and at least one symbol. One way to do this is to use symbols/numbers as a substitute for letters. For example, say I wanted my password to be the name of my son, Benjamin. Instead of using Benjamin as my password, I could use 83nj@m1n! , which as you can see, is a lot more secure than Benjamin.

3. Note down your IP addresses. We need to make a note of your internal and external IP addresses. To do this, go to Start -> Run and type cmd . Then click OK. Type ipconfig and look for the IP address entry. In this example, we will use 192.168.01. This is your internal IP address. Now browse to http://www.whatismyip.com Take a note of your IP address, in this example, we will use 1.2.3.4. This is your external IP address.

Things will get a bit techy from this point on. The tasks we need to perform are pretty straight forward, however, if you have any questions, please ask a technical friend first or consult online help from the internet as an error in the below steps could cause your computer to malfunction or cause you internet connectivity problems.

4. Change the port number that remote desktop responds on. This will require you editing the registry. Go to Start -> Run and type regedit . Then click OK and you will be presented with the Windows Registry. I won't get into detail about the registry now, there are books as thick as encyclopaedias written on the windows registry, suffice to say, if you don't know what you are doing, don't mess around with it!

Now, if you browse through the tree to
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlTerminal ServerWinstationsRDP-Tcp. Once there, look for an entry in the right hand pane called "PortNumber". Double click this entry and select decimal. Now, this will be 3389 by default. Make sure you change this to a number of your choosing, above 1024 and below 65534. In this case, lets you 23456. I highly recommend making this number as obscure as possible to avoid people discovering an open port via portscan! Click OK, and close down Registry Editor.

One caveat to this, what port you decide to use, may affect the usability of this feature. Some companies will block ports that are not in common use, so 23456 will be blocked. Other companies allow all ports, as do most home users. If you choose a common port, such as port 80 or 443, it may allow you more access from secure networks, however will allow hackers to more easily see your PC on the internet.

Even using a higher port number will still render you vulnerable to certain attacks, however, the risk is severely minimised when using a higher port number. I and a number of colleagues have used this technology for a number of years without incident; however remember when allowing any connectivity over the internet, there is always a risk! This choice in functionality is up to you.

5. Ensure any local firewalls are not blocking the Remote Desktop Port. This step will most likely requiring you to check the instructions with your particular desktop firewall product. What you will need to do here is ensure that anyone is allowed to connect to the port number used above. This is usually in the form of a firewall rule and looks similar to the below:

Allow Anyone using protocol TCP 23456 in both directions to connect to My computer. Once again, this will require consulting your desktop firewall instructions.

Now, before we go any further we need to make sure this change has taken effect. Reboot your computer, and, if you have another computer on your LAN, try and remote desktop to your computer with the ":portnumber" at the end, for example. Mycomputer:23456, or your IP address, 192.168.0.1:23456. Make sure this works before continuing or else the next steps will not work.

6. Create the necessary port forwarding rules on your home router. This step will depend on your particular home router. You will need to connect to this and define a port forwarding rule similar to the following:

Allow anyone -> Using Port TCP 23456 (substitute for your port number above) to connect to 192.168.0.1 (substitute for your internal IP address). You may need to consult the manual for your router regarding port forwarding for this. You may need to define a particular protocol or server for TCP 23456 (substitute for your particular port number above). This is the hardest step of all so it may take you a while to achieve.

7. Sign up to a Dynamic DNS service (ignore if you have a static IP address from your ISP). If you know your external IP address will never change, ignore this step. If however, you have a dynamic IP from your ISP, you will need to perform this step.

This step is to ensure that if you external IP address changes, it will be registered on the internet so you can still connect to your PC. The best service I have found to use is http://www.dyndns.com.

Sign up here and enter a hostname that you would like to use, ie, myname.dyndns.com. Follow the instructions here to ensure that your external IP address is always updated on the internet.

8. Finally, you are ready to go. If you have completed all the steps above successfully, you'll want to test this out. The best choice will be to go to a friend's house with home broadband, and test connecting in. Once connected to the internet, load up your remote desktop client, and enter either you external IP address or DNS name, eg 1.2.3.4:23456 or myname.dyndns.com:23456.

Chances are this may not work the first time, so, I have included below tests that you can perform at each stage to determine where the problem may be.

1. Ensure that your computer will accept remote desktops requests. The best way to check this is to go to Start -> Run and type cmd . Then type "telnet 127.0.0.1 portnumber" ie, "telnet 127.0.0.1 23456". This should return a blank cmd window if successful, and an error if unsuccessful. If this is successful, move on to the next step. If this is unsuccessful, make sure Remote Desktop Connections to you PC are enabled and the port number is correct. You can do this by typing "telnet 127.0.0.1 3389" in the same cmd window as before, and if this is successful, your remote desktop port number has not yet changed. You may need to reboot your PC or check the above registry entry.

2. Make sure your password is strong! This test I will leave to you to ensure your password is correct.

3. Note down your IP addresses. Make sure that all your IP addresses are correct!

4. Change the port number that remote desktop responds on. You can check this has been set successfully by going to Start -> Run and type cmd . Then type "telnet 127.0.0.1 portnumber" ie, "telnet 127.0.0.1 23456". This should return a blank cmd window if successful, and an error if unsuccessful. If this is successful, move on to the next step. If this is unsuccessful, make sure Remote Desktop Connections to you PC are enabled and the port number is correct. You can do this by typing "telnet 127.0.0.1 3389" in the same cmd window as before, and if this is successful, your remote desktop port number has not yet changed. You may need to reboot your PC or check the above registry entry.

5. Ensure any local firewalls are not blocking the Remote Desktop Port. The best way to test this functionality, if you can, is to use a PC on your LAN. From a PC on the same network as yours, type "telnet ", ie "telnet 192.168.0.1 23456". If you receive a blank cmd window, then this is working OK. If you receive an error, and all the above tests are successful, then this indicates that something on your PC is blocking this connection. You will need to look at any local firewalls that may be preventing this access (including the inbuilt Microsoft Firewall).

If this step works, also ensure that your local firewall is not just allowing computer on your local network and nothing else to connect. I stress again, make sure you read the instructions that came with your desktop firewall.

6. Create the necessary port forwarding rules on your home router. This is the most problematic part of the process. To check this, you will need to be on another broadband connection. Once connected, navigate to Start -> Run and type cmd . Then type "telnet " ie, "telnet 1.2.3.4 23456". Once again, this should return a blank cmd window if successful and an error if unsuccessful. If all the tests above have been successful, and this command is unsuccessful, then this problem indicates there is an issue on the router port forwarding the Remote Desktop request. Ensure that you have read the manual and port forwarded this successfully.

7. Sign up to a Dynamic DNS service. You can test this simply by performing the same command as above. If "telnet externalip portnumber" works, and "telnet myname.dyndns.com portnumber" does not, then there is a problem with this service. From a cmd window, type ping myname.dyndns.com and see if it returns a reply. If not, then you will need to check the online help with regards to this service.

That should be it; you should now be able to connect to your home PC from almost any internet connection. Remember you can use advanced features of the remote desktop client such as connecting your local drives, printers etc.

I suggest you have a quick look at the help that comes with Remote Desktop Client to explore everything that it can provide you with.

As I mentioned at the beginning of this article, the possibilities for this use are endless depending on your own individual needs, and I imagine that as technologies such as 3G and GPRS are improved, this ability will extend to your PDA device as well so that you can access your home PC on the move, that's if you are not carrying around a small PC and mini holographic projector in your top pocket by then!

My Links : Buy Cheap PS3 Games | LOWER Prices in Same Item Bose Headphones Store Save! Plasma TV Store. LOWER Prices in The Same Item

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