HP-UX AAA Server A.07.01 Administrator's Guide

• Authentication Relay Port: Ensure that the correct UDP port that is used to relay
authentication requests (configured in /etc/services) is specified. The default
authentication relay port is 1812.
• Accounting Relay Port: Ensure that the correct UDP port that is used to relay
accounting requests (configured in /etc/services) is specified. The default
accounting relay port is 1813.
For more information on proxy server configuration, see Configuring Proxies on page
119. If a proxy server is offline or does not forward the requests, see “Troubleshooting
Flowchart” (page 332) to troubleshoot it.
Identifying Unrecorded DHCP Failures
Unrecorded DHCP failures can occur because of a shortage of addresses in the
configured address pool, or if the DHCP server sends a malformed packet to the HP-UX
AAA Server.
To determine if an unrecorded DHCP failure caused the problem, complete the following
steps:
1. Access the datastore used for user profile storage as described in “Identifying
Unrecorded External Datastore Failures” (page 351).
2. If the DHCP address pool is configured, ensure that there are sufficient addresses
in the pool.
3. Ensure that the DHCP server is sending valid packets to the HP-UX AAA Server.
Troubleshooting Access-Rejects from the HP-UX AAA Server
The HP-UX AAA Server sends an Access-Reject message to the RADIUS client if
authentication fails. Authentication failures occur because of incorrect configuration
on the HP-UX AAA Server or the RADIUS client, or due to incorrect credentials passed
to the HP-UX AAA Server.
Use the following sections to troubleshoot problems related to authentication failures.
• “Common Authentication Failure Problems” (page 352): This section lists the
common problems related to authentication failures and the necessary corrective
actions.
• “EAP Problems” (page 360): This section lists EAP implementation-specific problems
related to authentication failures.
Common Authentication Failure Problems
Compare the error messages recorded in the logfile to those in Table 28-5 and perform
the corresponding corrective actions.
352 Troubleshooting Procedures