This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(19.2, 55.00000000000001%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKB%3C/text%3E%3C/svg%3E)
Microsoft Anywhere Access broken on Server 2016 Essentials again? Getting the dreded an error has occured updating the dynamic dns information message
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(195.2, 68%, 28%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDZ%3C/text%3E%3C/svg%3E)
I have the same issue, if you ping the domain name they issued you xxx.remotewebaccess.com you should get your public facing IP address or more likely the prior public address your ISP provided to you before it was updated, that just means it hasn't updated in DDNS on the Microsoft side to match up. I get the prior so it's clear Microsoft DDNS is not updating the IP address that points to the server, I am guessing this is the same thing others are seeing. I'm not sure why Microsoft can't resolve this, yes the product may be near end of life but it isn't there yet and people still use it. It would be nice for it to work as it was intended, obviously from all the blogs about this its a pretty big issue that people want fixed until they have time to upgrade. I'm not even sure on a workaround since I'm not really a network guy, I just dabble a bit.
Thanks Dan. That is what I observer as well. Seems to be an issue every year or 2 for about 2 weeks until it gets resolved untill next time.
If you see it resolved, let me know. Last time that this happened it was about 5 months before they found a resolution. I wish it was only 2 weeks but people have been complaining about this since mid 2023.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(99.2, 12%, 19%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDH%3C/text%3E%3C/svg%3E)
My Server 2016 is experiencing the same issue... again... been this way about 3 weeks now.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(9.6, 50%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EG%3C/text%3E%3C/svg%3E)
i have the same issue here in europe Luxembourg , some SBS2016 are still working and some not
i asume if ISP changes ip it will broke remotewebaccess.com
hope Microsoft will find solution fast
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(32, 33%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ES%3C/text%3E%3C/svg%3E)
Same here, several essentials servers that i support have the same error
Did you manage to get it work? Still not updating dns record , will microsoft provide a solution?
Finaly its working ,
It's still not working for us here... It looks like the dynamic DNS update issues may have been corrected, but attempting to set up a new or replacement remotewebaccess.com Microsoft personalized domain name in Anywhere Access still fails with a (generic) timeout error (as I've reported over here). At least they're making some progress.
Okay, it looks like things are back up and working again. I'm now able to set up new remotewebaccess.com Microsoft personalized domain names again. :-)
I would absolutely minimize what you do, it's fragile and I wouldn't be surprised if it was broken again. I am not going to mess too much with it for fear that it will break again with an excuse of end of life product.
I completely agree... Folks should start moving off of the remotewebaccess.com Microsoft personalized domain names in order to avoid these types of (frequent and lengthy) interruptions and switch over to using their very own custom/vanity domain name instead.
I have a step-by-step writeup on how to do just that in Windows Server Essentials (using either a user-purchased SSL certificate or a free Let's Encrypt SSL certificate) posted on my website over here:
How To Manually Set Up A Custom / Vanity Domain Name In Windows Server Essentials
When you manually set up your own domain in Anywhere Access, you are in full control of it, and so you no longer need to worry about things going down on Microsoft's end (as you do when relying on a remotewebaccess.com Microsoft personalized domain name). ;-)