After being unable to earlier abort the JINETD job, we first tried doing
a =LOGOFF keeping only the console connected. When that didn't work we
shutdown the network services and tried to shutdown the system with the
=SHUTDOWN command. The system hung for almost 15 minutes, so at that
point we decided to do a <CNTL> B and reset the system.
After the system came back up we started the network services and
streamed the JINETD job. At first users were able to connect using
TELNET, but after 5-10 minutes they were locked out of their sessions
and unable to reconnect. We are also unable to abort the new JINETD
job. The only changes we have made in the past week was to load SAMBA
on our system (without any success so far). Our NS/VT users can connect
without any problem as do our serial connections.
Here is my SERVICES.NET.SYS file:
# 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 services(4) manual page for more information.
# Note: The entries cannot be preceded by a blank space.
#
echo 7/tcp #1Echo
echo 7/udp #1
discard 9/tcp sink null #1Discard
discard 9/udp sink null #1
daytime 13/tcp #1Daytime
daytime 13/udp #1
chargen 19/tcp ttytst source #1Character Generator
chargen 19/udp ttytst source #1
ftp 21/tcp
telnet 23/tcp hphost1.hptaxsa.ugsa
smtp 25/tcp # Simple Mail Transfer
time 37/tcp timeserver #1Time
time 37/udp timeserver #1
domain 53/tcp nameserver # Domain Name Service
domain 53/udp nameserver #
bootps 67/udp #1Bootstrap Protocol Server
bootpc 68/udp #1Bootstrap Protocol Client
tftp 69/udp # Trivial File Transfer Protocol
finger 79/tcp # finger server
http 80/tcp # Hostname Client
hostname 101/tcp # Hostname Client
POP2 109/tcp # POP2 server
POP3 110/tcp # POP3 server
nmbp 137/udp
smbp 139/tcp
DAServer 987/tcp # SQL distributed access
This is the job stream for the JINETD job:
do lsp
/SYS/PUB>lsp 3585
JOB JINETD,MANAGER.SYS,PUB.
Priority = DS; Inpri = 14; Time = UNLIMITED seconds.
Job number = #j2.
MON, OCT 13, 1997, 2:23 PM.
HP3000 Release: C.55.00 User Version: C.55.00
MPE/iX HP31900 C.05.08 Copyright Hewlett-Packard 1987.
All rights reserved.
STREAMED BY CONSOLE,MANAGER.SYS (#S1) ON LDEV# 20
STREAM DATE: MON, OCT 13, 1997, 2:23 PM
:COMMENT STREAM FILE JINETD.NET.SYS
:COMMENT STREAMED BY CONSOLE,MANAGER.SYS,PUB ON LDEV 20
:COMMENT ON MON, OCT 13, 1997, 2:23 PM
:RUN inetd.net.sys
Reading configuration
echo(tcp nowait MANAGER.SYS port: 7)
echo/tcp: Added service, server internal
echo(udp nowait MANAGER.SYS port: 7)
echo/udp: Added service, server internal
(24/106) Continue?
daytime(tcp nowait MANAGER.SYS port: 13)
daytime/tcp: Added service, server internal
daytime(udp nowait MANAGER.SYS port: 13)
daytime/udp: Added service, server internal
time(tcp nowait MANAGER.SYS port: 37)
time/tcp: Added service, server internal
time(udp nowait MANAGER.SYS port: 37)
time/udp: Added service, server internal
discard(tcp nowait MANAGER.SYS port: 9)
discard/tcp: Added service, server internal
discard(udp nowait MANAGER.SYS port: 9)
discard/udp: Added service, server internal
chargen(tcp nowait MANAGER.SYS port: 19)
chargen/tcp: Added service, server internal
chargen(udp nowait MANAGER.SYS port: 19)
chargen/udp: Added service, server internal
telnet(tcp nowait MANAGER.SYS port: 23)
telnet/tcp: Added service, server internal
bootps(udp wait MANAGER.SYS port: 67)
bootps/udp: Added service, server /SYS/NET/BOOTPD
tftp(udp wait USER.TFTP port: 69)
tftp/udp: Added service, server /SYS/NET/TFTPD
nmbp(udp wait MGR.SAMBA port: 137)
(47/106) Continue?
nmbp/udp: Added service, server /SYS/SAMBA/NMBD
nmbp/udp: New server /SYS/SAMBA/SMBD
nmbp/udp: New arguments for server /SYS/SAMBA/SMBD
Configuration complete
Received call for: nmbp udp
Received call for: nmbp udp
Received call for: nmbp udp
Received call for: telnet tcp
Received call for: nmbp udp
Received call for: nmbp udp
Received call for: nmbp udp
Received call for: nmbp udp
Received call for: nmbp udp
Received call for: nmbp udp
Received call for: telnet tcp
Received call for: nmbp udp
Received call for: nmbp udp
Received call for: nmbp udp
Received call for: nmbp udp
Received call for: nmbp udp
Received call for: nmbp udp
Received call for: nmbp udp
Received call for: telnet tcp
Received call for: nmbp udp
Received call for: nmbp udp
Received call for: nmbp udp
Received call for: nmbp udp
Received call for: nmbp udp
Received call for: nmbp udp
Received call for: nmbp udp
Received call for: nmbp udp
Received call for: nmbp udp
Received call for: nmbp udp
Received call for: nmbp udp
Received call for: nmbp udp
Received call for: nmbp udp
Received call for: nmbp udp
Received call for: nmbp udp
Received call for: nmbp udp
Received call for: nmbp udp
Received call for: nmbp udp
Received call for: nmbp udp
Received call for: nmbp udp
Received call for: nmbp udp
Received call for: nmbp udp
Received call for: nmbp udp
Received call for: nmbp udp
Received call for: nmbp udp
Received call for: nmbp udp
Received call for: nmbp udp
Received call for: nmbp udp
Received call for: nmbp udp
Received call for: nmbp udp
Received call for: nmbp udp
Received call for: nmbp udp
Received call for: nmbp udp
Received call for: nmbp udp
Received call for: nmbp udp
Received call for: nmbp udp
Received call for: nmbp udp
/SYS/PUB>
Ordinarially we could just get out TELNET users to connect via NS/VT but
we have a big demo tomorrow and the person doing the demo insists on
connecting via TELNET so we have to get this fixed ASAP..
Any help will be more than appreciated....
TIA,
Ted
Ted Johnson
[log in to unmask]
United Government Services of America
Heard, Goggan, Blair & Williams 210-225-6846
San Antonio, TX 78205
"Never drive faster than your angels can fly"
|