Friday, December 2, 2011

New Blog Gadet for E-mails

You can now follow my blog easier through the new gadget that blogger made. You can now follow my posts by simply putting your e-mail into the bar and hitting submit. Gadget is located on the right of my blog posts, directly on top of the polls. HAPPY BLOGGING!

Lab #5

For lab #5 you have to configure the routers interface, if you do not then you network cannot reach the eagle server (My Situation). To configure the routers you have to first setup the R2-Central router, which is the first router connected with the switch. You have to install an operating system for the Host PC and you need to install the terminal command prompt. After you install the operating system you go to the command prompt, and you type in the command INTERFACE, FastEthernet0/0 which then you add in the ip address given and turn the port on. My failure was the access the command prompt (A simple mistake which i hope i won't make in the future). My biggest failure of the lab which i now understand was to correctly read the instructions that are given to me CAREFULLY.

Lab #4

Lab #4 is basically lab #3 except you fully mastered the understandings of how to actually repair your network. You basically have to replace your "broken" devices (The Eagle_Server) with one that is configured correctly. When it says to replace it means to reconfigure and reboot the problem. That process is called troubleshooting, its something that 90% of the time you have to do when you first make a network. By troubleshooting the network, you will run simulation mode, which directly takes you step-by-step how the packet is traveling through the network. This helps you identify the problem accurately instead of actually taking the time to find the problem more physically. You repeat the simulation and also the trail & error process it takes to successfully send and receive a packet.

Lab #3 Reflection

Lab number three is basically to try and understand what went wrong with the network and to repair the problem in the network. You add in more numbers to the devices such as the gateway IP address and the DNS address which was the main problem of my network. I completely ignored the DNS server IP address, which is probably why the 2 routers didn't want to communicate with each other, it's imperative that you reach all of the requirements to components of the network if you want your server system to function correctly. Therefore, the problem was located in the transport layer which deals with TCP.

Lab #2 Reflection

In lab number 2 the main concepts were to determine if you configured the devices correctly so you can send a packet. The lab simply told you to diagnose the computer and to look at the scenarios when you send a packet to see if you successfully configured your network right. I configured all of the data that was given to me in the charts, after that i connected all of the devices together in the correct diagram. I turned on all of the ports, used the correct type of wire, and finally got all of the lights to go green.

Now was my part in lab #2 to send a packet from the Host computer to the Eagle_Server, without any type of technical difficulties. That's the main challenge and concept of the lab, to see if you know what you're doing instead of just randomly plugging in cables and typing random numbers. In this case, i did not complete the lab; therefore and i knew what the problem had to be. When i sent the packet over from the host to the eagle server, the packet successfully went through the from the host computer to the switch to the router. The packet did not however, travel to the second router. So right then i knew that the network was not working and i was just configuring with random numbers i did not comprehend with. Understanding what went wrong is the next lab.