I tested the remote web access to my Windows Server 2016 Essentials on Thursday 18 March. It was fine but has subsequently failed. Attempts to repair the remote web access fail with the wizard reporting that the remotewebaccess.com domain is unreachable. There doesn't seem to be anywhere one can look to see if there is a known issue.
Hello @TDell987-6351
Maybe the solution from this thread works for you: https://docs.microsoft.com/en-us/answers/questions/319165/remotewebaccesscom-down-again.html
Many have report success after perform this solution : https://sbsland.me/category/computers-and-internet/troubleshooting/
Best Regards
Karlie
If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Thank you. I am going to try the sbsland.me solution tomorrow when I can next get to the site. The question for Microsoft is why would 'many' have to apply such a solution on a product that is still in mainstream support?
@KarlieWeng-MSFT - Thank you. The sbsland.me solution worked as far as I could test without messing with people's work. We will have to see what happens when the ISP next rotates the dynamic IP.
However, having to add registry entries to fix changes by Microsoft to Microsoft's supplied DDNS set up on a mainstream supported product seems unacceptable. Would you or someone from Microsoft like to comment on its commitment to Windows Server 2016 support?
Hi, I understand your feeling, Microsoft still needs improvements. and we are waiting for the official explanation from dedicated teams as well.
6 people are following this question.
