Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!julius.cs.uiuc.edu!apple!snorkelwacker!bloom-beacon!eru!hagbard!sunic!news.funet.fi!tukki.jyu.fi!jyu.fi!otto From: otto@tukki.jyu.fi (Otto J. Makela) Newsgroups: comp.dcom.lans Subject: 3COM 501 and NCSA telnet/ftp Keywords: What are we doing wrong ? Message-ID: Date: 5 Oct 90 09:46:10 GMT Sender: news@tukki.jyu.fi (News articles) Organization: Turing Police, Criminal AI section Lines: 19 We have a couple of old 3COM 501's, and we've tried to get them to work with NCSA telnet 2.2DS (that's the one with national character extensions -- I know it's somewhat old, but haven't seen newer versions with this feature). Telnet works perfectly, but when you try to use ftp, it's atrociously slow. Something under 1k/s ! We've tried the NCSA internal 501 driver, the latest Clarkson packet driver, with direct thin connection, with external tranciever, just about every IRQ/IO/mem setting... We'd really like to see this work, since otherwise the old cards become fish- bait. The same software versions have successfully been used with WD8003 and 3C503 cards. What are we doing wrong ? PS. Can someone tell me the situation with NCSA telnet ? I've seen some ftp sites which say that NCSA has requested them to *remove* it. What's up ? -- /* * * Otto J. Makela * * * * * * * * * * * * * * * * * * */ /* Phone: +358 41 613 847, BBS: +358 41 211 562 (CCITT, Bell 24/12/300) */ /* Mail: Kauppakatu 1 B 18, SF-40100 Jyvaskyla, Finland, EUROPE */ /* * * Computers Rule 01001111 01001011 * * * * * * * * * * * * * * * * */