HP-UX Internet Services Administrator's Guide (May 2010)

2B. Maximum number of connections? The maximum number of simultaneous
connections is specified in the optional file /var/adm/inetd.sec. When
inetd is configured, it checks this file to determine the number of allowable
incoming connections. Look at this file to determine how many connections
are allowed. The default is 1000.
2B1. See the node manager. If the maximum number of connections has been
reached, the node manager can change this value in the /var/adm/inetd.sec
file.
2C.
Access to the server? The /var/adm/inetd.sec file also contains a list of
systems that may not access the server. If inetd was started with the -l option,
the system log may list the connections that are refused access to the server.
Check this log file, if it exists, or ask the node manager to verify whether you
have access to the server. If you find that you do not have access to the server,
continue with 2D.
2C1.
Using telnet or ftp? Additional security files exist for these services that
must be checked. If you are using ftp or telnet go to 2C2; otherwise, go to
2E.
2C2.
Using ftp? If you are attempting to use ftp, go to 2C3; otherwise, go to 2F.
2C3.
Access to ftp? If the user you are logging on as is listed in the /etc/ftpusers
file on the server system, you may not use ftp to that system. If you do not
have access to ftp, go to 2G.
2C4.
$HOME/.netrc file incorrect or non-existent? If this file is incorrect or
non-existent, it is not used for the connection attempt. In particular, if the file
exists, check its mode bits, owner ID, and syntax. Type man 4 netrc for more
information. If it is correct, go to 2H.
2C5.
Fix $HOME/.netrc. If the file is incorrect, make corrections to it and go to
2C6.
2C6. After you have made the corrections, repeat this flowchart beginning with 2A.
2D. See the node manager. If your system was denied access to the server system
by the /var/adm/inetd.sec file, but you want to use the server, contact the
node manager of the server system and request access.
2E.
Go to Flowchart 3. If you are using the Berkeley Services (sendmail, BIND,
finger, the rexec library, or any of the “r” services), go to Flowchart 3 to
begin troubleshooting the security for those services.
2F.
telnet should work. If you have reached this point in the flowchart, the
telnet server exists and you have access to the system. If you are using correct
syntax, if the login password you are using exists on the server system, and if
none of the error messages have solved the problem, report the problem to
your Hewlett-Packard support contact.
Troubleshooting Tips 85