[mod.protocols.tcp-ip] problems reaching cu20b

BLARSON@USC-ECLB.ARPA.UUCP (06/06/86)

I frequently have problems trying to get files from cu20b.columbia.edu
using ftp from either usc-eclb.arpa (milnet) or usc-oberon.arpa
(arpanet).  Tops-20 ftp (usc-eclb.arpa) gives the message "connection
rejected for unknown reason" and 4.2bsd ftp (usc-oberon.arpa) gives
the message "network unreachable".   (This is the second night in a row
this week, and I have had similar problems before.)  I have also had
many mail messages returned with "system unreachable" after three days
through both usc-ecl.arpa (milnet) and usc-eclc.arpa. (arpanet)  (both
Tops-20)

Apparently cu20b.columbia.edu (also a tops-20 machine) has no problems
sending mail to us, we get the info-kermit digest regularly.  Neither
the local postmaster or the info-kermit people seem to know a reason
for this problem.

Where is the proper place to report this type of problem?

Are other people experiencing it to?

Mail can be gotten through by routing via other systems.  (I used to
use columbia.arpa, but it no longer understands the % hack and I
haven't figured out out to specify an @host1:user@host2 address to
tops-20 mm.)  For ftp, I just keep trying until it decides to work.

Bob Larson <Blarson@Usc-Ecl.Arpa>
-------

melohn%sluggo@SUN.COM (Bill Melohn) (06/06/86)

Chances are good that the network which cu20b is on has fallen out of
the limited size EGP reachablity table that you (or more likely your
core gateway) use. This appears to happen to our non-backbone network
every once in a while.  The solution is to get more powerful core
gateways that implement EGP and provide more space for the ever
increasing numbers of non-backbone internet networks. If access to cu20b
is really important to your site, you might consider adding the entry
for the columbia gateway to ECLx's INTERNET.GATEWAYS file. That way you
will not have to ask your core gateway how to get to cu20b.  

Bill