Using Packet Tracer To Design A Small Computer Network
Using Packet Tracer has allowed computer networking professionals to design networks, teach ideas and concepts, and save time on brainstorming. Although it’s a wonderful tool, making a simple network is a challenge if you aren’t familiar with the program.
Having a networked based on a hub is easy enough- there isn’t any significant configuration. Putting a router in the network is a different story, however, since it will separate networks. Because it does so, any network containing a router will have at least two different network addresses for proper communication. Configuring them is just a matter of assigning the correct addresses and settings.
Constructing the network will take two crossover cables and a console cable. The two crossover cables will connect each desktop to the Ethernet ports of the router, while the console cable will connect one of the computers to the router for configuring. Be sure that the cable you are using isn’t a straight-through when using your Ethernet cable, as this type of cable is reserved for unlike devices.
The IP addresses you assign will be the logic of the operation. It’s up to you which network numbers and addresses you use, but they must follow a certain convention in order to work. You will be using at least four IP addresses total, counting your two desktop machines and two Ethernet ports on the router. Assign each Ethernet port and IP address that corresponds to a certain network. If you assign both to the same network, you will quickly see the configuration won’t work.
After configuring the IP addresses, you will need to configure what is called a gateway address. The gateway address is simply the IP address of the Ethernet port that a computer is connected to. The gateway tells a computer where to send and receive information that comes across the network. This address is edited on the desktop in the IP address settings. Without it, information would never reach its target destination.
Troubleshooting is what computer network technicians are known for. If you find that your network isn’t working at this point, you shouldn’t be surprised. There are hundreds of reasons a network can go wrong, ranging from physical connections to input errors. The trick is to troubleshoot the symptoms of the network to see where you went wrong and how to fix it. Try to complete the troubleshooting process by yourself, as it will be more of a meaningful lesson for the future.
In Conclusion
The small network described is functional, and is even used in real world applications. Using Packet Tracer will simplify the process of designing the network so that you can save time in the overall process, and put more time into troubleshooting and problems that arise during the course of the implementation.
Learn more about packet tracer tutorials and packet tracer.