Path: utzoo!utgpu!watmath!clyde!att!rutgers!deimos!uxc!uxc.cso.uiuc.edu!uxg.cso.uiuc.edu!uxe.cso.uiuc.edu!krauskpf From: krauskpf@uxe.cso.uiuc.edu Newsgroups: comp.protocols.appletalk Subject: Re: NCSA Telnet Message-ID: <66000028@uxe.cso.uiuc.edu> Date: 1 Dec 88 23:50:00 GMT References: <1411@aucs.UUCP> Lines: 40 Nf-ID: #R:aucs.UUCP:1411:uxe.cso.uiuc.edu:66000028:000:1537 Nf-From: uxe.cso.uiuc.edu!krauskpf Dec 1 17:50:00 1988 NCSA Telnet 2.2 runs without any undue pauses and freeze-ups for most sites without any problems. There are no known bugs which cause hangs or crashes during normal use after you have connected. I can't think of anything which you can configure which will cause a crash if you can at least get connected. So, suggestions when you get interrupted service: 1. Is anyone using your IP number? If you sometimes work for hours without a problem, but sometimes can't stay connected, check to see if someone else in the office has the same problem. They may have the same number that you do. Everyone must have a unique IP number. (Show Network Numbers from the Network menu) 2. Tuning. For AppleTalk and for a safe test, make sure your configuration file has these settings: rwin=512 ; mtu=512; maxseg=512 3. Check that you aren't running Pyro or other screensaver which will cause timeouts to occur after 3 minutes on most Unix systems. 4. Always check for conflicts with network INITs or mail programs. Don't run with Kinetics' or Apple's TCP drivers installed unless you know that there is no conflict on your system. If you are sure you checked, please send me your System version number, system 5.0 or 6.0.2, or other. Also make sure to indicate what kind of Ethernet board, FastPath and FastPath gateway software you are using. If there are any patterns to these problems, I may be able to find a solution. Send bugs/problems to telbug@ncsa.uiuc.edu Tim Krauskopf NCSA timk@ncsa.uiuc.edu