Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83; site cheviot.UUCP Path: utzoo!watmath!clyde!burl!ulysses!allegra!bellcore!decvax!genrad!mit-eddie!godot!harvard!seismo!mcvax!ukc!cheviot!andy From: andy@cheviot.UUCP (Andy Linton) Newsgroups: net.lan Subject: Strange Ethernet Behaviour Message-ID: <235@cheviot.UUCP> Date: Fri, 18-Jan-85 08:38:43 EST Article-I.D.: cheviot.235 Posted: Fri Jan 18 08:38:43 1985 Date-Received: Tue, 22-Jan-85 04:56:13 EST Expires: Thu, 31-Jan-85 20:00:00 EST Reply-To: andy@cheviot.UUCP (Andy Linton) Distribution: net Organization: U. of Newcastle upon Tyne, U.K. Lines: 28 We are running two 11/750's under 4.2BSD connected by Ethernet. The Ethernet kit is all DEC - DEUNA's, H4000's and DEC cable. We also have four Perq's on the same Ethernet using 3Com transceivers. The Perq's talk ECMA Transport Service protocols and so at present don't talk to the Vaxen. We have been running this setup happily for several months with no apparent problems - until yesterday! Vax to Vax communication stopped - no rlogin rwho or rsh commands worked, ruptime reported that both machines were down. This behaviour was the same on both machines. The Perq's also stopped talking to each other. We split the Ethernet cable to give us a Vax net and a Perq net. The Vaxen picked up straight away - things in the print queue of one started printing out on the other. The Perqs took rather more fiddling to restart - reboots and cable waggling. Has anybody any explanations or advice to offer (by mail please and I'll summarise to the net) Thanks Andy ---- Aindrias Mac Giolla Fhionntain - Computing Lab., U of Newcastle upon Tyne ARPA : andy%cheviot%newcastle.mailnet@MIT-MULTICS.ARPA UUCP :!ukc!cheviot!andy