top of page

Setting up a Network

Networking can be defined as a pathway between any number of nodes. The term "network of tunnels" is an example. Networking is by no longer a new concept or exclusively restricted to technology. Networking could refer to roads, railways or the telephone network, the same concept comes to mind, a pathway by which something is transmitted. Thus a computer network is an electronic extension of the same concept. The purpose of a computer network is to link two or more "clients" (or servers) together in order to exchange information.

The idea of computer networking is new to some people and almost always seen as a highly technical and rapidly evolving process. Every day, computer professionals are called upon by their employers to evaluate, judge, and implement the technologies necessary for the rapid communication of dissimilar groups in order to enhance productivity or lessen complexity within the organization's processes. Most see the task as a formidable one, and many feel they are not qualified or fully prepared to drive the creation of a Local Area Network (LAN) or Wide Area Network (WAN).

There are three basic rules without which no computer network could be created. Although these three rules may seem trivial, they are the cornerstones for a successful development initiative.

In order to do computer networking, you must:-

  1. have a means to connect two or more "clients" together.
  2. have computers that speak a common language.
  3. Determine the rules for a dialogue: Who talks first? Who responds? How are errors handled?

Most of problems facing existing networks are as a result of design factors, either they were not thought out fully, or not proactively designed to allow for network growth. Design is the most important ingredient if a network is to meet all the necessary milestones for success. Regardless of how limited the initial requirements each new network design is a new challenge. Cutting corners at the design to shorten the schedule could add weeks of re-engineering at the end of the project.

Documentation is equally important, the documentation validates the time and put into the project. Proper documentation can save untold time just as a means to eliminate the endless routine of searching for that one piece of critical information necessary during a physical failure or preplanned upgrade. As the network grows the documentation will provide the evidence to justify the increase in budget to gain the necessary resources and manpower.

ahb Solutions banner 1
bottom of page