View the connection status values. View the access log to see if the client connects to the management server You can view the Apache HTTP server Access log on the management server to check whether the client connects to the management server. Use the ping command on the client computer to test connectivity to the management server On the client computer, open a command prompt.
Type ping and the computer name of the management server, and then press Enter. You can use the server IP address in place of the computer name. The command should return the server's correct IP address. Note: If the ping command doesn't return the correct address, verify the DNS service for the client and check its routing path. Use a browser on the client computer to test connectivity to the management server On the client computer, open a web browser.
Therefore, the issue may be on the client. If the word OK does not appear, the client computer cannot connect to the management server. Therefore, the issue may be on the server. Check for any network problems Verify that there are no network problems by checking the following items: Test the connectivity between the client and management server first. If the client computer cannot ping or Telnet to the management server, verify the DNS service for the client.
Telnet examples: replace Check that the management server doesn't have a network problem. Check that the Endpoint Protection firewall or third-party firewall doesn't cause any network problems. Check debug logs on the client computer If the client has communication problems with the management server, status messages about the connection problem appear in the client's debug logs.
You can check the debug logs by using the following methods: In the SEP client, click Help , and then click Troubleshooting. In the left pane, click Debug Logs.
The file should be in one of these locations:. At the beginning of each LiveUpdate cycle, the LiveUpdate version will be shown. Please proceed to Step 4, if the correct version is shown. Assume the wrong LiveUpdate version is installed on the system, locate the LiveUpdate installer shipped with your release of SEP as per above.
Open a command prompt and change directory to the following path or the relevant path for the current installation. Move the. This technique enables you to change the normal portion of the installation path during a migration, when applicable. Question: Is anyone that is still using 11 considering migrating to something else or just upgrading to 12?
Looked through SW and google and have not come up with something I feel comfortable with. Obviously free will not compare to commercial license, but I was sort of seeking a temporary band-aid, till they are in a position to purchase Symantec again. In these you won't get all the features like EE but will get equal protection. Can email at license symantec.
To continue this discussion, please ask a new question. Get answers from your peers along with millions of IT pros who visit Spiceworks. Popular Topics in Symantec. Which of the following retains the information it's storing when the system power is turned off? Submit ». Bud G. This person is a verified professional. Verify your account to enable IT peers to see that you are a professional. Have you tried opening the SEP control panel and updating it from there?
Hello, What version of SEP are you currently running? In your case, since this issue is happening only on some clients, you would have to check - 1 If these clients are from the same group? If yes, Issue at group level. Let us know. Once the tool has been run the clients will show they are off line and start to check in depending on what communications settings. This could take an hour or more. If you see a broken image, please right-click and select 'Open image in a new tab'.
0コメント