Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!usc!apple!oliveb!orc!decwrl!shlump.nac.dec.com!michaud
From: michaud@decvax.dec.com (Jeff Michaud)
Newsgroups: comp.unix.ultrix
Subject: Re: DecNet-Ultrix / TCP-IP incompatability?
Keywords: DecNet TP IP
Message-ID: <8647@shlump.nac.dec.com>
Date: 23 Feb 90 22:16:19 GMT
References: <9479@portia.Stanford.EDU>
Sender: news@shlump.nac.dec.com
Organization: DEC
Lines: 21

> Help.   I have two dec3100s running ultrix.  One is a client of the
> other and they communicate via TCP/IP protocols.  I recently installed
> DecNet-Ultrix and found that the server no longer responded to NFS
> requests from the client.  My installation of DecNet was incomplete,
> i.e. I did not configure the nodes.  

	DECnet, when it is turned on, changes the hardware address on
	the ethernet device.  The other TCP systems however that your
	system was/are talking to however have the old ethernet address
	in their arp caches.

	DECnet does issue the ioctl to send out an arp delete request
	when it starts up.  Maybe in this case the client didn't
	see the arp message.  The arp entry in the clients cache should
	time out anyways I believe.  You can also do a manual "arp -d ..."
	on the client to remove it from the cache.

/--------------------------------------------------------------\
|Jeff Michaud    michaud@decwrl.dec.com  michaud@decvax.dec.com|
|DECnet-ULTRIX   #include <standard/disclaimer.h>              |
\--------------------------------------------------------------/