Installation guide

EK–WNTMP–MH. D01 123995–002 C–1
C
Troubleshooting Secure Path Connection Problems
This appendix describes general network configuration issues which might affect the ability of the
Secure Path Client and Agent to establish connection.
C.1 Client/Agent Considerations
•
Add each client’s NetBIOS name or Fully Qualified Domain Name (FQDN) to the
agent’s list of authorized clients using the Agent Configuration utility, and set the
password in the password dialog box. Once you’ve made the modifications, Stop and
Restart the Secure Path Agent to update the database using the Services applet from
Control Panel.
•
Make sure that you use the same name type, either NetBIOS or FQDN, during Secure
Path client login that you have entered in the agent’s database.
•
Each name you use must be mapped to its network IP address using a HOSTS file
(static text file with either NetBIOS or FQDN mapped to IP,) the Windows Internet
Naming Service (WINS with a NetBIOS name)
,
or by the Domain Name System
(DNS with a Fully Qualified Domain Name.) See network considerations below for
more information.
•
In cluster configurations make sure that the password you choose is common for both
agents in the cluster.
•
Secure Path does not use Windows NT domain authentication to authorize clients.
Client authentication is handled for each agent using name-to-IP address resolution
and password verification from the Secure Path configuration database.