Diagnosing Connection Refused Errors on a Windows Server

Follow the procedure below to diagnose connection refused errors on a Windows server.
  1. To confirm the name of the client system, from your Windows desktop, choose Start > Settings > Control Panel > Network > Configuration menu. Click TCP/IP, then choose Properties > DNS Configuration > Host. The name you specify for the "Host" entry is the one that the runtime uses.
  2. Confirm the name of the client system. Enter: 
    hostname

    The system will return its official network host name.

  3. 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: 
    acurcl -access
    Note: This task requires root privileges on a UNIX server. It should be done by the AcuConnect system administrator.
    1. Be sure to enter the name of the working server access file when prompted.
    2. Select menu item [4], Display one/all security records.
    3. Respond N to the Display all records? prompt.
    4. To the next two prompts, provide the client machine name and client user name, respectively. The matching record will be displayed.
  4. 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.
  5. Determine whether you have reached the Windows limit on the number of simultaneous child runtimes. The CHILD_WAIT configuration variable contains a value for the number of milliseconds that AcuConnect waits for a child runtime to start successfully. If the child runtime subsequently stops, check the trace file for the entry "Child runtime stopped!! Exit code is nnn." If nnn is "128", the Windows limit has been reached and no additional child runtimes are allowed until another runtime process is terminated. Refer to Microsoft Knowledge Base article 184802, "User32.dll or Kernel32.dll Fails to Initialize," to learn how to work around this limitation.
Parent topic: Connection Refused