Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!wuarchive!uwm.edu!rpi!uupsi!sunic!dkuug!imada!news
From: sms@dou.dk (Sven Meiborg Sorensen)
Newsgroups: comp.protocols.appletalk
Subject: Re: MacTCP feature!
Message-ID: <1991Feb15.073631.21323@imada.dk>
Date: 15 Feb 91 07:36:31 GMT
References: <4187@cernvax.cern.ch>
Sender: news@imada.dk (USENET News System)
Reply-To: sms@dou.dk (Sven Meiborg Sorensen)
Organization: Dept. of Math. & Computer Science, Odense University, Denmark
Lines: 26

jmg@cernvax.cern.ch writes:
> We have recently been having trouble with Macs running NCSA telnet
> being unable to connect off-site. It turns out that it is only those
> using MacTCP, and seems to be a MacTCP weakness.
>
> The problem seems to be when odd workstations are configured (wrongly)
> to run the route daemon, so they broadcast the (wrong) fact that they
> are routers. Most other systems which are set up to know the gateway
> address for getting to other networks ignore these broadcasts. MacTCP,
> however, decides to use these new router addresses instead of the one
> that we have carefully configured in them.
>
> Could there be a new MacTCP version which fixes this?

We have seen the same problem and reported it to Apple. Apple
responded promptly and admitted to an error in MacTCP 1.0 and 1.0.1.
The odd router-problem will be fixed in MacTCP 1.1 which
is due out somewhere in the April to May timeframe, according to
John Veizades at Apple.
In the meantime: turn off the routing capability of the offending
workstations or mainframes - if possible!

Sven--
Sven Meiborg Sorensen     Internet: sms@dou.dk
Senior Analyst
Odense University, Denmark