Path: utzoo!attcan!uunet!nih-csl!lhc!mimsy!haven!uflorida!rex!wuarchive!zaphod.mps.ohio-state.edu!rpi!uupsi!sunic!news.funet.fi!tukki.jyu.fi!jyu.fi!otto From: otto@tukki.jyu.fi (Otto J. Makela) Newsgroups: comp.dcom.lans Subject: Re: 3COM 501 and NCSA telnet/ftp Message-ID: Date: 10 Oct 90 10:07:36 GMT References: <650@tron.UUCP> Sender: news@tukki.jyu.fi (News articles) Organization: Turing Police, Criminal AI section Lines: 49 In-Reply-To: kerr@tron.UUCP's message of 7 Oct 90 00:18:35 GMT In article <650@tron.UUCP> kerr@tron.UUCP (Dave Kerr) writes: [in reply to my article on 3C501's being atrociously slow in ftp] There are a couple of parameters in the config.tel file that you'll want to change. Read thru the file, they specifically mention the 501 card. The parameters have something to do with the packet size that's transmitted. I don't have the info in front of me so I can't give you the exact details. I remember that our sizes were something like 2k or 4k. We changed them to 512. Our transfer rates jumped from about .2-20kBytes/sec to consistantly above 20kbytes/sec. Hum, my NCSA 2.2DS config.tel doesn't say anything special about 501's. I assume you mean the following parameters (from my current config.tel): retrans=1 # starting retransmit time out in ticks # 1/18ths of sec MAX 100, min 1 mtu=512 # maximum transmit unit in bytes # outgoing packet size, MAX=1500 maxseg=4096 # largest segment we can receive # whatever the hardware can take, MAX=4096 rwin=4096 # most bytes we can receive without ACK # =TCP window size, MAX=4096 contime=20 # timeout in seconds to try connection # before returning error to user I tried making maxseg and rwin smaller (since they should be hardware- dependant), but it didn't help. To re-iterate: I have a couple of old 3COM 501's, and am trying to get some use out of them with NCSA Telnet/ftp 2.2DS (this is the version with national character set support). Telnet works well, as does the separate ftp program, but if I do a telnet and then do a ftp back to my pc from the host, I get truly awful performance. Something under 1k/second. I've tried the NCSA built-in 501 driver, the latest (well, three weeks old) Clarkson packet driver and both internal and external trancievers. I know the card is old and definitely not top-of-the-line in performance, but I'd like to make them work, otherwise we'll use them for skeet practise or something... I also have a problem with *not* having the manuals for this, so I'm not sure if I have some kind of a hardware problem (bus contention or something), but I doubt it (it shouldn't work at any speed ?). Come on, someone HAS to have made them work. What am I doing wrong ? -- /* * * 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 * * * * * * * * * * * * * * * * */