Here an article about an SSL issue when launching applications via Citrix Netscaler. When trying to launch applications, upon clicking the icon, users receive SSL Error 38. The error message reads as follows: “Cannot connect to the Citrix Presentation Server. SSL Error 38: The proxy denied access to…” Cause This is possibly because of licensing restrictions as indicated in the
Steve Thomas, Senior Support Escalation Engineer at Microsoft, published an article about a recent issue where streaming may fail when using a Netscaler load balancer. Load balancers are common when using App-V in an RTSP streaming mode (one that leverages either the management server or the streaming server), however on some third-party load balancers special adjustments may be necessary. For
Citrix has made two changes to the “free” NetScaler VPX offerings. Specifically, Citrix has : Changed NetScaler VPX Express from 1 Mbps to 5Mbps Added a new “free” offering, VPX Developer Edition, a throughput-limited Platinum version that is available only to NetScaler customers. Citrix will continue to offer a time-limited evaluation of Platinum Edition as well. To make VPX Express
Citrix Blog posted another post about Citrix NetScaler. It is already hardended and only VIP’s will respond to TCP handshakes. However here are some more considerations for hardening your deployment. Hardening takes place by implementing the following on the Citrix NetScaler Load Balancer – Securing NetScaler system communication, Access Control Lists (ACL), Securing the NetScaler system using RPCNode and External authentication.
Configuring Redirection Mode You can configure a Load Balancing HTTP or HTTPS VServer with a redirect URL on theCitrix NetScaler Load Balancing VIP. This URL can be sent as a response to the client HTTP or HTTPS request if the VServer is not available. The common usage of this option is to direct the client to a customized Site Down
Preventing overload When you configure a NetScaler to use a metric-based load balancing method such as Least Connections, Least Response Time, Least Bandwidth, Least Packets, or Custom Load, the load balancing method will initially start out as Round Robin for what is called a slow start period. NetScaler appliances use the configured load balancing method to determine the appropriate service for forwarding
Load balancing uses a number of algorithms, called load balancing methods, to determine how to distribute the load among the servers. When a Load balancer is configured to use the least packets method, it selects the service with the least number transmitted and received packets. Least Packets Load balancing allows you to distribute client requests across multiple servers to optimize resource utilization. Load balancers
Load balancing uses a number of algorithms, called load balancing methods, to determine how to distribute the load among the servers. When a Load balancer is configured to use the token method, it selects a server based on the value of a token extracted from the client request. You can configure the location and size of the token. For subsequent requests with
Custom Load balancing allows you to distribute client requests across multiple servers and optimize resource utilization. Load balancers improve server fault tolerance and end-user response time. In a scenario with a limited number of servers providing service to a large number of clients, a server can become overloaded and degrade server performance. Load balancing is used to prevent bottlenecks by forwarding the
