Windows home server remote desktop gateway server is temporarily unavailable

->>>> Click Here to Download <<<<<<<-

Also be sure your RD gateway got the January security patch, as there is a critical TD Gateway remote code execution bug that can be remotely exploited by an unauthenticated attacker. To start, try manually connecting to your TD s wnssion host from outside and manually specify your RD Gateway server. If this doesn't work then you have a problem with RD gateway. If it does work, then your problem could be with RD Web, etc. I meant to manually connect to RD session host via RD gateway.

Autocorrect can really suck on my device. I do know that it has to be done correctly, or the two services, which use the same listening port, will conflict. Thanks so much for your assistance. I don't think i would have ever found this in such detail although i'm still having a little bit of trouble.

I have another GPO related to mapped drives just above this policy with the same setup of users so I think it's assigned correctly. I am using the. I'm posting a pic of the policy to see if you see anything i might have done incorrectly. I believe it is an SPN. Makes the account or the terminal server trusted for delegation and allows the credentials to pass. The remote users workstations are not part of the domain as they are remote.

The RD Server and user accounts are part of the domain. Is this my problem? Add the Certificates created above to the. Ryan's path wasn't correct but after correcting the path in the GPO and pasting the thumbprint in the policy it worked.

Only one authentication for the user at the splash page. To continue this discussion, please ask a new question. Search related threads. Remove From My Forums.

Answered by:. Archived Forums. Remote Desktop Services Terminal Services. Sign in to vote. My setup: Windows server Standard. So, I'm here, seeking help so I can find the root case and get this fixed up. Any other information you need, please do ask me. I'm very quick to reply back. Thank you in advance for your help. Thursday, November 20, AM.

Hi Steve, Thanks for your comment. How is everything going? Could you please tell us the present situation? Wednesday, November 26, AM. Hi Dharmesh, Thanks for following up. Thanks Steve. From you initial description it seems you have everything working except connection through RD Gateway. This happens because when you try to connect to the farm, the Gateway tries to connect to the DNS and resolve the farm name. But as there is no resource like that, you get the error. So, in order to access the farm as well, you need to add the name of the farm in the RD RAP policies, so that it checks that as a network resource and thus, does not need to resolve the name with the DNS.

Kindly refer following article for more information. Hope it helps! Sunday, November 23, AM. The other thing is to make sure the ports are properly being forwarded to your server and the best way to do this is to reserve and IP number for the server with your router then forward the following ports to that IP 80, , and there is one more I believe its Ports and are for RDP connections.

If the other client works but the one you attempted to set the VPN up on does not then you have to correct the client.

So you have to address the issue on both the client and server side. Hi, thanks for your fast response! Idiot over here didn't set up a backup before fiddling as my hard drive that I was planning to use for the backup is currently in a PC who's primary hard drive is at the menders, so I can't rescue the data off it easily, it is the only tower PC we have, minus the server.

The location I am attempting to connect from uses a TS Gateway to connect to their infrastructure providers site, and so do not block those ports.

My router has a reputation for poor port forwarding and so this may be a culprit. The port is reported as closed on canyouseeme. Also, the fact I'm getting this error suggests the server is being reached, if I enter an incorrect password the client tells me it is incorrect. Posted: Tue Feb 04, am.

If you were able to make the connections before then the issue may not be with the router but if not then quit possibly the router could be the issue.

You need to look back and figure out what you could do before that you can not do now to determine where the problem is be it with the router or with a configuration in the server or client. I do know that routers can be a big pain and are often overlooked as the cause of a problem.

Posted: Tue Feb 04, pm. I believe I could connect, I can recall as previously mentioned getting to the certificate acceptance error, and just hitting No as I din't want to connect at the time. I have doubts as to the status of port , but I believe I read somewhere it is only opened on demand, and if I could get through before then I believe it isn't the port to blame.

I am so annoyed at myself for fiddling, the VPN side of things wasn't too damaging, but this Remote Desktop Services role has really caused some problems. I believe if you could do it before then the router would not be the issue. Can you make an RDP connection within your network where the server is actually located? Thing about Remote Desktop is WHS uses it to also make a Dashboard Connection so if you can fully use it within your network it would be a good sign.

Then the next question is can you make a connection to the server itself from outside your network to verify RWA or Remote Web Access is functional and that you can get on the servers Dashboard as this will be a good sign.