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 :)
remotewebaccess.com domains are not responding!
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!
Windows for business | Windows Server | Devices and deployment | Set up, install, or upgrade
Windows for business | Windows Server | User experience | Other
10 answers
Sort by: Oldest
-
SteveDr 1 Reputation point2020-07-25T19:13:00.633+00:00 -
Jesse Flintoff 236 Reputation points
2020-07-25T22:52:32.92+00:00 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".

-
Eddie Barnes 11 Reputation points
2020-07-27T08:59:46.303+00:00 Could this be the first steps in removing Remote Webaccess, it was left out of 2019 and this not was on a twitter chain?
-
Jesse Flintoff 236 Reputation points
2020-07-29T18:42:56.377+00:00 Works for me too.
-
Hans-Jörg Paul 111 Reputation points
2021-03-23T19:07:51.53+00:00 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:-(