> Source: [sk104657](https://support.checkpoint.com/results/sk/sk104657)

# sk104657 - Manual IPS update in SmartDashboard fails to start when Proxy is configured.

| Property | Value |
|----------|-------|
| Solution ID | sk104657 |
| Date Created | 2015-02-09 |
| Last Modified | 2017-08-29 |
| Technical Level | General |
| Products | Security Gateway, SmartConsole |
| Versions | R82.10, R82, R81.20, R82.10, R82, R81.20 |
| OS | Windows |

## Symptoms

- * Manual IPS update fails to start even when improved SmartConsole from [sk98078](http://supportcontent.checkpoint.com/solutions?id=sk98078) is installed.

* Possible TraceUtil debug output (global-rule-editor level) (per [sk112334](http://supportcontent.checkpoint.com/solutions?id=sk112334)) while initiating IPS update from the SmartConsole shows:

  ```
  
  * Could not resolve proxy: ; Host not found
  * Closing connection #0
  * Couldn't resolve proxy name
  ... ... ...
  [FDT] [ERROR] http_client_get: Operation failed. curl returned: Errorcode=5. Error String:Couldn't resolve proxy name
  FDT_get_data: http_client_get returned: 6
  [ERROR] FDT_get_data: Failed to get data (curl error: 6) from https://updates.checkpoint.com/WebService/services/DownloadMetaDataService?wsdl
  ... ... ...
  diffFields ("fdt_proxy_address: changed from 'none' to 'http://' ;fdt_use_proxy: changed from 'false' to 'true';")
  :diffFieldsName ("fdt_proxy_address changed from 'none' to 'http://' ;fdt_use_proxy changed from 'false' to 'true';")
  ```

* Proxy is configured via Active directory GPO and the proxy name from the debugs does not appear in the AD configuration under Group Policy Objects.

* Security Gateway logs do not show drops or blocks for the update attempts.

* Connecting to update servers ([sk83520](http://supportcontent.checkpoint.com/solutions?id=sk83520)) is possible via CLI on the Security Management and Security Gateways.

* Possible TraceUtil debug shows that Proxy information, could not be found under the relevant Registry path: "HKEY_CURRENT_USER\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Internet Settings\\ProxyServer" Though, No proxy configuration could be found and Thus Proxy is defined as "None" - :diffFields ("fdt_proxy_address: changed from 'http://' to none' ;fdt_use_proxy: changed from 'true' to 'false';")
* Looking into the customer Proxy script in use, it can be confirmed that the script injects the Proxy value into a wrong Registry path, for example: "\[HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\windows\\currentversion\\Internet Settings\]" Instead of - "\[HKEY_CURRENT_USER\\Software\\Microsoft\\CurrentVersion\\Internet Settings\]"
* The Proxy URL path in the correct Registry path: "\[HKEY_CURRENT_USER\\Software\\Microsoft\\CurrentVersion\\Internet Settings\]" is resolved by the Client into wrong IP address by the DNS server/ This can be confirm by pinging the Proxy URL shown in the TraceUtil debugs and compare with IP address the URL is resolved to.
* No Proxy server value can be found under the correct Registry path: "\[HKEY_CURRENT_USER\\Software\\Microsoft\\CurrentVersion\\Internet Settings\]"

## Cause

**This issue is not related to Check Point software.**

The registry value on the Windows client - "HKEY_CURRENT_USER\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Internet Settings\\ProxyServer" is populated with incorrect Proxy address.

## Solution

**Configure the Group Policy (User Policies) in the Active Directory with the correct Proxy address** (refer to the relevant Microsoft documentation).

This should update the Windows Clients with the correct value in  
HKEY_CURRENT_USER\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Internet Settings\\ProxyServer

**Important: See [Third-Party Software Disclaimer](https://www.checkpoint.com/third-party-software-disclaimer/index.html)**

---

# Agent Instructions

This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products.

## Navigating This Knowledge Base

- **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt)
- **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml)
- **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}`
- **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content