VIEWS: 1 PAGES: 11 POSTED ON: 11/5/2011
June, 1993 Computing & Communications Installing NCSA Telnet on MS-DOS & MS-Windows PC's Overview To facilitate access to the campus Ethernet, you are being provided with basic commun-ications software, which is called NCSA Telnet. NCSA Telnet installation is performed by running the INSTALL utility on the NCSA Telnet distribution diskette. NCSA Telnet installation performs two basic functions: 1) the Telnet software is loaded onto your hard disk and your AUTOEXEC.BAT is modified; 2) your computer is registered by the C&C Network Operations facility in the Academic Computing Center and assigned a unique IP address which is necessary when connecting to the Ethernet. IP (Internet Protocol) addresses are required on Ethernet networks which use the TCP/IP network protocol. IP addresses are unique. No two computers may have the same IP address. If two machines have the same IP address, connections will fail. There is nothing you need to do with your IP address. You might write it down and tape the number on your computer. But you will never need to remember the number when connecting to the Ethernet because it is stored in a file (CONFIG.TEL) located in your newly created NCSA Telnet directory (\NCSA). After installation is completed, you can now use the basic suite of tools (telnet and ftp) to connect to the campus network. Installing the NCSA Telnet software If you have NCSA Telnet on 5-1/4 inch media, there are three separate diskettes. On 3-1/2 inch media there are two diskettes. For 3-1/2 inch media, insert the disk labelled "Distribution Diskette" into the A drive. For 5-1/4 inch media, insert the disk labelled "Distribution Diskette #1" into the A drive. Make the A drive your default drive by typing: C:\> A: <Enter> From the A: prompt, type INSTALL to begin the installation process: A:\> INSTALL <Enter> Initial Telnet Install Screen The first screen you see will look something like this: University of Washington Networks and Distributed Computing NCSA Telnet Installation Utility, v2.0 <additional text> Press any key and the program will respond that it is "initializing". This process can take anywhere from several seconds to two minutes, so please be patient. Selecting the Interface Driver When the initialization process has been completed, you will be asked to select an interface driver. The preferred Ethernet network interface cards at the University of Washington are made by 3Com, the largest manufacturer of Ethernet adapters for PC's. There are four models of 3Com boards: Model # Model Name Description 3C503 - Etherlink II 8-bit and 16-bit ISA bus 3C507 - Etherlink-16 16-bit ISA bus 3C509 - Etherlink III 16-bit ISA bus 3C523 - Etherlink/MC 16-bit MicroChannel bus (MCA) Use the down-arrow key to highlight the interface driver which matches the model number of your Ethernet card. Then press the <Enter> key to select your choice. Identifying Current Settings for Your Ethernet Board After selecting the interface driver, you will be prompted with the following question: Use the default Ethernet settings (IRQ3, I/O 300h) <y/n> ? Currently, default settings for NCSA Telnet are IRQ3 (interrupt 3) and I/O 300h (base i/o address of 300 hex). NCSA Telnet installation does not assign values for shared memory or DMA. These values are acquired directly from the Ethernet board. Factory settings for the 3Com Ethernet boards will vary. The factory settings are as follows: 3C503: IRQ 3, Base I/O 300h, Shared Mem Disabled 3C507: IRQ 3, Base I/O 300h, Shared Mem D000:0 3C509: IRQ 10, Base I/O 300h 3C523: IRQ 3, Base I/O 300h, Shared Mem C000:0 Use the default Ethernet settings (IRQ3, I/O 300h) <y/n> ? Y <Enter> Please also note that IRQ3 corresponds to COM2 on your PC. If you have two serial ports or is you have an internal modem you will want to use IRQ5 (which corresponds to LPT2:) instead of IRQ3, so you will press "N" to change the default settings. Host Information Next, you are presented with a screen requiring you to enter "host information". In this case, the "host" refers to your PC. Information entered here (your name, building, address, etc) is loaded into a database to provide a resource for future network support. You will be given an opportunity to change the information you have entered if you are unsatisfied with any of your responses. Enter your full name and phone number. If you already have an account on a C&C Uniform Access computer, you will have an e-mail address which is your login name (userid) followed by u.washington.edu. For example: firstname.lastname@example.org The address should be your building address and room number. Architecture refers to the type of computer. For IBM PS/2's (models 55, 70, 80, 90, 95), the architecture is MCA (Micro Channel Architecture). Most other computers are ISA (Industry Standard Architecture). When specified, some computers are EISA (Extended Industry Standard Architecture). For operating system, ideal responses would be, for example, MS-DOS, or MS-Windows. If you are dissatisfied with any of your responses, answer "Y" to the question "Would you like to change anything <y/n> ?". Arrows will point to the first entry block on this screen (Name). Use the down arrow key to select the entry block you wish to modify> "Would you like to change anything <y/n> ?" Y <Enter> > Name: Ken Griffey < Phone: 543-0000 E-mail address: email@example.com Submitting IP Address Request After all host information is entered to your satisfaction, the installation program is responds with the following screen: Submitting IP Address Request In order to determine a new IP address, this PC MUST be connected to the campus network. Please verify that it is connected. Is this PC connected <y/n> ? The installation program is now ready to query the network in order to assign a unique IP address to your computer. In order for you to receive an IP address, your computer must be connected to the campus network. In other words, your Ethernet card must be installed in your computer and your Ethernet cable must be connected from your computer to the Ethernet port in your office. If your computer is not connected to your Ethernet port, this critical portion of the installation program will fail. Press "Y" when you are ready (do not press the <Enter> key) and the IP address assignment process will begin, taking up to 60 seconds before you receive you IP address. Is your PC connected <y/n> ? Y Default Setup for NCSA Telnet If the IP address assignment process completes successfully, you will see the following screen: University of Washington Networks and Distributed Computing NCSA Telnet Installation Utility, v2.0 Your new IP address is : xxx.xxx.xxx.xxx <more text> Do you want to use the default setup <y/n> ? If you do not see this screen and do not receive an IP address, please refer to the next section:When Things Go Wrong. You will be asked if you want to use default setup. Default setup does the following: 1. NCSA Telnet files are copied into a directory titled NCSA on your hard drive. 2. Your AUTOEXEC.BAT file will be modified to include: a. NCSA in your search path. b. An environment variable CONFIGTEL which defines the path and file name of your NCSA Telnet configuration file. Enter "Y" (do not press the <Enter> key) to select the default setup option unless you wish to change the system defaults. Do you want to use the default setup <y/n> ? Y If you are using 5-1/4 inch diskettes, you will be prompted to insert Telnet Disk #2 before installation is completed. If you are using 3-1/2 inch diskettes, installation completes with the single disk. When installation is completed, you will see a couple screens of post-installation notes: INSTALLATION SUCCESSFUL <more text> Hit Any Key To Finish Press any key to complete installation. When Things Go Wrong Troubleshooting your Ethernet connection is a complex task, reserved for advanced users. The following instructions are geared for advanced users and are therefore brief and to the point. If you have little experience troubleshooting computer problems, consult your departmental system administrator or department computer support person. The most common installation problem occurs when your computer attempts to make a request for an IP address assignment. This function is dependent upon: 1. a proper connection to the campus network 2. proper installation of your Ethernet card 3. proper configuration of AUTOEXEC.BAT and CONFIG.SYS files What to Do: Check the Connection The first thing you will want to do is check to see that your Ethernet card is working properly. Carefully check all cable connections. If connections are in order, check with Network Operations (543-5128) to make sure that you have an active Ethernet connection and that the IP server is accessible. What to Do: Run Diagnostics There are diagnostic utilities for your 3Com Ethernet cards provided on your NCSA Telnet distribution disk set. For 3-1/2 inch media, Ethernet diagnostics are located on the disk labelled "3Com Diagnostics Disk". For 5-1/4 inch media, the diagnostics utilities can be found on the disk labelled "Distribution Diskette #3". Before running diagnostics, you will want to rename your AUTOEXEC.BAT and CONFIG.SYS files and reboot your computer: C:> REN AUTOEXEC.BAT AUTOEXEC.SAV C:> REN CONFIG.SYS CONFIG.SAV When the computer has completed rebooting, insert the diskette with your 3Com Diagnostics in drive A. Each 3Com Ethernet board has its own diagnostic utility. The program files are listed below: 3C503.EXE - Etherlink II diagnostics 3C507.EXE - Etherlink-16 (thin Ethernet) diagnostics 3C507TP.EXE - Etherlink-16 (twisted pair) diagnostics 3C509.EXE - Etherlink III diagnostics 3C523.EXE - Etherlink/MC (thin Ethernet) diagnostics 3C523TP.EXE - Etherlink/MC (twisted pair) diagnostics These diagnotic utilities can be downloaded from ftp.cac.washington.edu via anonymous ftp. For example, to download 3C509.EXE, you would do the following: C:\> md 3com C:\> cd 3com C:\3COM> ftp ftp.cac User: anonymous Password: <your user id> ftp> cd msdos/3com ftp> bin ftp> get 3c509.exe ftp> quit Before running these diagnostic utilities, be sure to rename AUTOEXEC.BAT and CONFIG.SYS then re-boot. Diagnostics can cause the computer to freeze if network drivers are loaded prior to use. C:\> REN AUTOEXEC.BAT AUTO.SAV C:\> REN CONFIG.SYS CONFIG.SAV Run the diagnostic utility which matches your 3Com Ethernet board. For example, if you have a 3C503 Etherlink II network card, at the A:> prompt, type 3C503 and press <Enter>. A:> 3C503 <Enter> You may see a menu with a "Test" option, or you may see a screen something like the following: 3Com Etherlink Diagnostics Version x.x <more text> Press Any Key to Continue Press any key to see the Diagnostics menu. Select the option Diagnostics Tests.. Typically there are three groups of tests: Group 1: Internal Testing of Adapter Group 2: Network Testing of Adapter Group 3: Echo User Testing of Adapter Select Group 1. Tests should complete quickly. If the board passes the test, proceed to Group 2. Do not perform Group 3 tests. Exit the diagnostics program and rename your AUTOEXEC.BAT and CONFIG.SYS files: C:> REN AUTO.SAV AUTOEXEC.BAT C:> REN CONFIG.SAV CONFIG.SYS If all tests have pass, then your Ethernet board is functioning properly. If the diagnostics fail, you either have a faulty Ethernet board, or there is a resource conflict between the Ethernet board and some other device in your computer. The most common resource conflict is the interrupt. For the 8-bit 3C503 card, try reconfiguring your Ethernet board for IRQ-5 and see if that solves the problem. For the 16- bit 3C503, 3C507 or 3C509, try using IRQ-10. If changing the interrupt does not solve the problem, try changing the Shared Memory Address where applicable. If this does not solve the problem, try using another Ethernet board of the same variety in your computer. For the 3C523, resources are automatically configured from your IBM Reference diskette to automatically avoid resource conflicts. If the 3C523 board fails diagnostics, the board needs to be replaced. What to Do: Check Drivers If your Ethernet card passes diagnostics, the next possible problem is a conflict with drivers designated in your CONFIG.SYS and AUTOEXEC.BAT files. The most common driver conflict occurs with the EMM386.EXE memory manager which allows drivers to be loaded in high memory. Many Ethernet adapters (most notably the 3Com 3C503) use high memory to buffer Ethernet packets. The EMM386.EXE driver most be configured to exclude memory used by your Ethernet adapter. For example, the recommended memory setting for the 3c503 is CC00:0. To exclude the memory area from use by EMM386.EXE, your would set up the driver in the following way: DEVICE=C:\DOS\EMM386.EXE X=CC00-CCFF When All Else Fails ! If you are still having problems, you may call Information Systems (543- 3531) to get further assistance with your PC. APPENDIX A: INSTALL <options> -help Displays the command line usage. -sync Synchronize configuration switch. Install, if connected, sends a request to the Automatic IP Address Assignment Daemon, updates the IP address in the 'config.tel' file and updates the serial number associated with that file. No other parameters in the configuration file are over-written. -defaults Default installation switch. Automatically installs Telnet using default settings (ie. placing all relevant files in the 'c:\ncsa' directory and creating the vanilla configuration). The user is still prompted for the NIC model number. -unconnected Unconnected to the network switch. Installs Telnet without sending an automatic IP address request or trying to determine local sub-net address. For use on a PC that is yet unconnected to the campus network. -n No validation of the given IP address is performed. If this option is not set, the IP address given on the command line is checked for correct format and that it is an address on the known University of Washington campus. ipaddress If ipaddress is a valid IP address, install uses ipaddress for the installation process. APPENDIX B: Running NCSA Telnet With Other Network Software NCSA Telnet can be used with other network applications. The Ethernet driver which is loaded prior to NCSA Telnet, known as the Clarkson packet driver (aka Crynwr packet driver) can support multiple network protocol stacks with network applications running on top of each protocol stack. But there are restrictions. NCSA Telnet cannot run concurrently with other TCP/IP applications (TCPIP is embedded in NCSA Telnet and cannot be shared). Examples follow. Running NCSA Telnet with Novell NetWare NCSA Telnet can easily coexist because NetWare does not use the TCP/IP network protocol. Therefore, NetWare uses one protocol stack (known as IPX) and NCSA Telnet uses another (TCP/IP). Both protocol stacks run on top of the packet driver. A special version of the IPX driver (called PDIPX.COM) is compatible with the packet driver and therefore supports concurrency with NCSA Telnet. Sample AUTOEXEC.BAT: c:\ncsa\3c503 -w 0x66 3 0x300 (load the packet driver) c:\ncsa\pdipx (load the pd version of ipx) c:\netware\netx (load the NetWare shell) Running NCSA Telnet with Microsoft Windows for Workgroups: NCSA Telnet can run concurrently with Windows for Workgroups, because NCSA Telnet and Windows for Workgroups use different network protocols. NCSA Telnet uses TCP/IP protocol, whereas Windows for Workgroups uses Microsoft's NetBEUI. For a full explanation concerning NCSA Telnet and Windows for Workgroups, you can download the file telnet.wfw from ftp.cac.washington.edu via anonymous ftp: C:\> ftp ftp.cac User: anonymous Pass: <your user id> ftp> cd msdos/ndis ftp> get telnet.wfw ftp> quit Running NCSA Telnet and PC-Pine NCSA Telnet and PC-Pine both use the TCP/IP network protocol. They can both run on top of the Clarkson packet driver using separate TCP/IP protocol stacks as long as they are not run concurrently. This does not pose a major problem because the functions of the two programs overlap and the need for simul- taneous operation is not likely to be great. Running NCSA Telnet with NFS or X-Windows NFS and X-Windows are both built on top of the TCP/IP network protocol, and can therefore not be run concurrently with NCSA Telnet. A special exception is Sun Microsystem's PC-NFS, which can be made to run with NCSA Telnet by loading two TCP/IP protocol stacks. This is a rather unorthodox solution, but more information can be obtained by downloading pktmux.zip from ftp.cac.washington.edu: C:\> ftp ftp.cac User: anonymous Pass: <your user id> ftp> cd /msdos/utils/PCNFS ftp> bin ftp> get pktmux.zip ftp> quit APPENDIX C: Running NCSA Telnet With Microsoft Windows When MS-Windows 3.0 was introduced it was easy to set up icons to run your favorite DOS applications within Windows. NCSA Telnet, however, would consistently crash Windows when set up this way. As it turned out, the Clarkson packet driver, which is required to run NCSA Telnet, had to be re-designed to allow NCSA Telnet to run in Windows. The design modification (first implemented in the Clarkson packet driver release 7.3) is not trans- parent. It requires that an additional parameter (the -w switch) be added to the packet driver command. The packet driver command is added to your AUTOEXEC.BAT file when NCSA Telnet is installed on your PC. Below is a sample packet driver command found in AUTOEXEC.BAT as created by the Install program with the -w switch for rudimentary MS-Windows compatibility: C:\NCSA\3C503 -W 0X66 3 0X300 Running NCSA Telnet in Windows Enhanced Mode In MS-Windows Enhanced Mode, it is possible to run muliple DOS appli- cations concurrently. If you wish to run NCSA Telnet concurrently with such DOS applications as MS-Word, Word Perfect or Lotus 1-2-3, MS-Windows will need to run in Enhanced Mode. An additional patch is required to let NCSA Telnet run in MS-Windows Enhanced mode. This patch is called winpkt.com. The winpkt command must be added to your AUTOEXEC.BAT subsequent to the packet driver command to set up NCSA Telnet for Windows Enhanced Mode: C:\NCSA\3C503 -W 0X66 0X300 C:\NCSA\WINPKT 0X60 0X66 NCSA Telnet Performance Problems in MS-Windows Using the PIF Editor, it is possible to create a telnet.pif file to provide additional customizations to your NCSA Telnet application. One of those modifications is to run NCSA Telnet in Window mode versus full-screen mode. Window mode is convenient because you can more easily switch between Telnet and other applications with the point and click of the mouse on the apporpriate Window. However, some people have noticed signicant performance problems when running NCSA Telnet in a Window. If you experience this, performance should return to normal by switching NCSA Telnet back to full-screen mode. Minimizing NCSA Telnet in MS-Windows If you choose to minimize (iconize) NCSA Telnet or leave NCSA in the background for more than a few minutes at a time, you may find that when returning to your NCSA Telnet application that you have lost your connec- tion. This problem can be rectified by making modifications to your telnet.pif file using the MS-Windows PIF Editor. A sample telnet.pif file is installed in the c:\ncsa directory.
Pages to are hidden for
"install"Please download to view full document