Troubleshooting Symantec Endpoint Encryption Device Control 8.2.0: Problem with server communication.
|Article:TECH200106|||||Created: 2012-11-26|||||Updated: 2013-10-16|||||Article URL http://www.symantec.com/docs/TECH200106|
The Management Console cannot find the Symantec Endpoint Encryption Device Control Management server when you run it.
This could be occurring for the following reasons:
- When you browse to the server's website it does not request certificate approval or there is no option to export the Symantec Endpoint Encryption Device Control certificate with the private key under the certificate snap in because the SSL certificate is corrupt. To remedy the problem, create a new certificate for the server, and replace the existing one on the Symantec Endpoint Encryption Device Control website. (You may contact Symantec technical support with the full DNS name of the server to create a new certificate.
- Windows 2003 is not allowing files with ASP.net extensions. To allow these file extensions, allow the ASP.net Web service extension under the Web Service Extensions options in the IIS snap in (only available in Windows 2003).
- One or all of the Symantec Endpoint Encryption Device Control services are not running, because they haven't been started under the services snap in. To run the services, first verify that all for Symantec endpoint capitalize that Encryption Device Control services (Broadcast, DB, Local and Domain) have been started.
- When trying to open the IIS snap in, it cannot be opened and/or the IIS admin service cannot be started, because the IIS metabase has been corrupted. Reinstall the IIS to alleviate a corrupted IIS metabase.
- The Symantec Endpoint Encryption Device Control website is stopped in the IIS snap in. To remedy the problem, verify that Symantec Endpoint Encryption Device Control website has been started.
Article URL http://www.symantec.com/docs/TECH200106