Path: utzoo!attcan!uunet!kddlab!trl!rdmei!ptimtc!olivea!apple!usc!sdd.hp.com!caen!uflorida!haven!decuac!pa.dec.com!granite.pa.dec.com!mellon From: mellon@fenris.pa.dec.com (Ted Lemon) Newsgroups: comp.unix.ultrix Subject: Re: DECNet-Ultrix 4.0 installation Message-ID: Date: 30 Nov 90 20:04:30 GMT References: <3016@dali> <1990Nov30.082642@energy.irc.cbm.dec.com> Sender: news@pa.dec.com (News) Organization: Digital Equipment Corporation Lines: 25 >Now, as far as starting DECnet goes, I have gotten it to work in that >configuration by running ifconfig to start IP, mounting /usr and then >using ncp to start DECnet. I'm not sure why this works in the face of >the changing Ethernet address [...] The reason that Jaye's system froze completely was that both the DS5000 and the DS3100 had the same ethernet address, meaning that neither one could tell the difference between the other, and meaning that both would respond to requests from any machine on the net directed at the DS5000. In the 3100's case, it would probably respond to its own nfs requests with a message on the order of ``What in the blue blazes are you talking about???''. Major lossage. It's also possible that the IP code would hang in some less obvious way - I don't know enough about the guts of it to know for sure. Once you've fixed the problem of both machines having the same ethernet address, you're left with the problem that the data in the DS5000's arp cache is incorrect. This will fix itself fairly quickly, and the symptom will just be a long delay on the boot procedure on the 3100. _MelloN_