Xref: utzoo comp.sys.mac.comm:3268 comp.protocols.appletalk:5671 Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sdd.hp.com!spool.mu.edu!munnari.oz.au!mel.dit.csiro.au!latcs1!wcc!tom From: tom@wcc.oz.au (Tom Evans) Newsgroups: comp.sys.mac.comm,comp.protocols.appletalk Subject: Re: Async AppleTalk and MacTCP Message-ID: <1689@wcc.oz.au> Date: 11 Apr 91 04:55:13 GMT Article-I.D.: wcc.1689 References: <1991Apr5.180750@ap.co.umist.ac.uk> Followup-To: comp.protocols.appletalk Organization: Webster Computer Corp, Melbourne, Australia Lines: 45 Please ignore any previous non-Cancelled versions of this posting. In article , kre@cs.mu.OZ.AU (Robert Elz) writes: > jf@ap.co.umist.ac.uk (John Forrest) writes: > > >Anyway, MacTCP is quite happy in selecting the Async > >network icon. It does ask for which zone though - what affect does this have? The zone you have to select is the zone that MacTCP looks in to find its MacIP gateway - so you can have one centralised MacIP gateway performaing the address assignment and gateway functions. > >Anyway, the system doesn't fall over, but I get no response from anywhere. I > >suspect I have to fit some routing up. > > No - the problem is that there's no way to get the multigate to assign > an IP address for an async node (yet, this may happen some day), as the > async node appears to be on a remote network connected over IPtalk, which > isn't something that an IPGATEWAY will normally ever assign addresses to. I have managed to do this OK. You need one MPG (MultiPort Gateway) performing the Async services, and a second one providing MacIP services out one of its EtherTalk ports, but with IPTalk disabled. You then select the the appropriate EtherTalk zone (that the second one is in) in MacTCP. Now the bad news - it still doesn't work. The combination of MacTCP and NCSA Telnet expects to be on a fast, rapid, LOCAL network, and the timeouts that NCSA selects can't handle the Async speed (or lack thereof). It nearly works at 9600, but not quite. Maybe not even at 19,200 - I gave up there. If you can run 19,200, you can usually run LocalTalk over the same physical path (so why bother with async?). You want it to work at 2400. This is a general problem with NCSA and MacTCP, as the TCP timeouts won't even let it work across the Pacific on a fast net. I would expect it to fail over slower SLIP and Ether half-bridges too. A posting from jackb@MDI.COM (Jack Brindle) on comp.sys.mac.comm dated 5 Apr 91 17:31:28 GMT gives better details on the timeouts. ======================== Tom Evans tom@wcc.oz.au ** ADD ".au" MANUALLY (don't trust "reply") ** Webster Computer Corp P/L, 1270 Ferntree Gully Rd Scoresby, Melbourne 3179 Victoria, Australia 61-3-764-1100 FAX ...764-1179 A.C.N. 004 818 455