RemoteApp and RD Gateway

[harriuk]

Hi Nathan. This looks like exactly what is happening. At last Microsoft have put in a proper solution for it in RDS 2012 R2.

 

This didn't exist in RDS 2008 so we had to come up with other solution.

 

Have you run it and did it fix your issue?

[nathan]

Havent had a chance to run it yet, things are too busy here everyone wants everything doing now, typical school environment. Most think we sit around doing nothing until someone wants something.

[nathan]

just done it now, ran it and now they both say the remote.domain.com but it won't connect at all as it's saying remote.domain.com can't be found. Will have another look.

 

EDIT: I am getting the following error now though.

 

The user "DISCOVERY\username", on client computer "000.000.000.000", did not meet resource authorization policy requirements and was therefore not authorized to resource "remote.domain.org.uk". The following error occurred: "23002".

Edited February 12, 2014 by nathan

[harriuk]

Is the remote.domain.org.uk in your previous post a typo!

[harriuk]

Now you need to check what is in your RAP (Remote authorization policy) in the gateway setup.

 

Harriuk

[nathan]

Its not a typo, i just edited it out to not post the correct domain. I've recreated the RD RAP policy. Under User Groups, i have the ad group that the user is a part of. Under Network Reources i have created a new group with the ip, netbios and fqdn entered. under allowed ports i have 3389 only allowed.

[nathan]

Soooo, i've spent far too many hours on this , it's getting depressing now. Just rebooted the server, logged into rdweb, clicked on a remote app and it freezes ie. Look at the event log on the server and now i get the following error;

The Remote Desktop Connection Broker server could not enumerate the targets for the provider named NULL from the database.

 

Pooled virtual desktop collection name: NULL

Error: Logon to the database failed.

 

I havent changed anything fro 5 minutes ago!!! ahhhhhhh

[harriuk]

Ok try this solution.

 

http://www.urtech.ca/2013/02/solved-server-2012-remote-desktop-connection-broker-server-could-not-enumerate-the-targets-for-the-provider-named-null-from-the-database/

[nathan]

Ok try this solution.

 

SOLVED: Server 2012 – Remote Desktop Connection Broker server could not enumerate the targets for the provider named NULL from the database - Up & Running Technologies Calgary

 

i found the same page, done it and still nothing.

 

I'm just going to give up for tonight and will do a reinstall tomorrow. I should be able to reuse my certificate shouldn't i?

 

Thanks for you help by the way

[harriuk]

Yes you can reuse the certificate. And I dont blame you for calling it quits for tonight.

[fiza]

@nathan - did you get anywhere sorting the remote certificate mismatch with your local domain?

I have purchased my certificate and I get a warning that the hostname in the server certificate does not match the computer you are connecting to. Your connection might not be secure do you want to continue

[aleach2]

just done it now, ran it and now they both say the remote.domain.com but it won't connect at all as it's saying remote.domain.com can't be found. Will have another look.

 

EDIT: I am getting the following error now though.

 

I had the same issue with non domain joined computers. Open the RD Gateway Manager, navigate to your Recourse Authorization Policy and open the policy. On the Network recourses tab make sure the Allow users to connect to any network resource. This fixed the issue for us.

 

[nathan]

If only you could of answered 3 months ago!!

 

Just kidding, at least an answer is there for Google folk to see.

[omicron-czech]

Google folks have been pleased!

 

It work like a charm. Thanks a lot.