You are using an unsupported browser. Please update your browser to the latest version on or before July 31, 2020.
close
Home > Access It! Universal.NET > Access It! Universal.NET Client / Server Configuration
Access It! Universal.NET Client / Server Configuration
print icon

Overview

This document applies to:

  • Access It! Universal.NET v6
  • Access It! Universal.NET v7
  • Access It! Universal.NET v8
  • Access It! Universal.NET v9

For Access It! Universal.NET v5 see Access It! Universal.NET V5 Client / Server Configuration
For Access It! Universal v4 and previous see Access It! Universal Client / Server Configuration

Firewall Setup

Firewall settings only need to be set on the Server (the computer hosting the dongle). For more information on Windows Firewall, see the following Microsoft TechNet Article

  1. Exceptions need to be made for the AIUniSvc_Net.exe located in the Access It! Universal.NET installation directory 
    An exception can be made for TCP port 3030 if a firewall exception cannot be made for the Access It! Universal.NET service
  2. Other applications such as DVR interfaces, etc. will be application specific. Please reference the specific vendor’s installation and configuration notes as needed

General Notes

  1. The client workstation must be able to ping the Server (the computer hosting the dongle) by name or IP address
  2. If the service is running as local system account and the SQL Server is on another machine, the Database Configuration needs to be setup for SQL authentication.
  3. When either the server or client is in a Workgroup environment, the Windows Username and Password that is being used to log into the Client computer must exist and match exactly as a Local User on the server

Managing Windows Usernames and Passwords

When client and server do not reside in the same domain the Windows Username and Password that is being used to log into the Client computer must exist and match exactly as a Local User on the Server (the computer hosting the dongle).

  1. Open Computer Management off of the start menu
  2. Double click Local Users and Groups
  3. Select Users
  4. Right click on the right pane of the window and select New User

For more information on creating and managing user accounts, see the following Microsoft TechNet Article 

Troubleshooting Errors

  1. The Windows Operating System on the server machine has rejected the credentials for USER. Ensure this account exists as a Windows user on the server and that the passwords match.
    1. Verify that the launching Windows user on the client workstation exists on the server as a local user.
  2. The server has rejected credentials for USER. Verify that the user name and password for this user are valid at the server.
    1. Verify that the launching Windows user on the client workstation exists on the server as a local user.
  3. Couldn't connect to service - verify service is running on SERVER, the correct TCP port is specified and the firewall is properly configured.
    1. Verify that the service is running on the server.
    2. Verify that an exception has been made for either the Access It! Universal.NET service or TCP port 3030.
    3. Verify the server machine and client machine are running the same version of the software.
  4. The socket connection was aborted. This could be caused by an error processing your message or a receive timeout being exceeded by the remote host, or an underlying network resource issue. Local socket timeout was .00:00:05'.
    1. Verify that the launching Windows user on the client workstation exists on the server as a local user.
  5. An error occurred when verifying security for the message.
    1. Ensure the clock of the server and client are in sync. Time drifts can impact the authentication between machines.

scroll to top icon