Proxy Server Error Code 87
VIP Managed PKI Service VIP Access Manager Small Business Endpoint Protection Cloud Ghost Solution Suite Endpoint Encryption SSL/TLS Certificates Code Signing Norton Shopping Guarantee SHOP ONLINE Website Security SSL Certificates Complete Website Security Code Signing Certificates Norton Shopping Guarantee Buy SSL Products A-Z Services Services Home Business Critical Services Consulting Services Customer Success Services Cyber Security Services Education Services Solutions Solutions Home Intelligent Solutions Intelligent Endpoint Intelligent Cyber Operations Intelligent Data Protection Intelligent Email Intelligent SMB Blue Coat Solutions Topics Encryption Everywhere Internet of Things Office 365 Security Industries Automotive Cyber Insurance Education Financial Services Global Service Providers Industrial Control Systems Healthcare Retail Government Federal Government State & Local Support Center Symantec Support Blue Coat Support Symantec Connect Buying Programs Upgrading Products Maintenance & Renewals Training Security Center Security Center Home Updates Virus Definitions & Updates Threats, Risks & Vulnerabilities Security Advisories Publications ISTR Blogs Security White Papers Tools Removal Tools Spyware Removal English 中文(简体) 中文(繁體) Česká English Français Deutsch Magyar Italiano 日本語 한국어 Polski Português Pусский Español Partner Find a Partner Enroll in a Partner Program Partner Programs Product Resources for Partners Blue Coat Partners Login Required Partner Resources Products A-Z Financial Benefits Partner Licensing Partner Renewals Partner Training United States / English Search Technical Support Support MySymantec Licensing Products A-Z Login Profile Subscriptions Logout Login Forgot Password? Don't have a SymAccount? Create a SymAccount now!' SEP client is not able to communicate with SEPM TECH139251 August 16th, 2011 http://www.symantec.com/docs/TECH139251 Support / SEP client is not able to communicate with SEPM Did this article resolve your issue? Thank you for your feedback! Provide feedback on this article Request Assistance Pr
日本語 Español Help Video Screencast Help Usage of Proxy Settings in SEP 11.x Client Communication Created: 06 Mar 2011 • Updated: 14 Mar 2011 | 3 comments Language TranslationsMachine TranslationsDeutsch Français Español 简体中文 日本語 Nirav Mistry +1 1 Vote Login to vote Tweet Overview When SEP first starts, it attempts to connect to SEPM without using a proxy. Regardless of the proxy setting the client always attempt to connect without a proxy first. If the client is unable to connect to any servers in its management server list, it will rotate its proxy settings at the end of the heartbeat. The next https://support.symantec.com/en_US/article.TECH139251.html heartbeat will be attempted with proxy settings (if available). Once SEP is able to connect, it will not change its proxy settings until it is restarted. You could say it ‘locks’ the setting once it connects. This means that if the client connects without proxy, it will never connect via the proxy until it is restarted. If the client connects though the proxy, it will never http://www.symantec.com/connect/articles/usage-proxy-settings-sep-11x-client-communication connect directly to SEPM until it is restarted. Whichever one works first, that is the one the client will always use. The Three Proxy Settings Sylink has 3 proxy settings. They are settings 1, 2 and 3. Proxy setting 1 mean no proxy. This is the first setting that is tried. Proxy settings 2 and 3 both use the proxy. There is a difference in the way the proxy settings are called, but functionally it is very much the same. When the client first starts, it will try to use each proxy setting in turn, starting with setting one, down to setting 3. After that it starts again from setting 1 again. Sylink Logs Log entries are created in the Sylink Log when the client sets the proxy settings. Here are some example of the Sylink Log entries. There logs appear when the client first starts, before the first heartbeat. 06/02 10:51:34 [4260]
not all, available error codes in libcurl. Why they occur and possibly what you can do to fix the problem are also included. CURLcode Almost all "easy" interface functions return https://curl.haxx.se/libcurl/c/libcurl-errors.html a CURLcode error code. No matter what, using the curl_easy_setopt option CURLOPT_ERRORBUFFER is a good idea as it will give you a human readable error string that may offer more details about the cause of the error than just the error code. curl_easy_strerror can be called to get an error string from a given CURLcode number. CURLcode is one of the following: CURLE_OK (0) All fine. proxy server Proceed as usual. CURLE_UNSUPPORTED_PROTOCOL (1) The URL you passed to libcurl used a protocol that this libcurl does not support. The support might be a compile-time option that you didn't use, it can be a misspelled protocol string or just a protocol libcurl has no code for. CURLE_FAILED_INIT (2) Very early initialization code failed. This is likely to be an internal error or problem, or a proxy server error resource problem where something fundamental couldn't get done at init time. CURLE_URL_MALFORMAT (3) The URL was not properly formatted. CURLE_NOT_BUILT_IN (4) A requested feature, protocol or option was not found built-in in this libcurl due to a build-time decision. This means that a feature or option was not enabled or explicitly disabled when libcurl was built and in order to get it to function you have to get a rebuilt libcurl. CURLE_COULDNT_RESOLVE_PROXY (5) Couldn't resolve proxy. The given proxy host could not be resolved. CURLE_COULDNT_RESOLVE_HOST (6) Couldn't resolve host. The given remote host was not resolved. CURLE_COULDNT_CONNECT (7) Failed to connect() to host or proxy. CURLE_FTP_WEIRD_SERVER_REPLY (8) The server sent data libcurl couldn't parse. This error code is used for more than just FTP and is aliased as CURLE_WEIRD_SERVER_REPLY since 7.51.0. CURLE_REMOTE_ACCESS_DENIED (9) We were denied access to the resource given in the URL. For FTP, this occurs while trying to change to the remote directory. CURLE_FTP_ACCEPT_FAILED (10) While waiting for the server to connect back when an active FTP session is used, an error code was sent over the control connection or similar. CURLE_FTP_WEIRD_PASS_REPLY (11) After having sent the FTP password to the server, libcurl ex