![]() ![]() One of the two Citrix virtual loopback policies required needs a list of names of apps that will get the redirected addresses, each on their own lines, for example SomeApp.exeĪnd those must match exactly to the names of the processes that are using TCP/IP. But for the future person who finds this problem in their work. Sigh, I end up answering my own question. Has anyone seen this problem, and what was the answer you found for it? Perhaps I've missed something there though? ![]() It's also apparently impossible to change, since it's a byproduct. NET web stack, since the test app is actually running under my user name. My colleague speculates that the problem is that the app we created runs as System, but as far as I can tell, that is a byproduct of using the. Java get REAL loopback address programmatically).īTW, the local port can't just be changed programmatically for each instance because the REST call is used to get the session's specific app instance, and so if ports were varied, the JavaScript would have to know the right one in advance, defeating the purpose. So now I am trying workarounds now that might help or not, such as using IPAddress.Loopback and ensuring that the IP address is IPv4 (which was found to make a difference for the similar Java problem years ago, seen in this StackOverflow Q/A: However, when I tried using 127.0.0.1 in the code, thinking the settings might redirect transparently despite it being spelled out, that didn't work at all. That part makes sense to me now, basically. In our code, using localhost as a literal resolves to 0:0:0:0, which isn't part of the 127.x.x.x series and so that fails. This isn't a problem of the browser not finding the right address either that would be set up with the Citrix policy, but the fail is occurring when our app starts and only the first instance can bind to the socket (naturally). This is a two-part policy in Citrix (setting it up in general, and naming the apps that can use the redirection), and both were set up properly. In contrast, a colleague worked with the Citrix approach using a Python test app as an experiment, and that worked fine. Īnd basically, it doesn't work for us with. Virtual Loopback basically allows a different "local host" for each session, in the form 127.0.0.1, 127.0.0.2, 127.0.0.3, and so on. For the moment we are trying Virtual Loopback. Each instance of the app must respond to browser JavaScript that is fetching from localhost:xxxx, with xxxx always being the same port number.Ĭitrix supplies something called Virtual Loopback for this, and also discusses Windows' Virtual IP for it. This app runs multiple times on one Citrix server, once for each user, as part of their Citrix session. NET / WPF app to customers who use Citrix XenApp (or whatever it has been renamed to). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |