Newsgroups: comp.sys.dec
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!cec2!news
From: krf@wucs1.wustl.edu (Kevin R. Fenster)
Subject: rarpd, lat, decnet, and IP
Message-ID: <1991May6.204154.21884@cec1.wustl.edu>
Sender: news@cec1.wustl.edu (USENET News System)
Organization: Washington University, St. Louis MO
Date: Mon, 6 May 91 20:41:54 GMT

Configuration:  DECsystem 5500, Ultrix 4.1, Xyplex Model 1400 printer
		server, LAT & DECnet configured and operational.

Problem:	The xyplex 1400 loads it's image and parameters
		across the network using rarp and tftp.  As usual,
		the 1400 sends out a rarp request with its ethernet
		address, and the 5500 is supposed to respond with
		the correct Internet address.  If I have rarpd running
		in verbose mode, I look in /usr/spool/mqueue/syslog
		and read all the startup messages.  As soon as rarpd
		receives a RARP request from the 1400, it logs it to
		syslog.  It also logs the fact that rarpd was able to
		determine the correct IP address. Then, when it appears
		that rarpd is trying to reply to the 1400, rarpd spits
		out an error message to syslog

/usr/etc/rarpd: Address family not supported by protocol familty write
to device failed.

		At the same time, an error messages appears on the
		console

		net_output: ne0: can't handle af3


		After these messages are displayed, rarpd dies.

Question:	Does any of this make sense to anyone?  Anyone have
		a clue as to the actual problem and/or solution?

Any help/suggestions would be greatly appreciated.  Note that I have
the similar setup working with a Sun SPARCserver acting as the
load host.  That was simple.  Why isn't this simple?

Later,
Kevin R. Fenster
Nebraska Wesleyan University
krf@NebrWesleyan.edu