Journal
Knowledge base
Comprehensive configuration of U-PROX software and network interaction

Comprehensive configuration of U-PROX software and network interaction

Share and save

Use the recommended software version and follow the recommendations below.
If you plan to use current versions of SQL Server, review the installation instructions in the “Installation Rules” file included in the setup package.

Recommended software version: v3.057.7988.
After its install or update, existing databases are ALSO upgraded.

Download the ISO image of U-Prox software version 3.57.7988 and install/update your current version:
https://drive.google.com/file/d/14kt60eWtgMPhV5VQMBS1jq5MN7l47uxy/view

Update in sequence – Server, Client, Web Server, Desktop Server – on the program server; and Client and Desktop Server on remote client workstations.
Desktop Server – where the Web Client or the U-Prox Desktop USB reader is used.
After switching to newer versions, refresh the browser page with Ctrl+F5 to reload with cache clearing.

General system information

Moving the server/databases:

On Win 7 (and similar or earlier), by default the installer installs SQL 2008 R2
On Win 10 (and similar or later), by default the installer installs SQL 2014
You can upgrade databases from SQL 2008 R2 to SQL 2014, but not reverse.

On the old PC:

Stop the “U-Prox IP Equipment Service” and disable its startup
If controllers and server are on different subnets, change the old server’s IP address to any free address
Take a backup of the databases

On the new PC:

Install the software version
Assign the PC the same IP address the old server used
Restore the databases, leaving “Update database to current version” checked during restore
Start the “U-Prox IP Equipment Service”

Install the components “U-Prox Server,” “U-Prox Client,” and “U-Prox Web Server” on the PC that will act as the system server.

For use with the classic client

On remote PCs install the “U-Prox Client” and the driver for the U-Prox Desktop USB reader, then perform the settings below.

For use with the web client

On remote PCs install the “U-Prox Desktop Server” and the driver for the U-Prox Desktop USB reader, then open the Web Client in a browser as described below.

Important!

The “U-Prox IP Equipment Service” (“U-Prox IP Hardware Service” in English or non-Cyrillic UIs) must be running on the server.
The controller must be online with the software before performing “read network configuration.”
You may need to factory-reset the controller first.
Ensure that the controller’s TCP/UDP ports 28001–28003 are not being blocked.
Once the controller comes online, upload its configuration; its status will then change to “Autonomous.”
“Initialization” status means the controller was added to the database but has never had its configuration loaded.
“ping” shows ICMP connectivity; you must also have TCP (or UDP) access on ports 28001 and 28002.

U-PROX IP (also “U-Prox WEB”) interfaces

It has two user interfaces: classic Windows and web.

On the first PC (the software server) install “U-Prox Server,” “U-Prox Client,” and “U-Prox Web Server.”
On other PCs install “U-Prox Client.”

For the web client – no special settings: browse to
http://<server_IP>:40001/ or http://<server_name>:40001/
For HTTPS use port 40002.

For the U-Prox Desktop USB reader in the web client – besides drivers, install the “U-Prox Desktop Server” component.

Equipment ↔ Software connectivity requires

The “U-Prox IP Equipment Service” running on the server
IP400 with factory keys
Correct network settings on IP400
Network accessibility (between subnets, PCs, routers, antivirus) for UDP/TCP ports 28001–28003 or proper port forwarding
In the database, manually added IP400 (if not on the same subnet) with its correct GID (found on the board label or in the USB configurator)

If the controller is online in the software – highlighted in green.
If connection is lost – highlighted in red.

If there is no connection – then any actions from the program will have no effect.

Check in the Event window for incoming new notifications, and you can also view the entire event pool via the “Events Report.”

If ICMP traffic passes through the tunnel – you can “ping” the controller’s IP address from the server side, and vice versa.

GENERAL INFORMATION ABOUT CONFIGURATION FOR WAN OPERATION

Our controllers operate over Ethernet networks, via LAN, WAN, VPN, with the appropriate configuration.

Review the document on configuring our equipment – on the website, under “Downloads,” “Tech Support”:

Initial IP Controller Setup Using UPROXIPConfigurator

And familiarize yourself with the following document:

Configuring Client–Server Interaction (Remote Workstations) in U-PROX IP

The following information may be useful:

On a local network it’s simple—just ensure ports 28001, 28002, 28003 (UDP and TCP) are open between subnets. Over a global network (WAN), you need proper routing, port forwarding, firewall rules, and to ensure your providers do not block the ports or protocols.

Controller settings are described in the document:

“Initial IP Controller Setup Using UProxIPConfigurator”, located in \Documentation, and also at
https://u-prox.systems/downloads/acs/support/ru/Configurator.pdf — see the examples on the last pages.

Example of controller operation via WAN:

From the remote controller side:

The “server” is the public IP address (or DNS name) of the router on the program server side
In the router’s firewall, allow outbound UDP and TCP on port 28002
In the router’s firewall, allow inbound UDP and TCP on port 28001

From the U-PROX software server side:

In the server-side router, forward external UDP and TCP port 28002 to the same port on the U-PROX server’s IP address
In that router’s firewall, allow inbound UDP and TCP on port 28002
In that router’s firewall, allow outbound any UDP and TCP port from the U-PROX server’s IP address

Manually add the remote controller in the software, specify its serial number (GID), establish connectivity—otherwise check what is still unconfigured.

For a remote “classic” client over WAN, the recommendation is:

Please perform the following actions:

Ensure that on both server and client the installed version of “U-PROX IP” is the same and is at least 3.040.6078.
- If an earlier version is installed, update U-PROX IP first to 3.040.6078, then to the current version.
On the client, run the registry editor regedit.exe and make these changes:For x32 systems[HKEY_LOCAL_MACHINE\SOFTWARE\A2SoftIn\UProxIP\2.00] For x64 systems[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\A2SoftIn\UProxIP\2.00] "DatabaseServer"="server_IP_address\SQLEXPRESS,1433" – example: with SQL server name GG2002 and SQL server port 28000Remove (or comment out) the "RemoteServer"=.... In other words, add the DatabaseServer string value with the ACS server’s IP, instance name, and SQL port, and remove the RemoteServer string value.
If the server is on an internal network, forward external port 1433 on that network’s router to port 1433 on the server. This is usually configured under “Port Forwarding” in the router’s web settings. In this case, in the client’s registry specify the router’s external IP instead of the server IP.
On both client and server, create a local Windows user with the same login and password.
- The password cannot be empty; it must contain at least one character.
- Add this local user to the UProxIPUsers group on the server, then restart SQL Server.

На клієнті увійдіть в систему з логіном і паролем вищезгаданого користувача та запустіть програму-клієнт. Переконайтеся, що під час запуску не виникає помилок.