Connection refused

Problem: Attempts to connect to the server fail, possibly returning a 9D, 103, connection refused error.

Connection refused errors occur for a variety of reasons:

1. The matching access record specifies an invalid Local Username, or DEFAULT-USER holds an invalid user name. Note that use of "same as client" in the Local Username field of the access record can lead to the attempted use of an invalid user name ("same as client" directs AcuConnect to use the Client Username as the Local Username).
   
2. There is no matching access record for the client machine name/client user name combination.
   
3. If connecting to a UNIX server, the AcuConnect license on the server may require that the acushare license manager be running, and AcuConnect was not able to start acushare automatically.

Diagnostics:

Confirm your client user name and client machine name and find the combination's matching entry in the server access file.

1. Follow diagnostic steps 1 and 2 from Unexpected user name.
   
2. Examine the server access file for the record that matches the client machine name/client user name combination (this should be performed by the AcuConnect system administrator).

   On a UNIX server, become superuser or log on as root. On a Windows NT server, log in as Administrator or from an account that belongs to the Administrators group.

   Run the server access file manager utility ("acuconnect -access"). Be sure to enter the name of the working server access file in response to the utility's first prompt.

   Select menu item [4] -- "Display one/all security records." Respond no ("N") to the prompt "Display all records?" Respond to the next two prompts with 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) or the Windows NT User Manager 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) or the Windows NT User Manager 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") or the Windows NT User Manager for the presence of a valid entry for that name.

3. Confirm that acushare is running on the UNIX server by issuing the "acushare" command with no arguments. If you receive a usage message, then acushare is not running, and may be manually started using the "acushare -start" command. See "UNIX Start-up" for more information on running acushare.