June 08, 2018
Fine-Tune: Making the 3000's ports report
I have a port in an HP 3000 and I want to know the application that is currently using that port. Is there any command that can show me the applications accessing a particular port?
Kevin Miller replied:
Enter ‘c’ for ‘call sockets.’ Listeners are shown in port order.
The port for telnet on our 3000 is set to a different value then 23, but it is set to 23 on our HP Unix server. When I try to telnet from the 3000 to HP-UX I get the following message: Trying... telnet: Unable to connect to remote host. If I switch the port for telnet to 23 on the 3000, it works great.
My question is: Can I run telnet on two different ports on either box so that I can maintain my non-standard port on the 3000, but still allow telnet to run between the two boxes? If not, is there another way to make this work?
Jeff Kell replied:
Just ‘telnet your.3000.name nnn’ where ‘nnn’ is your ‘nonstandard’ port.
How do I point network printer configurations to specific ports on (external) multi-port JetDirect (or equivalent) boxes?
Gilles Schipper replied:
You need to add the tcp_port_number option, in NPCONFIG, as follows:
(network_address = 18.104.22.168 tcp_port_number = 9100) # for port 1
(network_address = 22.214.171.124 tcp_port_number = 9101) # for port 2
(network_address = 126.96.36.199 tcp_port_number = 9102) # for port 3
(Please note that everything on each line after and including the “#” represents a comment.)
My HP 3000 is set up for full access to the Internet. The telnet connection works fine, but I also see that VT-MGR also works. I know that inetdsec is used for restricting access for ip, https, ftp and so on. Is there something in NMMGR to restrict VT-MGR access, or do you use inetdsec for that also?
Chris Bartram replied:
Just an option logon UDC that checks the CIVars set for the IP address and hostname of the originator.
We’ve got a DLT4000 tape drive I’d like to connect to a Series 957 and use them for database, incremental, and full backups. Can I simply hook a DLT4000 drive to the SE-SCSI port on the MFIO card, set its SCSI address, and add the device as an HPC1521B?
Gilles Schipper replied:
It should be no problem at all. The DLT4000 SE SCSI device can also be utilized as a boot device on the 957. You should use the device ID of DLT4000 and not HPC1521B. You should consider using the device ID of HPC1521B as a workaround to any restore problem. It would be best to use device ID DLT4000 and test to ensure good restore performance, and only resort to device ID HPC1521B if the restore speed is NOT satisfactory.
Use our search engine to find 20 years
of HP 3000 news and articles
The comments to this entry are closed.