NetScaler Gateway 11 – RDP Proxy

Last Modified: Jun 14, 2016 @ 7:51 pm

RDP Proxy

NetScaler 10.5.e and NetScaler 11 support RDP Proxy through NetScaler Gateway. No VPN required. There are two ways of launching RDP sessions through NetScaler Gateway RDP Proxy:

  • Bookmarks on the Clientless Access portal page.
  • After logging in, change the URL in the browser to /rdpproxy/MyRDPServer. MyRDPServer can be IP or DNS.

You can have one Gateway vServer that authenticates the user and a different Gateway vServer to proxy the RDP connection. The Gateways use Secure Ticket Authority (STA) for mutual authentication. See Stateless RDP Proxy at for more information.  💡


Here are some requirements for RDP Proxy:

  • NetScaler Enterprise Edition or Platinum Edition.
  • NetScaler Gateway Universal Licenses for each user.
  • TCP 443 and TCP 3389 opened to the NetScaler Gateway Virtual Server.
  • TCP 3389 opened from the NetScaler SNIP to the RDP Servers.

Do the following to configure RDP Proxy:

  1. Expand NetScaler Gateway, expand Policies, right-click RDP and click Enable Feature.
  2. Click RDP on the left. On the right, switch to the Client Profiles tab and click Add.
  3. Give the Client Profile a name and configure it as desired. Scroll down.
  4. In the RDP Host field, enter the FQDN that resolves to the RDP Proxy listener, which is typically the same FQDN as NetScaler Gateway.
  5. Near the bottom is a Pre Shared Key. Enter a password and click OK. You’ll need this later.
  6. On the right, switch to the Server Profiles tab and click Add.
  7. Give the Server Profile a name.
  8. Enter the IP of the Gateway Virtual Server you’re going to bind this to.
  9. Enter the same Pre Shared Key you configured for the RDP Client Profile. Click Create.
  10. If you want to  put RDP bookmarks on the Clientless Access portal page, on the left, expand NetScaler Gateway, expand Resources, and click Bookmarks.
  11. Alternatively, Simon Gottschlag Publish RDP Proxy Link via StoreFront shows how NetScaler Rewrite can insert an RDP Proxy link into a StoreFront web page.  💡
  12. On the right, click Add.
  13. Give the Bookmark a name.
  14. For the URL, enter rdp://MyRDPServer using IP or DNS.
  15. Check the box next to Use NetScaler Gateway As a Reverse Proxy and click Create.
  16. Create more bookmarks as desired.
  17. Create or edit a session profile/policy.
  18. On the Security tab, set Default Authorization Action to ALLOW. Or you can use Authorization policies to control access.
  19. On the Remote Desktop tab, select the RDP Client Profile you created earlier.
  20. If you want to use Bookmarks, on the Client Experience tab, set Clientless Access to On.
  21. On the Published Applications tab, make sure ICA Proxy is OFF.
  22. Edit or Create your Gateway Virtual Server.
  23. In the Basic Settings section, click More.
  24. Use the RDP Server Profile drop-down to select the RDP Server Profile you created earlier.
  25. Scroll down. Make sure ICA Only is not checked.
  26. Bind a certificate.
  27. Bind authentication policies.
  28. Bind the session policy/profile that has the RDP Client Profile configured.
  29. You can bind Bookmarks to either the NetScaler Gateway Virtual Server or to a AAA group. To bind to the NetScaler Gateway Virtual Server, on the right, in the Advanced Settings section, click Published Applications.
  30. On the left, in the Published Applications section, click where it says No Url.
  31. Bind your Bookmarks.
  32. Since this NetScaler Gateway Virtual Server has ICA Only unchecked, make sure your NetScaler Gateway Universal licenses are configured correctly. On the left, expand NetScaler Gateway and click Global Settings.
  33. On the right, click Change authentication AAA settings.
  34. Change the Maximum Number of Users to your licensed limit.
  35. If you want to connect to RDP servers using DNS, make sure DNS servers are configured on the appliance (Traffic Management > DNS > Name Servers).
  36. If you want to use the short names instead of FQDNs, add a DNS Suffix (Traffic Management > DNS > DNS Suffix).
  37. Connect to your Gateway and login.
  38. If you configured Bookmarks, simply click the Bookmark.
  39. Or you can change the address bar to /rdpproxy/MyRDPServer. You can enter IP address (e.g. rdpproxy/ or DNS names (/rdpproxy/myserver).
  40. Then open the downloaded .rdp file.
  41. You can view the currently connected users by going to NetScaler Gateway > Policies > RDP and on the right is the Connections tab.

Email this to someonePrint this pageTweet about this on TwitterShare on LinkedInShare on FacebookPin on PinterestShare on RedditShare on StumbleUpon

63 thoughts on “NetScaler Gateway 11 – RDP Proxy”

  1. Very nice article! I’m now also trying to replace the RD webinterface with the netscaler, i tried to connect to the gateway and to the RDS broker but can’t seem to get it working. Is the broker still not supported in RDPproxy?

  2. Thanks for an excellent article Carl, smooth and easy setup.

    However, I’m having trouble when connecting to 2012 R2 servers, it gives the following error “Your computer can’t connect to the remote computer because the connection broker couldn’t validate the settings specified in your RDP file”. Any tips on how to solve this?

  3. Thanks for the article Carl. Is it possible not to pass the login credentials to the RDP session and ask you for the username and password?

  4. Thanks for your great work. After the update to 11.1 is the rdpProxy feature, although we have an Enterprise license, no longer licensed. Can you confirm it?

      1. Thanks for your quick reply. We already have an enterprise license installed. Any idea? I’ll try a clean installation.

    1. Removed thanks. I thought I saw it as an option in one of the Partner documents but I couldn’t find any SKU in the price list.

  5. My issue is I configured unified gateway. Therefore, I have a content switching server and 1 NetScaler gateway Virtual server. Now, I configured RDP Proxy using a separate virtual server, when I use the domain name ( as the RDP host it works. However, when I use the unified gateway domain name ( as the RDP Host I cannot get a connection. Why is this happening?

  6. Hi Carl thanks for the blog.

    I want to replace UAG with Net Scaler which is a gateway for backend RDS2012 setup. I tried to use RDP proxy feature of Netscaler but found that it is only used to publish RDP of the standalone server and doesn’t integrate well with the RDS 2012 farm like RDP Broker, RDS host Servers, RDP APPs, etc which we can easily configure onUAG 2010.

    Also We have configured multi factor authentication (Radius and AD) on UAG and users cannot download the RDP app in RDP format which forces them to login to UAG portal first and then access the RDP apps.

    Can I achieve above via Netscaler.

  7. A quick one carl; and great article btw. You mention binding a bookmark to an AAA group? Where do you do this? I can only seem to bind policies through authorisation for aaa groups. Im looking to have individual rdp proxy bookmarks per user/group in AD.

    1. Go to NetScaler Gateway > User Administration > AAA Groups. Add a group that matches the AD group name. Then you can bind bookmarks to the group.

  8. Hi Carl,

    is there a way to use RDP – Proxy with VPX Express License ?

    “There’s also a CCU add-on for Standard Edition”
    Did you get any information about restrictions and pricing ?


    1. Express = Standard so I don’t think so. I just found a pricing guide saying that RDP Proxy needs Enterprise Edition and Gateway Universal licenses.

      The FAQ mentions the add-on license but I haven’t found any details on that.

        1. If my instructions didn’t help you then you can post your question to or call Citrix Support. Almost every NetScaler appliance comes with support. If you found something wrong with my instructions let me know and I’ll fix it.

    1. Hi Andrew,

      I have a little Demo (ESXi) with AAA-Groups to demonstrate different access variants over Universal Gateway with CSW-Rules in front. One scenario is access to published apps and desktops with ica pxoxy on. Another scenario is clientless access with Bookmarks to Websites, StoreFront, ShareFile and RDP-Proxy over the same vserver. It works fine.


      thanks for the great blog, and sorry for my bad englisch.


  9. Hi Calr,

    thank for the article, if can please help me on this, i launch the RDP session to the desired workstation with full VPN connetion , but with clienteles connection it dosen’t work, kindly help me on this.

  10. Hi Carl, Nice article. However i’m unable to get it working. No matter what I do I get prompted to download or use the Netscaler Gateway Plugin (Although clientless is configured, as far as I can see). If I continue and use the AGEE, and click the bookmark I get http 403 errors. I wondered if any config (Apart from install the session host role) is required on the RDP server (Win 2012r2).


  11. Hey Carl, first of all thanks for the blog 🙂

    I’ve got this setup as suggested and when connecting I get the RDP file as expected with the STA stuff in there, it opens and begins to connect. If I packet capture I can see packets going from the subnet IP to the correct RDS box, the RDS client goes through its process..securing, configuring, estimating and then fails with can’t connect.

    Any ideas? If I connect via full tunnel I can RDP fine so the endpoint is working. Been at this for days now :S

    1. Gateway won’t allow RDP unless the user has been authenticated.

      I added a note about Stateless RDP. Basically it allows you to authenticate to one Gateway but use a different Gateway for the RDP connection. The Gateways use STA to authenticate each other.

      1. Ok, so then it would be SSL from the client instead of 3389? Current deployment is UGW and RDPProxy on top, and then it only works if I open 3389 externally to the VIP (user get’s authenticated all the way even SSO)

  12. Hi,

    tried to establish a RDP-proxy-connection. Without success.

    I’m able to get the rdp-file. But when the MSTSC-client try to connect to the RDP-server I get the error-message that it can’t connect to the remote computer.

    This is my configuration:

    Win-Client -> Internet -> NAT-IP -> Firewall -> DMZ-NetScaler with RDP-proxy-config -> Firewall -> internal NetScaler with LB-RDP-Vserver -> RDP-server.

    Because the SSL-VPN-technique of the NetScaler is not common to me, I have a problem to understand the functionality to access the RDP-server over the internet, because I try to access an internal IP-adress over the internet (entry in downloaded rdp-file).
    How can I check whether a VPN-connection is established when I try to access the RDP-server over SSL-VPN-RDP-proxy?

    Thank you in advance!

    1. RDP Proxy does not require a full VPN tunnel. If you have a VPN tunnel then you don’t need RDP Proxy since you can connect to the RDP server directly.

      1. Ok. This is comprehensible. But I’ve still a problem in understanding how I can connect via the internet with the MSTSC-client to an internal-IP-address.

        1. Without VPN, you use NetScaler Gateway RDP Proxy to generate the .RDP file for you. Then you simply launch the .RDP file. The connection should be proxied through NetScaler Gateway RDP Proxy.

        2. I just realized that my instructions were missing the RDP Host field in the RDP Client Profile. The RDP Host should be a FQDN that resolves to the RDP Proxy Listener.

          1. With the entry of the missing RDP-host in the RDP client profile I am able to reach my RDP-server.
            But I am not able to accomplish a RDP-session. At the configuring-phase at the MSTSC-side I got a error message “An internal error has occurred.”. I’ve checked the firewall-logs whether something is blocked between the related stations. Nothing blocked.
            At the RDP-host I see a successful login and an immediate logout of the user in the Windows-Security-log. Any idea?

          2. Hi,

            new awareness. I tried with Windows 2008R1-host as RDP-host all the time (because this is our productive RDS-environment). As I tried Windows 7 and Windows 2008R2 the connection worked. So what is the difference between 2008R1 and 2008R2/Win7 in RDP via NetScaler RDP-proxy?

          3. I assume you mean with “NLA” “Network Location Awareness” (the windows-integrated firewall-setting).
            I’ve tested it with different 2008R1- und 2008R2-systems on which the same domain-GPOs operate and we don’t use local security-settings.
            Can you give me a tip which NLA-setting could be a reason for my problem?

          4. Just wondering if there’s any difference. I don’t have any 2008 R1 servers to test against. I wonder if it’s because 2008 R1 doesn’t support RDP 8.0.

          5. Hi,

            now it’s getting confusing. Since yesterday I’m neither able to connect to 2008R1 nor to 2008R2 (which worked last week!). The error I receive from MSTSC-client is “An authentication error has occured (Code: 0x80004005) Remote computer: [FQDN-name of NS-gateway]”.
            The only changes are actual MS-patches for the server.

          6. I saw a similar problem when using REST calls to create my 11.0 build 63 Gateway vServer. To fix it, I had to open the Gateway vServer, go to Other Settings (or Profiles), click the pencil icon, don’t change anything and click OK. This caused the RDP Proxy to start working. I think it’s a bug.

          7. Unbelievable… after opening the Gateway vserver, opened “Other settings” and closed it, 2008R2-servers work again! Thank you very much!
            Now I have the old situation. 2008R2 works, 2008R1 not. Continuing debuging…

          8. Update: I tried connecting to Windows 2003 Server via RDP over RDP-Proxy. Same problem like 2008R1. It looks like that the NetScaler RDP Proxy has a problem with RDP <= 2008R1.
            I have already played around with NTLM settings on 2008R1- and MSTSC-side. Without success.
            Any idea? I am thankful for every tip or new idea!

          9. It might require RDP 8. I don’t have any older OSs to try with. Try asking at

          10. I’m just somewhat confused here, will this be the same FQDN as the gateway vServer or the FQDN of the actual RDP server on the inside? Thanks for a great write up of an confusing issue 🙂

          11. You mean the RDP Proxy Host field? That should be the Gateway FQDN unless you’ve split them out.

  13. Hi, Is there a API Call to netscaler I can make to get the RDP File for a given ICA File?
    What I want to achieve is that once i have the list of app published, I want to have the ability to download the .rdp file for a particular ICA file. Is it possible?

    1. You want to use RDP instead of ICA/HDX? Why?

      For published apps, they are published using Citrix, not RemoteApp, so connecting using RDP probably won’t work.

      1. Without going into much detail on what my solution is, I am working on a solution with combines RDP proxying within Citrix infrastructure. Where most of the things are done programmatically for which I need to know as to how can I fetch the address of a host on demand basis so that I can get the RDP file for the host.

        I have my netscaler setup to proxy RDP traffic and I do get the .RDP file when I go to the browser and do something like https://mynetscalar/rdpproxy/

        But the issue I have is I do not always know the IP address ( of the host nor its domainName?

        I tried calling the /Resource/LaunchICA API which gives me back the .ICA file for a published remote app and when you take a look at the contents of this .ICA file in the response, you see different info depending on where this request was made to:

        api call (/resources/launchICA) to storefront, gives back a response


        among other data but address is what interests me.

        The same API call against the netscaler gives me back a response with address containing some random string


        Q is, Is there any configuration change I can make on the netscaler to make sure the ipaddress of the host is sent as part of the ICA file just like the storefront?

        Once I get the Address, Then I can make this call to fetch the .RDP file
        https://mynetscalar/rdpproxy/HOST IP ADDRESS

        Much appreciate your quick response!


        1. You’d need to configure StoreFront to not rewrite the ICA file for NetScaler Gateway. In other words, remove (or unbind) the Gateway configs from the StoreFront console. But I’m not sure how to do that but also allow authentication at the Gateway and SSON to StoreFront. You might be able to do clientless access to StoreFront with a Traffic Policy that does forms-based auth to StoreFront. Or you can configure StoreFront to accept Basic Auth but I’ve never tried it.

  14. Hi, can I ask a question re: this article? I have a strange situation where when users connect to their desktop, they get an error “This computer can’t connect to the remote computer. Try connecting again. If the problem continues, contact the owner of the remote computer or your network administrator”.

    I found another person thru Citrix forums having the same problem as me but no replies. The issue is that the remote users are connecting to their target machines, but the full name is being passed in, instead of the username. Thus, the Event Viewer on the target machine shows “Unknown user name or bad password”. So instead of domain\cstalhood, “Carl Stalhood” is sent in as the username.

    I reconfigured the client profile to not insert the username into the .rdp file in the hopes that it would force the users to have to enter the credentials but that doesn’t work either. Seems like there’s some SSO functionality built into it, regardless.

    I tried this on Netscaler 11 and 10.5 and the results are identical. Have you come across this before?

      1. Whoa! Thank you! I didn’t think to look there. It was set to the default “cn”. I set it to “new” and then input sAMAccountName. Works like a charm now! Thank you!

  15. Nice Articles Carls…Enjoyed…I have done two months before when product got release…It was clients requirement for RDP session to be managed through Gateway…:)

Leave a Reply