Open the URL below in your web browser:
If you are given the option to download the metadata file, you are connected to the repository. If you cannot access the repository, contact your system administrator to resolve firewall issues.
Make sure you have HTTP 1.1 enabled when accessing the repository or ESET update servers via 3rd party proxy. This applies to all products that have access to ESET repository.
Do not use an IP address to access the ESET repository.
Open ESET Security Management Center Web Console (ESMC Web Console) in your web browser and log in.
Click More → Server Settings and expand Advanced Settings. In the Repository section, type the ESMC repository URL into the Server field and click Save to apply the changes. You can override the automatic selection of repository server by changing the default ERA repository URL to a repository based in the USA: http://repositorynocdn.eset.com/v1
Figure 1-1
Click the image to view larger in new window
Open ESET Security Management Center Web Console (ESMC Web Console) in your web browser and log in.
Click Policies.
Select the agent policy you need to change, click the gear icon and then select Edit.
Figure 2-1
Click the image to view larger in new window
Expand Settings → Advanced settings. In the Repository section, type the ESMC repository URL (http://repositorynocdn.eset.com/v1) into the Server field.
Choose Apply or Force and click Finish.
Figure 2-2
Click the image to view larger in new window
Check your connection to the repository again. If your connection continues to fail, proceed to Part IV.<./p>
In Windows Explorer, navigate to one of the following folders, depending on your operating system:
In the path above, find and rename the Crypto folder to "Crypto old." If you cannot rename the folder, right-click it, select Copy from the context menu, right-click in the present folder and then select Paste from the context menu (this copy will serve as a backup).
After making a backup, delete the original Crypto folder.
The Crypto folder will be re-created automatically, and the connection to the repository should now be functional. Test your connection to the ESMC repository as described in Part I.