Brian Kantor (firstname.lastname@example.org)
13 Jan 88 05:36:14 GMT
I can't ping SEISMO.CSS.GOV from our host 'SDCSVAX.UCSD.EDU' at
22.214.171.124. I can ping SEISMO quite nicely from our neighbor on the same
IMP (NOSC.MIL at 126.96.36.199). We are both using the same default gateway
at 188.8.131.52, which seems to be the way the packets are going.
I guess that SEISMO could have different routes back to SDCSVAX than they
do back to NOSC, but I don't know WHY they'd have them, since we're both
on the same IMP.
SEISMO isn't an isolated case - I can't ping any of the following hosts
from SDCSVAX, but I can from NOSC:
There are others. And there are hundreds of mail messages waiting in
our queue because we can't get to their nameservers to get delivery
addresses. (There ARE hosts on network 10 that I can ping, btw, such
I called the Milnet NOC, and they seemed to think that it's a core
gateway problem and told me to call BBN. BBN assures me that they were
already working on the problem - seems that they see a problem with one
of the gateways, but I don't know what that problem would be.
I'd like to understand what's going on, as well as get it fixed. The
only thing I can think of is that NOSC is connected to the IMP with
1822, and we're connected with X.25, but don't quite see how that would
make a difference either. NOSC is running EGP for our 128.54 network,
so I don't think that's the problem - if indeed that is even relevant,
since we're dealing directly with network 26 source addresses in the
Oh yeah, we've been having this sort of problem since Friday. I'm not
sure it's always the same hosts.
I'm stumped. Anybody got any ideas?
UCSD Office of Academic Computing
Academic Network Operations Group
UCSD B-028, La Jolla, CA 92093 USA
email@example.com (619) 534-6865
This archive was generated by hypermail 2.0b3 on Thu Mar 09 2000 - 14:40:40 GMT