TELNET - TASK A

Windows Vista did not make this task any easier. I had read in one of the postings on the discussion board that the "Help Menu" in WINDOWS VISTA (http://windowshelp.microsoft.com/Windows) was a must read and boy was that pretty good advice.

Initially I read the part on how to change my settings for Telnet Client and thought I knew it all, but was proved wrong. The next option was to revisit the help menu at http://windowshelp.microsoft.com/Windows and read the instructions in its entirely.

Once the clouds cleared, it was breeze to do Task A in Module 1. A copy of the following email can be found in my inbox @ https://sm-mailgw.curtin.edu.au .


On the whole this experience gave me a little peek into the traditional methods used before the wide world of web. It is interesting that commands on Telnet such as "open" is O, "print" is P etc. Telnet has also reminded me that the very first system I used in Telstra for technicians and fault reporting was actually Telnet based. The first look at the screen and commands brought all those memories back.... we have definitely moved forward in IT based systems.

I can now see that Telnet would probably be more useful to seekers of information rather than programmers as programmers now have available more advanced and improved GUI (Graphical User Interface) applications to access remote locations or machines. Some examples of this would be Windows Terminal Services, Altiris, VNC etc.

Telnet is most likely to be used by program developers and anyone who has a need to use specific applications or data located at a particular host computer. (Refer: http://searchnetworking.techtarget.com/sDefinition/0,,sid7_gci213116,00.html)

I also checked out www.telnet.org/htm/faq.htm, for more of a insight during my struggle for comprehension of what I was reading.