NIC@SRI-NIC.ARPA (DDN Reference) (12/02/87)
A meeting will be held on Thursday, December 3, to furthur discuss the new ARPANET End-to-End protocol (PSN 7.0). Due to necessary software patches, 2 test period options are being considered: 1) Testing of the new End-to-End on two week-ends, December 5th and 6th, and December 12th and 13th for a total of 4 days. 2) Testing of the new End-to-End beginning December 5th running through December 13th, for a total of 9 days. Hosts experiencing problems during this test period are asked to call the ARPANET Monitoring Center at (617) 873-3571/3070 or (800) 492-4992. -------
NIC@SRI-NIC.ARPA (DDN Reference) (12/08/87)
Testing of the new ARPANET End-to-End Protocol resumed on Saturday, December 5th and will continue running through Sunday, December 13th. Most problems have been fixed and/or identified. Those problems that have been identified are awaiting software patches. Hosts experiencing problems during this test period are asked to call the ARPANET Monitoring Center at (617) 873-3571/3070 or (800) 492-4992. -------
esj@beach.cis.ufl.edu (Eric S. Johnson) (12/09/87)
Forgive me if this question is obvious, but Im not very knowledgable about routeing issues. During the recent ARPANET testing (12-5 to 12-13) I have noticed strange behavior in the internet. We are a SURANET/NSF net site here and during the testing, I find I am not able to connect to many hosts that are within LAN's that are gatewayed on to the ARPANET proper. Yet I am able to make connections with hosts actually on the ARPANET. For example, some mail has been sitting in our mailq here waiting to be delivered to violet.berkeley.edu. No connection can be made to that machine, but a connection can be made to ucbvax.berkeley.edu and ucbarpa.berkeley.edu. I know violet is up becuase a finger @violet.berkeley.edu@ucbarpa.berkeley.edu happily lists the users. This is only one example; many other sites that are gatewayed via a 10.*.*.* are not reachable directly, but via finger @host@arpahost I am able to confirm that the host is up and running. It seems to me (and my armchair tests) that some routeing information is getting lost somewhere. Everything was fine, and I none of these problems, before last saturday (12-5). Also, I have no problem reaching other NSFnet sites. Would someone care to fill me in on the details. Is this problem seen from only our LAN here? Have others noted this kind of problem? Is it limited to NSFnet or SURAnet? Thanks for any enlightenment. -- In Real Life: UUCP: ...ihnp4!codas!ufcsv!beach.cis.ufl.edu!esj Eric S. Johnson II Internet: esj@beach.cis.ufl.edu University of Florida "Your species is always dying and suffering" -Q
ruffwork@orstcs.CS.ORST.EDU (Ritchey Ruff) (12/11/87)
We are having the same problem here - before the new protocall went
into testing orstcs.cs.orst.edu and uwchem.acs.washington.edu could
talk directly to each other, now they can't (it's actually intermitent
but I have not been keeping that close a track of when the new
protocall is in/out). I can do a
finger @uwchem.acs.washington.edu@washington.edu
now and see uwchem, but directly to uwchem, which use to work ALL
the time, works less and less (and has not worked for the last week
that I know of).
Is this a problem with the new protocall ???
--ritchey ruff ruffwork@cs.orst.edu -or-
"It's against my programming ruffwork%oregon-state@relay.cs.net -or-
to impersonate a deity" --C3PO { hp-pcd | tektronix }!orstcs!ruffwork