One of the biggest misconceptions of all time in networking is the use of a traceroute to determine that your communication with a server has high latency. On windows, traceroute is the same command as tracert. Many people beleive that when they see high latency such as 250ms+ in a single hop of a trace-route that it means that that device in the transit path is responsible for the degraded network performance when in fact it could not be more further from the truth. First lets look at how...

This website was founded back in 2009 with the mission to provide CCNA candidates the ability to study for the CCNA Exam using GNS3, a freely available application so candidates do not have to spend hundreds if not thousands of dollars on Cisco Hardware to get hands on experience. Throughout the years I feel that the website has fallen from grace and have moved away from the founding ideas of the website and more towards a hardware lab based workbook which requires you to buy a lab...