How to Handle an EPP Server IP Address Change When Using EasyLock

[jwkim (김지원)]

Currently, one of our customers using Windows PCs is planning to upgrade their EPP Server from version 5.9.4.3 to 2608.

The customer is currently using EasyLock on EPP Server 5.9.4.3, and the EPP Server IP address will be changed as part of a server hardware replacement.

As we understand it, when the server IP address is changed, the existing EasyLock clients will continue to point to the previous EPP Server IP address. As a result, the existing EasyLock installation may no longer function properly.

We tested the EasyLock Multi-Server feature as a possible solution. However, we found that File Tracking logs are not properly recorded when using the Multi-Server configuration.

Therefore, it seems that the Multi-Server feature may not be suitable for this environment.

Is there any way to continue using the existing EasyLock installation after the EPP Server IP address is changed?

For example, is there a way to update the EPP Server IP address while keeping the existing EasyLock configuration, without requiring the EasyLock client to be reinstalled?

We would appreciate it if you could advise us on the recommended approach for this scenario.

Thank you.

[krzysztof.staszalek (Krzysztof Staszałek)]

Hi @jwkim,

Your case is described in the Migration Guide under “Choosing Your IP/FQDN Strategy,” and it is considered an edge case.

If you choose the IP change strategy, Enforced Encryption drives cannot be migrated automatically. Between version 5.9.4.3 and the current releases, a number of communication-related changes were introduced, not solvable in this scenario.

In such cases, users must manually decrypt and re-encrypt every protected drive, or you should consider using the Same IP/FQDN Strategy instead.

(Migrating from a Legacy 5.x Server to 2608 | Netwrix Product Documentation)

BR, Krzysiek