INLS261 Tools for Information Literacy

[UNC] [SILS] [REB] [How Stuff Works] [Langa] [Web Style Guide] [ATN] [ITS Tips] [Other Lives]

[intro] [clients] [servers] [networks] [internet]
[open source] [telnet] [file transfer] [UNIX network tools] [subtask 1.5] [bookmarks] [next time]

[student] [topical] [radio] [newsletter] [interest] [policy]

Using UNIX to get Internet answers

To login, you need to make a telnet connection to the ISIS server.

To login from your computer (it's the same here in the lab or elsewhere on your laptop):

Once there, select <6> to get into a shell session and thus into UNIX. The $ is the UNIX prompt.

[top]

Internet tools available in UNIX and elsewhere (DOS, Windows)

As we discussed during the Internet session, the Domain Name System [DNS] operates behind the scenes. We don't need to know an IP address for a particular hostname, and don't need to worry about how the data get from one place to another.  For experts, though, it's good to be able to get behind the scenes to diagnose problems or errors.

Utilities available for UNIX/Linux and Windows machines, among others, include ping, traceroute, nslookup and whois.

[top]

Try them out using UNIX:

[top]

Try out WHOIS in UNIX and on the Web

You can also use and telnet tool to find out something about web domains by using the UNIX command "whois". In this example, I used SecureCRT. You can use SSH if you prefer.

[top]

Try out Traceroute a bit more

We want to use Traceroute to see how long it takes to send a signal to a remote server and have it return to ISIS.

The traceroute program is used to determine the path that messages might take from one machine to another. Recall that any packet (message) sent on the Internet must go through some number of routers to get to its destination. Each link in this path is called a hop. Local traffic usually has very few hops (zero or 1 or 2) while long-distance traffic can take thirty or more hops before arriving. Traceroute lets us look at the path a message might take through this chain of routers to get to its destination.

Using a simple telnet tool [not SSH], I ran one traceroute to europa.eu.int to see what it got me. I could see it first told me the site's IP address (expressed in numbers) and then showed me all the jumps from ATN's ISIS server through switches at CiscoKid, on to RTP, then onto the Internet backbone through several different backbone providers (AlterNet, UUNet [part of WorldCom], UUNet in Belgium, among others, and on to the final destination. In this case, it took over 30 hops to get there.

I then ran a second traceroute to www.sandhills.net which is in Southern Pines, NC (about 75 miles away), and it took 11 hops to get there, mostly through Sprint switches.

Try it out on sites you are curious about. Look at the path the connection follows and how long each segment takes.

When you are finished, type in the command <exit> and then select option 8 to close your link to ISIS

The above procedure allows you to run traceroute on a Unix server, but you can also run it on a Windows PC

The DOS way to run Traceroute is to go to start and then open the run dialog box

then type in <cmd> for a command prompt.

Once you have the command prompt, type the command <tracert> followed by the internet address

However, fully typing the word <command> will get you to the command prompt on all windows boxes

Consider adding SSH or WS_FTP to your computer for FTP applications

[top]