HP3000-L Archives

May 2004, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Mark Bixby <[log in to unmask]>
Reply To:
Mark Bixby <[log in to unmask]>
Date:
Fri, 14 May 2004 09:53:37 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (25 lines)
Tom Hula wrote:
> In my JINETD stdlist, I get this message over and over again,
> most often displaying this hex number address:
>
> hardware address not found: 00206F1203BF
>
> No one appears to be having any problems using telnet
> to access the 3000. But I do recall a time when JINETD
> had a relatively small stdlist no matter how long it ran,
> instead of thousands of lines long after a month or so....

I believe this is due to bootp activity on your 3000's local LAN segment.  Back
when I was a customer, this could be caused by powering on external JetDirect
boxes for network printers.

If your 3000 doesn't need to be a bootp server, comment out the bootps entry in
/SYS/NET/INETDCNF and then restart JINETD.  While you're at it, you should
comment out *everything* in INETDCNF that you aren't explicitly using.
--
[log in to unmask]
Remainder of .sig suppressed to conserve expensive California electrons...

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2