Connection Refused

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

Connection refused errors occur for two reasons:

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 in 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 AcuServer system administrator).
    1. On a UNIX server, become superuser or log on as root. On a Windows server, log in as administrator or from an account that belongs to the administrators group.
    2. Run the server access file manager utility (acuserve -access).
    3. Be sure to enter the name of the working server access file in response to the utility's first prompt.
    4. Select menu item [4] - Display one/all security records.
    5. Respond no (N) to the prompt Display all records?.
    6. 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 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 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 User Manager for the presence of a valid entry for that name.