DCS Agents on legacy OS' like Windows 2000 that used old protocol versions (TLS 1, TLS 1.1) and ciphers, stopped communicating with DCS Communication server after upgrade to 6.10.
DCS 6.9.x upgraded to 6.10.x
Since DCS 6.10 is not using server.xml to store communication configuration data, additional configuration steps are required after a successful upgrade.
The below example is based on Windows 2000; protocols and ciphers may vary based on the Agent OS.
Before modifying system files, ensure you have created backup copies of application.properties and java.security.
Open ...\Symantec Data Center Security\Server\Communication\application.properties and append TLSv1 and TLSv1.1 to the enabled protocols list:
server.ssl.enabled-protocols=TLSv1,TLSv1.1,TLSv1.2,TLSv1.3
In the same application.properties file, add one of the following cipher suites to server.ssl.ciphers=:
Option A:
server.ssl.ciphers=TLS_RSA_WITH_AES_128_CBC_SHA, TLS_RSA_WITH_AES_256_CBC_SHA
Option B:
server.ssl.ciphers=SSL_RSA_WITH_3DES_EDE_CBC_SHA, SSL_RSA_WITH_RC4_128_MD5, SSL_RSA_WITH_RC4_128_SHA
Open ...\Symantec Data Center Security\Server\Communication\java\conf\security\java.security and remove TLSv1 and TLSv1.1 from the jdk.tls.disabledAlgorithms property.
Updated value:
jdk.tls.disabledAlgorithms=SSLv3, RC4, DES, MD5withRSA, \
DH keySize < 1024, EC keySize < 224, 3DES_EDE_CBC, anon, NULL
Restart the Communication Server and Management Server services to apply the configuration changes.