This password is the one that you entered for the database when you installed the management server. When the Certificate Status appears, click on View... Try these resources. Thank You! get redirected here
Click Finish. Veritas does not guarantee the accuracy regarding the completeness of the translation. If the client computer cannot ping or Telnet to the management server, verify the DNS service for the client. The dates, times, server address, and port numbers are available for troubleshooting connection problems.
Due to the nature of this procedure, Symantec Technical Support cannot provide support for this procedure. In the Security Warning dialog, review the URL and other information. Look for the Security Warning dialog. Type the following command: 32-bit operating system: %systemroot%\system32\odbcad32.exe 64-bit operating system: %systemroot%\syswow64\odbcad32.exe In the ODBC Data Source Administrator dialog box, click System DSN.
Check that the management server is not running multiple versions of PHP You can check whether the management server runs multiple software packages that use different versions of PHP. Education Services Maximize your product competency and validate technical knowledge to gain the most benefit from your IT investments. This article describes how to troubleshoot communication issues. Deploy the communication file to the client computer: An additional option in SEP 12.1.2 (RU2) and later is the Communication Update Package Deployment.
Sorry, we couldn't post your feedback right now, please try again later. Click Place all certificates in the following store, click Browse, and then click Trusted Root Certification Authorities. Click Browse, select the certificate file you downloaded in Step 2, and then click Open. Check the inbox logs on the management server You can use a Windows Registry key to generate logs about activity in the management server inbox.
Provide feedback on this article Request Assistance Print Article Products Subscribe to this Article Manage your Subscriptions Search Again Situation You see certificate errors when using a web browser to view The error above is expected because telnet did not provide the expected input per the bpcd protocol. Notice also that 'localhost' is correctly determined not to be a valid NetBackup server. You must first enable the Apache HTTP server Access log before you can view the log. Look for the result that states "TESTS COMPLETED SUCCESSFULLY!".
When you modify the Windows Registry, the management server generates the logs (ersecreg.log and exsecars.log). You can run the tool remotely or save it and then run it on the client computer. Most likely firewall software of some sort; see the Firewall topics above for some possibilities.Checking for Name Resolution DelaysWhen testing connections to bpcd and other daemons be sure to check the time difference delta Within Firefox, go to Options (or Options > Options) > Advanced.
Click Database. Get More Info Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? To verify ODBC connection with the embedded database: Click Start > Run. Translated Content This is machine translated content Login to Subscribe Please login to set up your subscription.
Submit a False Positive Report a suspected erroneous detection (false positive).
If the management server runs the remote SQL database, perform the following actions: Verify that you have specified a named instance when you installed and configured Symantec Endpoint Protection Manager. how SEP is being utilized by the customer base. This is required. No Yes Products Products Home Threat Protection Advanced Threat Protection Endpoint Protection Endpoint Protection Cloud IT Management Suite Email Security.cloud Data Center Security Blue Coat Products Information Protection Data Loss Prevention
Check system requirements Ensure that both the client and the management server meet the minimum or recommended system requirements. For Linux clients, if they are missing a library file required by bpcd or vnetd, you would get this type of error message:telnet localhost 13782Trying 127.0.0.1...Connected to clientname.domainname.comEscape character is '^]'.bpcd: In the right pane, under Symantec Endpoint Protection, click Edit Debug Log Settings. this page Translated Content This is machine translated content Login to Subscribe Please login to set up your subscription.
You should be able to successfully access the web console. Network issues include the firewall blocking access, or networks not connecting to each other. In the Server drop-down list, verify that the correct server and instance is selected. https://tses.symantec.com The article How to test connectivity with Insight and Symantec Licensing servers is a useful resource for troubleshooting any issues.
Translated Content This is machine translated content Login to Subscribe Please login to set up your subscription. Symantec Endpoint Protection licenses cannot be activated when using a proxy server. https://central.ss.crsi.symantec.com https://central.nrsi.symantec.com https://central.avsi.symantec.com https://central.b6.crsi.symantec.com https://central.crsi.symantec.com CAT submissions: Client Authentication Token. If the ping command does not return the correct address, verify the DNS service for the client and check its routing path.
No Yes Menu Close Search SOLUTIONS Solutions Overview Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government PRODUCTS Product Overview Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z SERVICES Click OK, click Next, and then click Finish. When executed, the command does the following. 1. No formal definition created for this item yet.) and if not needed because a formal definition is already created, the client will not submit the sample.
If you use the English version of Symantec Endpoint Protection Manager, use the default sem5. Education Services Maximize your product competency and validate technical knowledge to gain the most benefit from your IT investments. If the client connects, the client's connection problem is probably not a network issue. In the ODBC tab, verify that the Data source name drop-down list is SymantecEndpointSecurityDSN.