Nx Servers can't see each other after upgrading to Nx Witness 3.0.

Certain server configurations in multi-server Systems might lose connectivity after upgrading to Nx Witness 3.0.

During the upgrade from version 2.6 or lower, no servers show up. In fact, you can see that all of them are running and allow connecting directly with Nx Desktop or Nx Web Admin. All other servers at that moment are shown as "offline" in the Resource Tree.

If you check the System Administration > Routing management tab and click any offline server, you'll see all network addresses with "0" port values:

Important Note! This article doesn't cover cases when some of the essential nodes just won't run after the upgrade. I.e. they are unavailable for the connection from local PC using browser thus blocking connectivity proxy for other hosts. Such issues should be addressed directly to our support staff.

This issue may occur if all your servers are located in the same local network and one of the following conditions is satisfied:

• Enable cameras and servers autodiscovery in System Administration is turned off before the upgrade.
• Multicast communication is intentionally disabled at your network on the networking hardware level by system administrators.

We're going to improve Nx Witness so that such situations are resolved automatically during the database migration. It's likely that version 3.1 won't have such issues, but before that, we suggest the following to resolve the issue manually:

1. If you have the autodiscovery option disabled -- please turn it on until servers find each other (typically occurs within several seconds). To turn it on:
   a. Open System Administration (Ctrl+Alt+A).
   b. In the General tab, find the System Settings section and check the box for Enable cameras and servers autodiscovery.
   c. Click OK or Apply to save changes.
2. If you already have auto-discovery enabled but there's still no communication and servers have "0" port values in Routing Management,  you likely have multicast connections disabled on the networking level. Do the following to modify this port information:
   a. Open System Administration (Ctrl+Alt+A).
   b. In the Routing Management tab click any "offline" server.
   c. Click Add. The Enter URL dialog window will pop up.
   d. Input the network interface address which is used for connection to other servers with the correct TCP port specified to the URL bar.
   

   Input the corresponding address for your server, the screenshot below uses 192.168.0.150 as an example. If the port used in version 2.6 is different from 7001 you'll also have to specify it.
   
   

   e. Click OK or Apply to save changes. Typically, it takes seconds to get the server back online.

Questions

If you have any questions related to this topic or you want to share your experience with other community members or our team, please visit and engage in our support community or reach out to your local reseller.