[comp.protocols.appletalk] Trouble with AIR and corrupt neighboring routers

ferriby@perot.com (John Ferriby) (12/13/90)

I have been experiencing difficulty with the Apple Internet Router and
I am wondering if a solution exists...

We have the Apple Internet Router operating on a Mac that operates in a common
area.  This Mac is directly attached to both an Ethernet and LocalTalk and it
only uses Phase II AppleTalk.  There are numerous other routers on this
Ethernet (it is a "bridged Ethernet environment"), mostly KFPs, GatorBoxes or
Ciscos.  When the Mac is rebooted, it regularly will not allow the AIR to
fire up because it (the AIR) detects that it's network number and zone name
parameters do not match correctly.  This is because one of the aforementioned
numerous routers has a corrupt routing table and is broadcasting the wrong
stuff.

If I go to the trouble [yucko!] of booting the Mac on an isolated Ethernet
(ie: put a terminator on the back of the Mac) and boot it AIR fires up just
fine. (of course) At that point when I re-establish the Ethernet connection
for the Mac everything is hunky-dory.

If I don't go through that trouble, AIR will not fire up.

My question [at last] is this: Is it possible to *force* the AIR to use it's
current data and to ignore the [mistaken] conflict?  I welcome code 
modifications, back-door or just plain RESedit type solutions.

-- 
John Ferriby

Perot Systems Corporation     Telephone: 1+313-641-3660
4555 Corporate Drive           Internet: ferriby@perot.com
Troy, MI 48098-6353                UUCP:  {uunet,decwrl,teemc}!perot!ferriby
#! rnews 1104
Path: p