HP3000-L Archives

March 2003, Week 5

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:
John Burke <[log in to unmask]>
Reply To:
Date:
Sat, 29 Mar 2003 16:43:24 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (66 lines)
Wirt writes,

>
> Mike writes:
>
> > I really need assistance as I am at the end of the rope.  I
> have followed
> >  all the help offered by the folks here and believe I have everything
> >  configured correctly.  I cannot start arpa.  I get an error stating
> >
> >  (ANUtil):ERROR 31995 STARTING ALLBASE/NET LISTENER FOR ARPA
> >
> >  I can ping the address that I assigned to the 937LX using
> NMMGR.  When I
> >  try to start a TELNET session using QCTerm I get:
> >
> >  <TELNET Connect Error: [10061} Connection refused>
> >  A few questions,
> >  If I stream JINETD.NET.SYS, must I also run ARPA?
>
> HP tends to use the older, more original names for things,
> which adds to my
> confusion, if no one else's, but in general, my impression is
> "yes" to your
> last question.
>
No. This "arpa" is the allbase/net listener. Absolutely not needed for
general TCP/IP and telnet connectivity. Probably tried the command anstart
arpa.

> FTP, Telnet, etc. are ARPA "services", and thus for whatever
> base ARPA means,
> it must be up and running before any of its services are
> running. The ARPA
> base certainly includes TCP/IP itself.
>
> However, the fact that you can ping the machine is a good
> sign. TCP/IP has to
> be working, and therefore you can't be too far away from
> being up and running
> with telnet. The QCTerm message that you're receiving:
>
>      <TELNET Connect Error: [10061} Connection refused>
>
> ...is indicative that the telnet service is not running.
> JINETD must be
> running before telnet will work. Do a SHOWJOB and see if it's
> there in your
> session list. If it is, telnet should be available. If it's
> not, read the
> manual once or twice more and do whatever you need to do to get JINETD
> working, being sure not to skip any step. Until you do get
> the JINETD job to
> stream, telnet will not work.
>

Yes, go back to first principles and read the appropriate manuals. Mike does
not say what release of MPE he is running. First place to look is to make
sure services.net.sys exists and has telnet in it. Oh, and do not try to
screw around with security until you get it going.

John Burke

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

ATOM RSS1 RSS2