Forum Discussion

McGentrix's avatar
McGentrix
Copper Contributor
Apr 03, 2020
Solved

2019 RDWebClient, RDS Published Apps - missing something, just not sure where

University setting, VMWare & Microsoft

Internal domain local.name.edu  external domain name.edu 

Setup 2019 server vapps-01.local.name.edu  outside name vapps.name.edu  going through Barracuda load balancer as a proxy. using a wildcard cert *.name.edu (vapps-01.local.name.edu  as SAN) and applied down the line. Thumbprints checked and verified.

from browser, can open https://vapps.name.edu  that is redirected to https://vapps.name.edu/rdweb/webclient  and connects to vapp-01.local.name.edu/rdweb/webclient  and comes up with login credentials. Can login using local\name and password.

Brings up console with applications and when application is selected, "opening remote port", "Configuring remote port" and dies there. "Oops, we couldn't connect to "app" The connection to the remote PC was lost, This might be because of a network connection problem. If this keeps happening, ask your admin or tech support for help."
Well, **bleep**. That's me.
As far as I can tell, the app is opening an RDP connection on port 3392, which is open in firewall and has SSL cert attached to it but the connection is failing.

I am hoping someone out there has had this happen to them and they know what check box I missed or link I need to change. 

Wireshark makes it appear as 3389 is dropping session with a RST, ACK Maybe that is issue. Could be DNS, Could be needing a gateway... Hopefully someone has experience with 2019 now?

9 Replies

  • McGentrix hi - for VMware deployments it might be best to loop in VMware - or use their support platforms. Thanks.

    • McGentrix's avatar
      McGentrix
      Copper Contributor

      For some reason, evasse marked this as the best answer? This is no answer so for it to be marked best answer is no good. What would VMWare have to do with this at all? It obviously either a certificate issue or a permission issue with Microsoft and there is no documentation or guidance to move on.

       

      While I appreciate Pieter's effort, pushing this off as a VMWare issue is really just passing the buck. I'm not looking for buck passing, but help or answers. Problem has not been resolved or answered.

      • evasse's avatar
        evasse
        Bronze Contributor

        McGentrix : Please contact as suggested VMWare to confirm this is not a bug within the management plane.

         

        Thank you!

Resources