Follow the procedure below to diagnose connection refused errors on a UNIX server.
Confirm your client user name. Log on to the client system using the same user name and UNIX environment that resulted in
the unexpected user name. At the UNIX prompt, enter:
who am i
Is the user name returned the name you expected?
Confirm the name of the client system. Enter:
The system will return its official network host name.
On the server, examine the server access file for the record that matches the client machine name/client user name combination.
Run the server access file manager utility:
Note: This task requires root privileges on a UNIX server. It should be done by the AcuConnect system administrator.
Be sure to enter the name of the working server access file when prompted.
Select menu item , Display one/all security records.
Respond N to the Display all records? prompt.
To the next two prompts, provide the client machine name and client user name, respectively. The matching record will be displayed.
If there is no matching entry, you need to add one:
- If the Local Username field contains the name of a user (a string), check the UNIX password file (/etc/passwd) for the presence of a valid entry for that name. If no entry exists, the name is not valid.
- If the Local Username field is "same as client", Local Username is set to the value of Client Username. Check the UNIX password
file (/etc/passwd) for the presence of a valid entry for that name.
- If the Local Username field is blank, Local Username is set to the value of the server configuration variable DEFAULT_USER.
The value of DEFAULT_USER is defined in the server configuration file. Check the UNIX password file (/etc/passwd) for the presence of a valid entry for that name.
Confirm that acushare is running on the UNIX server by issuing the acushare command with no arguments. If you receive a usage message, acushare is not running and may be manually started using the
acushare -start command.