Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!uunet!mdisea!jackb From: jackb@MDI.COM (Jack Brindle) Newsgroups: comp.sys.mac.comm Subject: Re: Message-ID: <1991Apr5.173128.6595@MDI.COM> Date: 5 Apr 91 17:31:28 GMT References: <1991Mar27.174714.9902@cc.newcastle.edu.au> Sender: news@MDI.COM Organization: Motorola, Mobile Data Division - Seattle, WA Lines: 26 In article <1991Mar27.174714.9902@cc.newcastle.edu.au> cegrw@cc.newcastle.edu.au writes: >I have aproblem with MacTCP/NCSA Telnet combination which we have been >unable to figure out (neither can NCSA help). I can connect to plenty >of machines within Aust. but none overseas (i.e. US) The problem seems to be >with the response time. Machines overseas typically take about 6-10 secs >to respond by which time MACtcp has timed out (we checked this by pinging >sites from the campus mainframe). In the CONFIG.TEL file the comments >indicate that the timeout parameter is ignored for the MacTCP version of >NCSA Telnet and that does seem to be the case. SO ... does MacTCP have the >timeout period hard coded into it ... Garry (et al); Yes, timeouts are configurable within TCP. In fact, you must either set the specific time delay, or accept Apple's defaults. Obviously, Telnet chose the default. I believe the source to Telnet is available. It should be relatively easy to add the ability to set this parameter (as is done in the internal driver version). A copy of the MacTCP development notes (from APDA - but expensive [$100]), would be required... > and if so were Apple stupid enough to set it at 5 secs? No, the NCSA folks were stupid enough to accept the defaults :-). You were unfortunate to get caught by them. By the way, they are also too short if you try to pump ip packets across a packet radio channel... (Now you know why I know about the timeout parameters :-). - Jack Brindle ham radio: wa4fib