Path: utzoo!attcan!uunet!jarthur!usc!ucsd!ames!dftsrv!nssdca.gsfc.nasa.gov!lanmaint From: lanmaint@nssdca.gsfc.nasa.gov (Dave Yoest) Newsgroups: comp.dcom.lans Subject: Re: 3COM 501 and NCSA telnet/ftp Message-ID: <3592@dftsrv.gsfc.nasa.gov> Date: 10 Oct 90 14:58:37 GMT References: <650@tron.UUCP> Sender: news@dftsrv.gsfc.nasa.gov Reply-To: lanmaint@nssdca.gsfc.nasa.gov Organization: NASA - Goddard Space Flight Center Lines: 49 News-Software: VAX/VMS VNEWS 1.3-4 >In article , otto@tukki.jyu.fi (Otto J. Makela) writes... >>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. > > [ body Otto's post deleted ] >Come on, someone HAS to have made them work. What am I doing wrong ? >-- Try this, direct fom the NCSA docs file..... The setting required for the 3com 3C501 and any other troublesome network situation, also the most conservative setting is: RWIN=512 MTU=512 MAXSEG=512 Have you tried this? The "clay pigeon" idea also has it's merit..... Dave Yoest NASA Goddard Space Flight Center LAN Section Supervisor DYOEST@128.183.4.5