Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!sdd.hp.com!ucsd!rutgers!netnews.upenn.edu!scotty.dccs.upenn.edu!tony
From: tony@scotty.dccs.upenn.edu (Anthony Olejnik)
Newsgroups: comp.protocols.appletalk
Subject: Re: MacTCP won't connect to hosts in other domains.
Message-ID: <34032@netnews.upenn.edu>
Date: 4 Dec 90 16:28:35 GMT
References: <1863loganj@yvax.byu.edu>
Sender: news@netnews.upenn.edu
Organization: University of Pennsylvania
Lines: 21


I, too, had a problem with MacTCP not being able to connect to host
in other domains.

It seems that even though I had a particular default gateway 
specified in MacTCP, it was listening to RIP packets and
using that info instead of the specified address of the IP router.

We use a single default IP Router as our default gateway and thus
do not use RIP.  All hosts on our campus should not be broadcasting
RIP packets.  However, some hosts were incorrectly configured and
were broadcasting RIP packets.

Usinging an ethernet monitor, it seems that the off campus (out of
domain) ethernet address was *NOT* our default IP gateway.  Rather
it was the ethernet address of a host that was incorrectly sending
RIP packets.  When the MacTCP packet (destined for off campus) was
received by the incorrectly configured host, it was discarded.


--tony


Brought to you by Super Global Mega Corp .com