New RDS not connecting
Hello.
I have a new 2019 hyper-v setup taking over from server 2012/2008 legacy servers. My new setup -
vm1- DC, DNS FILE
vm2 - Apps, DC, DNS, Print server
vm3 - RD Broker, RD Gateway, RD licencing, RD Web access.
vm4 - RD Session host 1,
VM5 - RD Session host 2.
I have configured many RD environments before with no issues and have matched everything like for like. The issue is have is that when I try to connect to the RD Environment via the web page i receive an error -
"Remote desktop can't find the computer vm3.domain.local. This might mean that vm3.domain.local does not belong to the specified network. Verify the computer name and domain that you are trying to connect to."
I receive the above message internal or external to the network.
I have looked through many threads on the net and it seems to be related to DNS. I have tried several fixes with no success.
On VM3 event viewer i receive event ID WARNING 304. "The account on client computer met connection authorization policy and resource authorization policy requirements, but could not connect to resource vm3.domain.local. Connection protocol used: "HTTP". The following error occurred: "23005". "
If anyone know how to fix this or point me in the right direction, I would be most thankful.
I have a new 2019 hyper-v setup taking over from server 2012/2008 legacy servers. My new setup -
vm1- DC, DNS FILE
vm2 - Apps, DC, DNS, Print server
vm3 - RD Broker, RD Gateway, RD licencing, RD Web access.
vm4 - RD Session host 1,
VM5 - RD Session host 2.
I have configured many RD environments before with no issues and have matched everything like for like. The issue is have is that when I try to connect to the RD Environment via the web page i receive an error -
"Remote desktop can't find the computer vm3.domain.local. This might mean that vm3.domain.local does not belong to the specified network. Verify the computer name and domain that you are trying to connect to."
I receive the above message internal or external to the network.
I have looked through many threads on the net and it seems to be related to DNS. I have tried several fixes with no success.
On VM3 event viewer i receive event ID WARNING 304. "The account on client computer met connection authorization policy and resource authorization policy requirements, but could not connect to resource vm3.domain.local. Connection protocol used: "HTTP". The following error occurred: "23005". "
If anyone know how to fix this or point me in the right direction, I would be most thankful.
ASKER
Hi, So the ping is internally works fine. (External DNS is setup and NATs to vm3)
powershell test - 443 - Past
powershell test on 3389 - Failed
powershell test - 443 - Past
powershell test on 3389 - Failed
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thank you for your help. I think allowing remote desktop to vm3 fixed the problem.
1) Pinging VM3 by name resolves to the correct IP from your testing machines (internally) ?
2) using powershell - what you get from
- tnc -computername vm3 -port 443
- tnc -computername vm3 -port 3389