Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!utgpu!water!watmath!clyde!rutgers!husc6!bbn!uwmcsd1!ig!jade!ucbvax!ANDREW.CMU.EDU!te07+ From: te07+@ANDREW.CMU.EDU.UUCP Newsgroups: comp.sys.apollo Subject: Re: Apollo TCP/IP problems Message-ID: Date: Fri, 20-Nov-87 18:52:49 EST Article-I.D.: andrew.UVdAQ2y00WAB1aM08K Posted: Fri Nov 20 18:52:49 1987 Date-Received: Sun, 22-Nov-87 16:49:34 EST References: <388a01aa.bab@hi-csc.UUCP> Sender: daemon@ucbvax.BERKELEY.EDU Organization: The ARPA Internet Lines: 25 Flame on! I reported problems with this to 1-800-2APOLLO more than a month ago(yes we have a service contract). I am kind of ticked that I find out about a patch on this bboard rather than a phone call or better yet the patch arrives without any request at all. They should notify users/owners about bugs of this importance. Basically our Apollos have only been able to talk to a very small subset of the campus which is very limiting. In general, I have not been pleased with the TCP. Every other workstation seems to fit right into the campus network and can talk to everyone. Why can't the same be true of the Apollo? I have had similar problems with sendmail suddenly going crazy. How does this relate to routed? Does routed cause it or is it another bug? We no longer run either daemon because of these problems. Tom Epperly **************************************************************** te07@andrew.cmu.edu (ARPANET) te07%tb.cc.cmu.edu@cmuccvma.bitnet (BITNET) te07@tb.cc.cmu.edu (CCNET) te07%tb.cc.cmu.edu@csnet-relay te07#%andrew.cmu.edu@seismo.UUCP (UUCP) so I have been told ****************************************************************