Check to be sure JINETD is running.
-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On Behalf
Of Jim Chance
Sent: Wednesday, June 16, 2010 9:53 AM
To: [log in to unmask]
Subject: [HP3000-L] Connecting to 192.168.0.199..... Could not open
connection to host, on port 23: Connect failed
Can anyone tell me why I can't DOS telnet or Reflections telnet to a new
HP3000 that appears to have the network up?
When from DOS I telnet I get the error message:
Connecting to 192.168.0.199..... Could not open connection to host, on port
23: Connect failed
When in Reflections I get connection timed out.
I followed the suggestions for enabling the network via a job that's
streamed from sysstart.pub.sys from a previous issue thread.
I have jinetd running.
I can ping the HP3000.
I can run ping.net.sys and ping externally.
RELEASE: C.75.00 MPE/iX HP31900 C.45.05 USER VERSION: C.75.00
Perhaps I need to change something in sysgen to enable port 23 for telnet?
Help. Thanks.
services.net.sys contains telnet for port 23 below
:print services.net.sys
# This file contains the information about the services provided.
# Copy this file to SERVICES.NET.SYS if that file does not already exist.
#
# The form for each entry is:
# <official service name> <port number/protocol name> <aliases>
#
# See the Configuring and Managing MPE/iX Internet Services Manual
# for more information (HP Part No. 32650-90835).
#
# Note: The entries cannot be preceded by a blank space.
#
echo 7/tcp # Echo
echo 7/udp #
discard 9/tcp sink null # Discard
discard 9/udp sink null #
daytime 13/tcp # Daytime
daytime 13/udp #
chargen 19/tcp ttytst source # Character Generator
chargen 19/udp ttytst source #
ftp 21/tcp
telnet 23/tcp
time 37/tcp timeserver # Time
time 37/udp timeserver #
(24/36) Continue?
domain 53/tcp nameserver # Domain Name Service
domain 53/udp nameserver #
bootps 67/udp # Bootstrap Protocol Server
bootpc 68/udp # Bootstrap Protocol Client
tftp 69/udp # Trivial File Transfer Protocol
DAServer 987/tcp # SQL distributed access
nmbp 137/udp
smbp 139/tcp
shell 514/tcp cmd # remsh
smtp 25/tcp mail # Simple Mail Transfer Protocol
syslog 514/udp # remote system logging
psmond 1788/tcp
diagmond 1508/tcp # Support Tools Manager (STM/iX)
My NMMGR shows the network interface config and it appears to be normal:
---------------
PMP credential. Information Technology professional since 1987. SQL Server
2k/2k5/2k8 admin, Advanced Crystal Reports 8.5/9/11 development &
instruction, Project Management (small scale), HP3000 expert, IBM/SCO/HP
UNIX exp., Migrations/Conversions, ERP tier I & II expert. Skill Keywords:
PMP, SQL Administrator, HP3000, Crystal Reports, T-SQL, UNIX, AS400,
Jobscope, Epicor, Macola, JEE, Vantage, ERP, Enterprise Manager, Query
Analyzer, Active Directory, SSIS/DTS, PowerHouse, Cognos, IMAGE, MPE, SQL
server, Project Manage, MS Visual Studio, Noble, Business Analyst,
Programmer Analyst, Systems Analyst, Project Leader, IT Management, Linux,
COBOL, System Management/Admin., SDLC.
http://hotjobs.yahoo.com/resumes/jim_chance/jimchanceyahoo
Jim Chance
1485 County Road 1575
Ashland, Ohio, 44805
Home: 419-557-2225
Cell: 419-651-6704
Fax: 732-601-6704
Email: [log in to unmask]
NMMGR has been validated and saved.
System has been restarted.
Hardware is in place (couldn't ping to it if any component of hardware
wasn't connected).
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
