Installing and Administering Internet Services

Chapter 12 481
Troubleshooting Internet Services
Troubleshooting the Internet Services
2C5. Fix $HOME/.netrc. If the file is incorrect, make
corrections to it and go to 2C6.
2C6. Once the corrections are made, repeat this flowchart
beginning with 2A.
2D. See node manager. If your system was denied access to
the server system by the /var/adm/inetd.sec file, but
you wish 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.
2G. See node manager. You are not allowed to use ftp to
access the server system. Check with the node
manager of the server system and request that the
appropriate user name be removed from the
/etc/ftupusers file.
2H. ftp should work. If you have reached this point in the
flowchart, the ftp server exists and you have access to
the system. If you are using correct syntax and none of
the error messages have solved the problem, report the
problem to your Hewlett-Packard support contact.