Quantcast
Channel: Remote Desktop Services (Terminal Services) forum
Viewing all articles
Browse latest Browse all 1106

RDS 2016 - UWP, iOS, Android and Mac OS X Microsoft Remote Desktop Manager cannot connect to URL

$
0
0

About two weeks ago, the UWP, iOS, Mac OS and Android versions of Microsoft Remote Desktop Manager all stopped working for our RDS environment externally; previously, users were able to use this application externally and internally without fault.  If the users access our RDWeb/Pages/en-US/default.aspx and use classic MSTSC to open RemoteApps then this works externally.

When plumbing in the correct feed details to the apps we get (iOS, Mac OS) 'no workspace is associated with this URL site'.

We are using Windows Server Datacenter 2016 across the board with 2 servers acting as Gateways, Licensing, Broker and Web Access with a further 6 acting as session hosts.  All have been updated including the most recent crypto hotfix (approximately when the whole thing stopped working).

The route external users take would be:

External DNS entry - ADFSWAP - Gateway - Broker - Session Host

The following error can be found in the logs on our gateway servers:

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System><Provider Name="ASP.NET 4.0.30319.0" /> <EventID Qualifiers="32768">1309</EventID> <Level>3</Level> <Task>3</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2020-01-28T09:09:11.513985500Z" /> <EventRecordID>135104</EventRecordID> <Channel>Application</Channel> <Computer>##gateway computer##</Computer> <Security /> </System>
- <EventData><Data>3005</Data> <Data>An unhandled exception has occurred.</Data> <Data>28/01/2020 09:09:11</Data> <Data>28/01/2020 09:09:11</Data> <Data>b06bd32f8e5749749acc0c7da21c3816</Data> <Data>78</Data> <Data>13</Data> <Data>0</Data> <Data>/LM/W3SVC/1/ROOT-1-132246739255801381</Data> <Data>Full</Data> <Data>/</Data> <Data>C:\inetpub\wwwroot\</Data> <Data>##gateway computer##</Data> <Data /> <Data>7564</Data> <Data>w3wp.exe</Data> <Data>IIS APPPOOL\DefaultAppPool</Data> <Data>HttpException</Data> <Data>A potentially dangerous Request.Path value was detected from the client (:). at System.Web.HttpRequest.ValidateInputIfRequiredByConfig() at System.Web.HttpApplication.PipelineStepManager.ValidateHelper(HttpContext context)</Data> <Data>https://fqdn:443/https:fqdn/api/feeddiscovery/webfeeddiscovery.aspx</Data> <Data>/https:/fqdn/api/feeddiscovery/webfeeddiscovery.aspx</Data> <Data>##Internal IP##</Data> <Data /> <Data>False</Data> <Data /> <Data>IIS APPPOOL\DefaultAppPool</Data> <Data>26</Data> <Data>IIS APPPOOL\DefaultAppPool</Data> <Data>False</Data> <Data>at System.Web.HttpRequest.ValidateInputIfRequiredByConfig() at System.Web.HttpApplication.PipelineStepManager.ValidateHelper(HttpContext context)</Data> </EventData></Event>

Anyone got any ideas?  The above has had some data annonymised for security.



Viewing all articles
Browse latest Browse all 1106

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>