Using Terminal Server Proxy webapps with Round Robin DNS

Using Terminal Server Proxy webapps with Round Robin DNS

My Terminal Server Proxy webapp does not always connect to my backend server, when using the Round Robin DNS name. If we go directly to one of the relays, we can connect 100% of the time.



Assign individual DNS names to your relay IP addresses. 
relay1.example-cloud.com 
relay2.example-cloud.com 
etc... 

Add those DNS names to the Virtual Hosts section of the respective relay objects. 

Create your Terminal Server Proxy webapp and get it working. 
When editing the webapp object, make a note of the webapp DN. 
This is listed at the top of the properties page when editing the webapp object. 
It looks something like : cn=mywebapp,ou=WebApps,ou=webNetwork,o=stoneware 

Assign the link to your test account. Test the link and make sure it works properly. 

Assign this "rights" link to all users who will eventually have access to this webapp. 

Remove the visible option for the "rights" link so it does not show up on the users' menu. 

This link will act as a way to give users rights to the back end web server. 

Next, make a standard link. We are going to set the url to launch the application from a specific relay. 
This is done by using the webapplication's DN that you made a note of earlier. 
Set the URL for the standard link to https://relay1.example-cloud.com/StartWebApplication/cn=mywebapp,ou=WebApps,ou=webNetwork,o=stoneware. 

Set a restriction on the link to only be visible on that specific relay. 
Now assign this link to the appropriate users. 

Login to that relay and test, this should work just like the original "rights" link that you originally created. 

Now make as many separate links like the above, changing the relay DNS and restriction as needed. 

Common quesions 
1) What is the "rights" link for ? 

Answer :
All access to webapplications is granted to users via link objects.  If users do not have access to a link that is a webapplication type link then they will not have access to the back end server. 

2) Why does the "rights" link not need to be visible? 
Answer : Because it is just granting the user rights, all of the launching of the webapp is done with the standard links. 

We are investigating methods of automating this process in our code, so that this method isn't necessary.


    Can't find the KB

    Unable to find the KB to address your issue ?  

      • Recent Articles

      • Lenovo Unified Workspace End-of-Life Questions and Answers

        Will the shutdown of LUW servers and access to downloads affect my server licensing? No, the shutdown of the customer servers and access to the product and licensing downloads will not affect your server licensing. This license is downloaded and ...

      • How do I determine my Unified Workspace license expiration date?

        The best method for determining the licensing information including the expiration date of your Unified Workspace license: Login to your 8090 management console on each server This may take remoting into each LUW server and relay, opening a browser, ...

      • Lenovo Unified Workspace 7.0.2.13 Released

        Highlights of Unified Workspace 7.0.2.13 Before you install: Please view the installation notes here. 7.0.2.13 requires a 7.0 license file. Below is a list of enhancements and fixes released in Unified Workspace 7.0.2.13 Fixed external storage ...

      • LanSchool Documentation Guides

        LanSchool Classic Teacher Console The LanSchool Teacher Console is the interface teachers will use to manage their classroom and students. It contains all the tools necessary for a teacher to effectively interact with students and create a ...

      • Lenovo Unified Workspace 7.0.1.41 Released

        Highlights of Unified Workspace 7.0.1.41 Before you install: Please view the installation notes here. 7.0.1.41 requires a 7.0 license file. Below is a list of enhancements and fixes for Unified Workspace 7.0.1.41 Updated Log4j Updated Java Updated ...

      • Related Articles

      • Issues with Round Robin DNS and webNetwork

        Round Robin DNS is considered the "poor mans load balancer"  You can find the information about it at WikipediA.  In general Round-Robin DNS works well with static web sites.  Once dynamic information is utilized then there may be problems.  The ...

      • SSLVPN Terminal Server webapps through Safari on Mac with Java 1.7 not connecting

        Customer is trying to launch a SSLVPN Terminal Server webapp using Safari on their Mac. The are receiving the following error:  "Received and error connecting to 127.0.0.1"  Webapp connects fine using Firefox.  Customer is using the latest version of ...

      • Launching mstsc.exe using Slingshot and Generic TCP Proxy webApps

        Issue: The old SSLVPN RDS webApp to launch mstsc.exe no longer works after upgrading to 6.4, due to the Java plug-in going away with modern browsers, and other security enhancements. Solution: Create a set of webApps that open a TCP proxy port, and ...

      • Terminal Server sizing

        Are there recommendations for Terminal Server sizing? Terminal server sizing is one of those loaded questions and typically gets the answer of "it depends"  There are many factors in sizing a Microsoft terminal server. A quick Google search and you ...

      • Terminal Server 2000 information

        Windows 2000 terminal server settings From Microsoft site : http://72.14.203.104/search?q=cache:OPeT_a8tzEEJ:www.microsoft.com/technet/prodtechnol/win2kts/maintain/optimize/secw2kts.mspx+terminal+server+active+session+limit&hl=en&gl=us&ct=clnk&cd=1 ...