![]() When a connection comes to the StoreFront it can match it against the gateway URL or the SNIP (if that’s defined) and thus identify if the connection is external or internal. Each gateway definition contains the URL of the gateway as well as a NetScaler SNIP address ( now optional the article I link to is a good read btw). StoreFronts have a list of gateways corresponding to the various NetScaler gateways that can connect to its stores. logging in and getting a list of resources etc, nothing to do with ICA files or launching a resource (which is what I am interested in). Note: this is for connecting to a store – i.e. Basically a store has an internal URL and an external URL (via gateway) and once you add a store to Citrix Receiver the Receiver uses beacons to identify if its internal or external and use the correct URL. How does the StoreFront know the connection is via a gateway? There’s this thing of “ beacons” which is supposed to help detect if a connection is external or internal but that’s used by the receiver, not by the StoreFront. Ok, so the StoreFront is the one who generates the ICA file. The StoreFront passes this ICA file to the gateway if its an external connection, or to the receiver / browser directly if its an internal connection.Depending on whether the connection is internal or via gateway the StoreFront server will put in the correct address in the ICA file.The ICA file is based on a template, per store, and can be found at C:\inetpub\ The StoreFront will create an ICA file and send to the user. ![]() The XML/ STA service will put all this information in an STA ticket (basically an XML file) and send back to the StoreFront server.StoreFront contacts the XML/ STA service on the Delivery Controller which will decide where to launch the resource on (which server/ desktop etc).This request makes its way to the StoreFront server – either directly or via NetScaler. Upon login via NetScaler (or directly) the StoreFront creates a page with all the available resources.Found this excellent blog post (cached PDF version just in case) on the flow of traffic and that confirmed that it is the StoreFront who generates the ICA file. information, or they knew I was connecting externally but choosing to not input the gateway information. Either they were wrongly detecting my external connection attempt as coming internally and hence skipping out the STA etc. Everything was configured correctly as far as I could see, but obviously something was missing.įirst question: who generates the ICA file? As far as I know it is the StoreFront, but was I sure about that? Because whoever was generating the ICA file wasn’t doing a good job of it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |