It appears that the nameservers for remotewebaccess.com have changed in the past 24 hours which has broken VPN/AnyWhere access for any Essentials servers utilising xxx.remotewebaccess.com domains. This needs to be fixed ASAP!
It appears that the nameservers for remotewebaccess.com have changed in the past 24 hours which has broken VPN/AnyWhere access for any Essentials servers utilising xxx.remotewebaccess.com domains. This needs to be fixed ASAP!
Unfortunately it looks like Microsoft may have lost control of the remotewebaccess.com domain. The registrar and nameservers have changed.
Is there any news about this problem? We are with the same problem...
I have tweeted this issue to Microsoft twice. No response. I can't find a contact anywhere. This is ridiculous...
If Microsoft lost control of the domain, would that be why I can’t sign in to renew a revoked certificate?
My server’s certificate got revoked, google chrome warns that a hacker may be trying to steal info (odd error), and I can’t use the wizard to sign in to renew. It says try again in a few minutes.
Same in UK. Apparently nameservers have been changed for the remotewebaccess.com domains which has caused havoc worldwide and is being very slow to resolve
Not sure why this would affect the certificates as it's just the DNS entry for the domain gone missing. As mentioned above, editing the hosts file on each external PC is a workaround for those that remember what the hosts file is.
I'm not dealing with end users that have that skill set. The actual remotewebaccess.com resolves just fine. It's the subdomains that won't.
And the reason the subdomains aren't resolving are that they are hosted on Microsoft's Azure nameservers which are no longer the nameservers for remotewebaccess.com.
Yeah unfortunately that's the situation most of us are in. Have spent a fair bit of time remotely accessing client PCs and updating host files for them quickly to get them back up and working. Unfortunately it's been quite a significant period of time now and Microsoft still hasn't replied despite multiple threads, tweets, etc
Our certificate got revoked at about the same time all of the remote webaccess sites went down.
I can’t renew the certificate using the wizard, it tells me try again in a few minutes every time.
Our certificate also got revoked for at least one client's webaccess site.
The US phone number for the new registrar, Com Luade, is invalid.
So should we speculate that someone has indeed hacked the domain control for remotewebaccess.com and changed the nameservers? I couldn't imagine Microsoft wanting to cause such an outage at anytime let alone with the current pandemic.
Not related. The nameservers did not resolve to this UK host yesterday. Someone renewed the domain, changed nameservers and broke DNS about 4pm Eastern time yesterday 7/23/2020.
Question, I'm having a two fold issue here. I'm having the same DNS issues as everyone else, but just prior to this when it all started around 5:30pm EDT yesterday, one of our remote access servers got their certificate revoked.
If this happens, normally I'd just go into the wizard again and repair or do the setup again.. but when I sign in to the Microsoft account it says:
An error occurred while setting up your domain name. The domain name was not setup for your server. Wait a few minutes and run the wizard again.
I think this would be because the wizard can't contact remotewebaccess.com to setup the domain and get a new certificate. Would that be a correct assumption?
You are correct in that the wizard will fail if it can't resolve the domain name.
Word is it has just been fixed, now we get to wait on DNS propagation
Google DNS is reporting the correct nameservers now - but not the rest of the big dns providers
Still unable to resolve the *.remotewebaccess.com webpage on my server. Also still receiving the "NET::ERR_CERT_REVOKED" when attempting to reach the page through URL or IP address. Is there a resolution to this issue yet? I don't know of any users who this is currently working for....PLEASE HELP!!!
Is it possible that the registrar was changed for remotewebaccess.com, but Microsoft did not setup the DNS records straight away - meaning that the default dns for the host was used - until they corrected it?
Perhaps they'll explain what happened, and why we were not given notice of it so that we could have alerted clients of the impending downtime :)
DNS resolution issue fixed. However if you try to run the anywhere access wizard to adjust your settings. Or run it from scratch. The wizard will fail with error "an error occurred while setting up your domain name".


I am still seeing the "An error occurred while setting up your domain name". My existing one works but it doesn't seem like I can't modify this in the future. Looking at the Dashboard.log in C:\ProgramData\Microsoft\Windows Server\Logs I see the following:
GitmeInfrastructure: GetReferralServiceBaseUri: read referral Service Uri from registry:
GitmeInfrastructure: Failed to download global valid TLDs from the online service: System.Net.WebException: The remote name could not be resolved: 'www.microsoft-sbs-domains.com'
So it looks like the issue is the no longer existant URL www.microsoft-sbs-domains.com . This worked back in March of this year (2020) so I wonder if this went down too back in July but was never corrected.
Could this be the first steps in removing Remote Webaccess, it was left out of 2019 and this not was on a twitter chain?

yes the domain-activate-process at the server works again now.
But all my clients has a problem. VPN connected, but the server-connector gets no connection:-(
12 people are following this question.