Cause A

The IP of the Management Server is unresolvable from the Windows File Server agent.

Cause B

The Windows File Server trying to register is of version 4.5 while the Management Server is of version 5.2 or above. The registration fails due to security protocol changes regarding TLS and SSL. From DI 5.2 onward SSL and TLSv1 protocols have been disabled. However, Windows File Server agents version 4.5 are not compatible with TLSv1.1 and TLSv1.2 protocols and hence fail to communicate/register with MS of version 5.2 or above.

Solution

For Cause A

Resolved by adding the IP of the Management Server to the hosts file on Filer:

1. Add MS IP to etc\hosts file (C:\windows\system32\drivers\etc\hosts) as <ip> <MS_hostname>
2. Try resolving the IP of the MS from Filer now and confirm it is accessible.
3. Run the installer/registration again.

Verify the installation and configuration is successfully.

For Cause B

1. Stop the Data Insight services on the problem Windows File Server.
2. Rename the JRE folder. The default location is C:\ProgramFiles\Symantec\DataInsight\jre to .old
3. From any other Windows File Server of version 5.2 or above, copy the JRE folder. The default location being C:\ProgramFiles\DataInsight\JRE.
4. Paste it on the problem File Server at C:\ProgramFiles\Symantec\DataInsight\jre
5. Start the Data Insight services.
6. Manually run the RegisterWorkerNode.exe from the BIN folder. The default location is C:\ProgramFiles\DataInsight\bin.
7. The Filer should now be listed under the list of Windows Filer list with status as "Healthy".

NOTE: The locations for the JRE and BIN folder may vary based on initial DI install settings.