The SEP client can access the SEPM via the defined communication port, but can not connect to the SEPM. Replacing the sylink.xml and disabling the proxy setting in the Internet Explorer (IE) configuration does not resolve the issue.
In the registry of the SEP client, the following values display for the proxy settings:
After deleting the above value and rebooting, the registry value is restored automatically.
The sylink debug log displays: "Unable to create Session with 'No Proxies' settings - Error Code: 87"
The Web Proxy Auto-Discovery Protocol (WPAD) configuration is set on the DHCP Server, which will enforce the DHCP client proxy settings to be automatically rewritten. Deleting the DefaultConnectionSettings value in the registry and rebooting the SEP client will not change the scenario as the WPAD configuration for the proxy settings will be reassign to the client again after the reboot.
Upgrade the SEP client to SEP 11 RU6 MP3 (Fix ID: 2125088) or later.
For information on how to obtain the latest build of Symantec Endpoint Protection, read Obtaining an upgrade or update for Symantec Endpoint Protection.
Change the proxy setting for the WPAD configuration or remove the WPAD configuration from the DHCP server.
The SEP client and the SEPM are in same subnet. The SEP client receives an IP address from the DHCP server. Internet Security and Acceleration (ISA) server is installed with the DHCP server on the same host.
Rate this Article
This is machine translated content
Login to Subscribe
Please login to set up your subscription.
Didn't find the article you were looking for? Try these resources.