How to Pass the Client's Source Port to the Backend Server When Accessed Through NetScaler

To achieve this, we would have to disable the Use Proxy Port option.

To configure the Use Proxy Port setting on a service by using the configuration utility:

  1. Navigate to Traffic Management> Load Balancing > Services, and open a service.
  2. In Advanced Settings, select Traffic Settings, and unselect Use Proxy Port.

To configure the Use Proxy Port setting on a service by using the CLI:

At the command prompt, type:

set service svc -useproxyport NO

The Use Proxy Port option works only when the Use Source IP/ Use Client IP option is enabled on the Service/Service Group respectively.

Also, this option is enabled by default for TCP-based service types, such as TCP, HTTP, and SSL,

This will allow the backend server to see client IP and source port from which the client tries to connect.

Related:

  • No Related Posts

Communication times out while forwarding to RemoteHcl WCF server

Specify the cloud connector FQDN in the WinHTTP proxy bypass list. The following example shows the addition of the cloud connector with an FQDN of `bvcchard2.hardening.local` to the WinHTTP proxy bypass list:


After setting the bypass list, restart the cloud connector to apply the new WinHTTP settings.

Important

When specifying the bypass list, use semicolons, not commas, to separate the items in the list. The netsh winhttp set proxy command accepts the comma syntax, but the resulting bypass list is ignored. Do not use “*” wildcards when performing this operation.

For example:

netsh winhttp set proxy proxy-server=”http=10.10.10.50:8080;https=10.10.10.50:8080″ bypass-list=”<-loopback>;bvcchard2.hardening.local”

In the example above, the IP addresses are the proxy server and port.

Related:

Communication times out while forwarding to RemoteHcl WCF server (HclOverWebsockets feature toggle enabled)

Specify the cloud connector FQDN in the WinHTTP proxy bypass list. The following example shows the addition of the cloud connector with an FQDN of `bvcchard2.hardening.local` to the WinHTTP proxy bypass list:


After setting the bypass list, restart the cloud connector to apply the new WinHTTP settings.

Important

When specifying the bypass list, use semicolons, not commas, to separate the items in the list. The netsh winhttp set proxy command accepts the comma syntax, but the resulting bypass list is ignored. Do not use “*” wildcards when performing this operation.

For example:

netsh winhttp set proxy proxy-server=”http=10.10.10.50:8080;https=10.10.10.50:8080″ bypass-list=”<-loopback>;bvcchard2.hardening.local”

In the example above, the IP addresses are the proxy server and port.

Related:

Error: “Previous Upload to cis.citrix.com failed. Network Error While Connecting cis.citrix.com” with Code 10


The error message indicates that the Call Home upload toCitrix.comfailed. This can happen due to multiple reasons, including there was simply no connectivity from the License Server toCitrix.com, or the presence of a Firewall or Network Proxy in the environment.


To troubleshoot the underlying cause of the failure, please follow the steps below:

  1. Make sure the License Server has network connectivity and can connect tocis.citrix.comover port 443
  2. If you will have to configure a proxy, please refer to the following documentation for the steps:Configure a Proxy server.Please note that Licensing service needs to be restarted for the changes to take effect.
  3. If there are no proxies required to reachcis.citrix.comfrom the server, it is possible that there was a network error at the time of upload attempt and that has been resolved since then. Once an upload fails, the Upload failure status is tracked through an XML file (Upload_result.xml). So even when the network issue is resolved or when Call Home is subsequently disabled after an upload failure, unless the XML file is manually deleted, you will continue to see the error. The following steps will get rid of the error message:
    1. Browse toC:Program Files (x86)CitrixLicensingLSresourceusagefolder.
    2. Take a copy of the contents of this folder for backup purposes and empty this folder.
    3. Restart theCitrix Webservice for Licensing servicefrom the Services console.
  4. If none of the steps above resolved the issue, you can disable Call Home following the steps outlined inCTX220679

Related:

Error: Previous Upload to cis.citrix.com failed. Uploader failed for reason “Network Error while connecting cis.citrix.com” with code 10


The error message indicates that the Call Home upload toCitrix.comfailed. This can happen due to multiple reasons, including there was simply no connectivity from the License Server toCitrix.com, or the presence of a Firewall or Network Proxy in the environment.


To troubleshoot the underlying cause of the failure, please follow the steps below:

  1. Make sure the License Server has network connectivity and can connect tocis.citrix.comover port 443
  2. If you will have to configure a proxy, please refer to the following documentation for the steps:Configure a Proxy server.Please note that Licensing service needs to be restarted for the changes to take effect.
  3. If there are no proxies required to reachcis.citrix.comfrom the server, it is possible that there was a network error at the time of upload attempt and that has been resolved since then. Once an upload fails, the Upload failure status is tracked through an XML file (Upload_result.xml). So even when the network issue is resolved or when Call Home is subsequently disabled after an upload failure, unless the XML file is manually deleted, you will continue to see the error. The following steps will get rid of the error message:
    1. Browse toC:Program Files (x86)CitrixLicensingLSresourceusagefolder.
    2. Take a copy of the contents of this folder for backup purposes and empty this folder.
    3. Restart theCitrix Webservice for Licensing servicefrom the Services console.
  4. If none of the steps above resolved the issue, you can disable Call Home following the steps outlined inCTX220679

Related:

Error: “Previous Upload to cis.citrix.com Failed. Network Error While Connecting cis.citrix.com” with Code 6

The error message indicates that the Call Home upload toCitrix.comfailed. This can happen due to multiple reasons, including there was simply no connectivity from the License Server toCitrix.com, or the presence of a Firewall or Network Proxy in the environment.


To troubleshoot the underlying cause of the failure, please follow the steps below:

  1. Make sure the License Server has network connectivity and can connect tocis.citrix.comover port 443
  2. If you will have to configure a proxy, please refer to the following documentation for the steps:Configure a Proxy server.Please note that Licensing service needs to be restarted for the changes to take effect.
  3. If there are no proxies required to reachcis.citrix.comfrom the server, it is possible that there was a network error at the time of upload attempt and that has been resolved since then. Once an upload fails, the Upload failure status is tracked through an XML file (Upload_result.xml). So even when the network issue is resolved or when Call Home is subsequently disabled after an upload failure, unless the XML file is manually deleted, you will continue to see the error. The following steps will get rid of the error message:
    1. Browse toC:Program Files (x86)CitrixLicensingLSresourceusagefolder.
    2. Take a copy of the contents of this folder for backup purposes and empty this folder.
    3. Restart theCitrix Webservice for Licensing servicefrom the Services console.
  4. If none of the steps above resolved the issue, you can disable Call Home following the steps outlined inCTX220679

Related:

License Server – Call Home Failing and Logging an Error in Director – Uploader Failed “Network SSL Error When Connecting to citrix.com” Code 7

The error message indicates that the Call Home upload tocis.citrix.comfailed. This can happen due to multiple reasons, including there was simply no connectivity from the License Server tocis.citrix.com, or the presence of a Firewall or Network Proxy in the environment.

To troubleshoot the underlying cause of the failure, please follow the steps below:

  1. Make sure the License Server has network connectivity and can connect tocis.citrix.comover port 443
  2. If you will have to configure a proxy, please refer to the following documentation for the steps:Configure a Proxy server.Please note that Licensing service needs to be restarted for the changes to take effect.
  3. If there are no proxies required to reachcis.citrix.comfrom the server, it is possible that there was a network error at the time of upload attempt and that has been resolved since then. Once an upload fails, the Upload failure status is tracked through an XML file (Upload_result.xml). So even when the network issue is resolved or when Call Home is subsequently disabled after an upload failure, unless the XML file is manually deleted, you will continue to see the error. The following steps will get rid of the error message:
    1. Browse toC:Program Files (x86)CitrixLicensingLSresourceusagefolder.
    2. Take a copy of the contents of this folder for backup purposes and empty this folder.
    3. Restart theCitrix Webservice for Licensing servicefrom the Services console.
  4. If none of the steps above resolved the issue, you can disable Call Home following the steps outlined inCTX220679

Related:

Error: “Previous Upload to cis.citrix.com Failed. Network Error While Connecting cis.citrix.com” with Code 5

The error message indicates that the Call Home upload to Citrix.com failed. This can happen due to multiple reasons, including there was simply no connectivity from the License Server to Citrix.com, or the presence of a Firewall or Network Proxy in the environment.

To troubleshoot the underlying cause of the failure, please follow the steps below:

  1. Make sure the License Server has network connectivity and can connect to cis.citrix.com over port 443
  2. If you will have to configure a proxy, please refer to the following documentation for the steps: Configure a Proxy server. Please note that Licensing service needs to be restarted for the changes to take effect.
  3. If there are no proxies required to reach cis.citrix.com from the server, it is possible that there was a network error at the time of upload attempt and that has been resolved since then. Once an upload fails, the Upload failure status is tracked through an XML file (Upload_result.xml). So even when the network issue is resolved or when Call Home is subsequently disabled after an upload failure, unless the XML file is manually deleted, you will continue to see the error. The following steps will get rid of the error message:
    1. Browse to C:Program Files (x86)CitrixLicensingLSresourceusage folder.
    2. Take a copy of the contents of this folder for backup purposes and empty this folder.
    3. Restart the Citrix Webservice for Licensing service from the Services console.
  4. If none of the steps above resolved the issue, you can disable Call Home following the steps outlined in CTX220679

Related: