Jim,

Stock system do not enable telnet. Telnet is available from the JINETD.NET.SYS job, which must be configured (INETDCNF.NET.SYS)for telnet before starting. The default communications protocol is NSVT.

When a network connection is made, you can see the HPLOCIPADDR and HPREMIPADDR. They are associated with network connections, not serial/console connections........

You can ignore the catalog warning. 

NSVT will use the NMMGR configured ports.

Ping only shows the card is alive. FWIW In the past, I have seen successful pings against a 980/200 LANIC where the MPE operating system was down (DEAD displayed on the panel).

Neal Kazmi
Minisoft, Inc.
800-682-0200
360-568-6602
www.minisoft.com


-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On Behalf Of Jim Chance
Sent: Monday, July 05, 2010 12:45 PM
To: [log in to unmask]
Subject: [HP3000-L] Connecting to 192.168.0.199.....(.....) "connection refused by host"

Although its been roughly 3 weeks since I spoke of this issue, it unfortunately still remains an issue. I can only work on this problem about once a week for a few hours. Any suggestions you can offer is appreciated. 
 
The problem is the client can’t telnet connect via (....) to a newly received HP3000 box. 
 
Symptom:
Best telnet connection via (......) to 192.168.0.199 says “Connection refused by host”
 
Questions:
Why doesn’t showvar list a variable that shows the IP of 192.168.0.199? I thought there was a variable name for that? What sets it? 
 
In NMMGR my validation lists the following, is this the root cause of my problem? 
Copying validated configuration file to backup file, please wait ***
(Press RETURN when done viewing screen contents)
 
Based on your HP3000 knowledge, is the NMMGR configured network list? 
 
Items checked/findings:
1. DOS ftp, open 192.168.0.199, connected to 192.168.0.199, connection closed by remote host
 
2. This file has been verified to ensure there is no telnet deny setting:
:print inetdsec.net.sys
:
3. DOS ping works ok. But trying to run ping.net.sys and attempting to ping the client does not work. 
 
4. I added a stream job to sysstart.pub.sys to get the network started……..
:print sysstart.pub.sys
 
5. Running nmmaint.pub.sys shows some things not installed, but I’m not certain if that’s my problem/root cause:


6. Services.net.sys looks ok. Its contents are:


TMI

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