Occasionally, during your CCNA and CCNP studies, you’ll run into a term that just doesn’t quite make sense to you. (Okay, more than occasionally!) One such term is “reverse telnet”. As a Cisco certification candidate, you know that telnet is simply a protocol that allows you to remotely connect to a networking device such as a router or switch. But what is “reverse telnet”, and why is it so important to a Cisco CCNA \/ CCNP home lab setup?\nWhere a telnet session is started by a remote user who wants to remotely control a router or switch, a reverse telnet session is started when the host device itself imitates the telnet session.\nIn a CCNA \/ CCNP home lab, reverse telnet is configured and used on the access server. The access server isn’t a white box server like most of us are used to; an access server is a Cisco router that allows you to connect to multiple routers and switches with one session without having to move a rollover cable from device to device.\nYour access server will use an octal cable to connect to the other routers and switches in your home lab. The octal cable has one large serial connector that will connect to the access server, and eight rj-45 connectors that will connect to your other home lab devices. Your access server then needs an IP Host table in order to perform reverse telnet.\nAn IP Host table is easy to put together (and you better know how to write one to pass the CCNA!). The IP Host table is used for local name resolution, taking the place of a DNS server. A typical access server IP Host table looks like this:\nip host FRS 2007 22.214.171.124\nip host R3 2003 126.96.36.199\nip host R1 2001 188.8.131.52\nip host R2 2002 184.108.40.206\nip host R4 2004 220.127.116.11\nip host R5 2005 18.104.22.168\nip host SW1 2006 22.214.171.124\ninterface Loopback0\nip address 126.96.36.199 255.255.255.255\nno ip directed-broadcast\nThis configuration will allow you to use your access server to connect to five routers, a frame relay switch, and a switch without ever moving a cable. When you type “R1” at the console line, for example, you’ll be connected to R1 via reverse telnet. If you have a smaller lab, an access server is still a real timesaver and an excellent investment. And by getting a static IP address to put on your access server, you can even connect to your home lab from remote locations!