remotewebaccess.com Anywhere access broken on Server 2016 Again?

ChrisWY27 136

Last year a similar issue occurred and by manually applying the registry edits from these two threads most seemed to resolve their issues:

https://learn.microsoft.com/en-us/answers/questions/319165/remotewebaccesscom-down-again.html?childToView=836766#answer-836766

https://learn.microsoft.com/en-us/answers/questions/318584/are-the-problems-with-remotewebaccesscom-domain-an.html?page=2&pageSize=10&sort=oldest

The problem is as of yesterday (May 3 2022) I am now experiencing the issue again. Re-applying the registry tweaks does not solve the issue either unfortunately. More so, I am not able to un-register my domain through the wizard or change to a new one, I am seeing the same issue as this user on their fresh install: https://learn.microsoft.com/en-us/answers/questions/814489/cloud-services-integration-amp-anywhere-access-not.html?childToView=836816#answer-836816

Looking at my Dashboard.log in the ProgramData\Microsoft\Windows Server\Logs folder I see the below:

[5840] 220504.122339.7059: DomainConfigWizard: Next Page: progressPage
[6024] 220504.122340.0497: DomainManagerObjectModel: InvokeAsync: action resulted in exception: System.ServiceModel.FaultException1[Microsoft.WindowsServerSolutions.RemoteAccess.Domains.DomainManagerFault]: The creator of this fault did not specify a Reason. (Fault Detail is equal to DomainManagerFault:[Reason:CommunicationFailure, Message:CommitDomain failed, Detail:System.Web.Services.Protocols.SoapException: Live Dynamic DNS has encountered an internal error. This error has been logged. ---> Microsoft.Rest.Azure.CloudException: The access token is from the wrong issuer 'https://sts.windows.net/72f988bf-86f1-41af-91ab-2d7cd011db47/'. It must match the tenant 'https://sts.windows.net/33e01921-4d64-4f8c-a055-5bdaffd5e33d/' associated with this subscription. Please use the authority (URL) 'https://login.windows.net/33e01921-4d64-4f8c-a055-5bdaffd5e33d' to get the token. Note, if the subscription is transferred to another tenant there is no impact to the services, but information about new tenant could take time to propagate (up to an hour). If you just transferred your subscription and see this error message, please try back later. at Microsoft.WindowsServerSolutions.DDNS.AzureRmDnsServer.GetARecords(String domainName) in E:\WSE-ServicesAndTools\src\ServicesAndTools\DDNS\DDNS\AzureR...). [6024] 220504.122340.0497: DomainManagerObjectModel: InvokeAsync: handling exception by transferring to eventArgs [5840] 220504.122340.0653: DomainConfigWizard: Error occurred in Domain Manager Object Model operations: System.ServiceModel.FaultException1[Microsoft.WindowsServerSolutions.RemoteAccess.Domains.DomainManagerFault]: The creator of this fault did not specify a Reason. (Fault Detail is equal to DomainManagerFault:[Reason:CommunicationFailure, Message:CommitDomain failed, Detail:System.Web.Services.Protocols.SoapException: Live Dynamic DNS has encountered an internal error. This error has been logged. ---> Microsoft.Rest.Azure.CloudException: The access token is from the wrong issuer 'https://sts.windows.net/72f988bf-86f1-41af-91ab-2d7cd011db47/'. It must match the tenant 'https://sts.windows.net/33e01921-4d64-4f8c-a055-5bdaffd5e33d/' associated with this subscription. Please use the authority (URL) 'https://login.windows.net/33e01921-4d64-4f8c-a055-5bdaffd5e33d' to get the token. Note, if the subscription is transferred to another tenant there is no impact to the services, but information about new tenant could take time to propagate (up to an hour). If you just transferred your subscription and see this error message, please try back later.
at Microsoft.WindowsServerSolutions.DDNS.AzureRmDnsServer.GetARecords(String domainName) in E:\WSE-ServicesAndTools\src\ServicesAndTools\DDNS\DDNS\AzureR...).
[5840] 220504.122340.0653: DomainConfigWizard: FailReason from Domain Manager Object Model operations: CommunicationFailure

This gives some insight to the root cause but I am not sure how to go from here to fix this.

Michael Westphal 11 Reputation points

2022-05-05T08:52:26.693+00:00

Hello Chris,

I have the same problems since Monday.
The logs show the same errors.

The Server think I have the same IP- Address since Monday, what is not true.

I hope that this will be fixed by Microsoft soon.
ChrisWY27 136 Reputation points

2022-05-05T11:48:43.283+00:00

I looked for any updates that could have caused this but didn't see any yet this week happening before the change. Mine too stopped working Monday at like 3am EST.
Michael Toth 1 Reputation point

2022-05-08T02:56:42.28+00:00

Same here. The kicker is I'm a military member and it's going to be at least 6 weeks before I can physically get in front of the machine.

Hope nothing requires attention between now and then....
Samriddhi Chaturvedi 226 Reputation points Microsoft Employee

2022-05-11T22:32:01.573+00:00

Hi
We have made some changes and changes and expect the issue to go away.
Can you please verify at your end/setups ?
ChrisWY27 136 Reputation points

2022-05-12T02:08:41.38+00:00

Still seeing the same issue. Made sure all updates were applies and rebooted. I attached my dashboard.log with the sensitive data covered in x's. I had to convert it to a pdf as the forum wasn't allowing me to upload it as a .log or .txt file. The server is still trying to update remotewebaccess using my old ip address not my current public ip.201203-dashboard.pdf
Samriddhi Chaturvedi 226 Reputation points Microsoft Employee

2022-05-14T00:32:36.617+00:00

We were able to get things working on our local test setups.
Can you please verify your setups and see if the issue went away for you.

Thanks and Regards
Samriddhi
Samriddhi Chaturvedi 226 Reputation points Microsoft Employee

2022-05-14T00:32:54.447+00:00

We were able to get things working on our local test setups.
Can you please verify your setups and see if the issue went away for you.

Thanks and Regards
Samriddhi
ChrisWY27 136 Reputation points

2022-05-14T02:05:30.043+00:00

Mine just came back online on its own. Thank you for taking care of this!!!

@Samriddhi Chaturvedi I want to ask though. How likely is this issue to return? Will we be good until the 2027 EOL date?
Gergely Szabo 26 Reputation points

2022-05-15T08:44:13.593+00:00

It seems to be resolved for our domain as well
Samriddhi Chaturvedi 226 Reputation points Microsoft Employee

2022-05-15T17:05:49.6+00:00

No issue is not likely to come back !

Regards
Samriddhi
ChrisWY27 136 Reputation points

2022-05-16T23:50:34.547+00:00

Thank you @Samriddhi Chaturvedi for your hard work on this. I wish I had your ear several years ago when I reported that the mac client connector was (and still is) broken due to a dependency on Objective-C Garbage collection that Sierra+ doesn't allow but at this point I doubt that will ever be fixed.
ChrisWY27 136 Reputation points

2022-11-14T15:41:18.447+00:00

Seeing related issues again now :( . Made a new thread

https://learn.microsoft.com/en-us/answers/questions/1088241/domain-register-and-update-for-remotewebaccesscom.html
Nick Burnell 36 Reputation points

2022-11-14T20:11:11.203+00:00

Same here. One 2012 essentials. Wrong ip address after company move. Cannot remove domain, cannot repair.
Nick Burnell 36 Reputation points

2022-11-15T19:42:43.803+00:00

Just been reading about TLS 1.2 issue. Could this be related?
David and Michelle Kouts 56 Reputation points

2022-11-15T19:48:11.973+00:00

I have the TLS 1.2 fix applied on my machine, but it's still broken for me.

Looks like the information on the previous post about https://dyndns.domains.live.com/service/livedyndns.asmx being down is the cause this time.
Susan Bradley 21 Reputation points

2022-11-16T21:57:06.027+00:00

https://support.microsoft.com/en-us/topic/october-18-2022-kb5020439-os-build-14393-5429-out-of-band-f9840376-4f36-45c3-8dd8-f366c4b884dd

That one for Server 2016
David and Michelle Kouts 56 Reputation points

2022-11-16T22:03:56.093+00:00

KB5020439 came inside the KB5017396 SSU.

Yes, it's already installed on my machine.

No, it did not help.
Sascha 16 Reputation points

2023-09-18T15:17:03.89+00:00

We have the same error on two Server 2016 Essentials after installing the September updates.
Samriddhi Chaturvedi 226 Reputation points Microsoft Employee

2023-09-18T17:38:38.66+00:00

We re actively looking into this.

The Office Maven 131

Can anyone confirm if this is broken once again?

On a brand new/clean Windows Server 2016 Essentials install (with the "SystemDefaultTlsVersions" and "SchUseStrongCrypto" .NET Framework registry settings set to 1) I'm consistently getting an unknown timeout error when attempting to configure a Microsoft personalized domain name within Anywhere Access.

These are the events that are logged in the server's Dashboard.log file:

[4316] 240225.082530.7179: DomainManagerObjectModel: InvokeAsync: action resulted in exception: System.ServiceModel.FaultException`1[Microsoft.WindowsServerSolutions.RemoteAccess.Domains.DomainManagerFault]: The creator of this fault did not specify a Reason. (Fault Detail is equal to DomainManagerFault:[Reason:CommunicationFailure, Message:SubmitCertificateRequest failed, Detail:The request channel timed out while waiting for a reply after 00:01:00. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout. ]).
[4316] 240225.082530.7179: DomainManagerObjectModel: InvokeAsync: handling exception by transferring to eventArgs
[4192] 240225.082530.7179: DomainConfigWizard: Error occurred in Domain Manager Object Model operations: System.ServiceModel.FaultException`1[Microsoft.WindowsServerSolutions.RemoteAccess.Domains.DomainManagerFault]: The creator of this fault did not specify a Reason. (Fault Detail is equal to DomainManagerFault:[Reason:CommunicationFailure, Message:SubmitCertificateRequest failed, Detail:The request channel timed out while waiting for a reply after 00:01:00. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout. ]).
[4192] 240225.082530.7179: DomainConfigWizard: FailReason from Domain Manager Object Model operations: CommunicationFailure

It appears that the Anywhere Access config wizard is able to successfully sign in to the Microsoft Live account, but then times out with a "CommunicationFailure" error when calling the "SubmitCertificateRequest" method. Looks to me like it's an issue occurring over on Microsoft's backend.

ChrisWY27 136

I haven't tried to set up a new WSE 16 box but my existing remotewebaccess domains still seem to be working, though I also pay for no-ip to have a backup dynamic dns.

I have this note I made to myself from Sept of 2022 (the last time I installed WSE16) to add these values via PowerShell but not sure if that would fix it for you.

# PowerShell
New-ItemProperty -Path "HKLM:\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v2.0.50727" -Name "SystemDefaultTlsVersions" -Value 1 -PropertyType DWORD -Force
New-ItemProperty -Path "HKLM:\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v2.0.50727" -Name "SchUseStrongCrypto" -Value 1 -PropertyType DWORD -Force
New-ItemProperty -Path "HKLM:\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319" -Name "SystemDefaultTlsVersions" -Value 1 -PropertyType DWORD -Force
New-ItemProperty -Path "HKLM:\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319" -Name "SchUseStrongCrypto" -Value 1 -PropertyType DWORD -Force

New-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\.NETFramework\v2.0.50727" -Name "SystemDefaultTlsVersions" -Value 1 -PropertyType DWORD -Force
New-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\.NETFramework\v2.0.50727" -Name "SchUseStrongCrypto" -Value 1 -PropertyType DWORD -Force
New-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\.NETFramework\v4.0.30319" -Name "SystemDefaultTlsVersions" -Value 1 -PropertyType DWORD -Force
New-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\.NETFramework\v4.0.30319" -Name "SchUseStrongCrypto" -Value 1 -PropertyType DWORD -Force

ChrisWY27 136 Reputation points

2024-03-20T19:02:14.1433333+00:00

Also found this post of mine where it looks like I reported a similar inability to register in Nov '22 and Samriddhi Chaturvedi from Microsoft responded resolving it internally:

https://learn.microsoft.com/en-us/answers/questions/1088241/domain-register-and-update-for-remotewebaccess-com?page=2#answers
The Office Maven 131 Reputation points

2024-03-26T15:21:10.97+00:00

@ChrisWY27 Thank you for your responses.

Yes, I've already added all of the required .NET Framework registry keys that you've mentioned (and restarted the server), but that makes no difference here. The registry keys do allow the Microsoft (Live) Account to be successfully signed into, but they do not prevent the timeout error from occurring when the domain name setup wizard attempts to communicate with the Microsoft personalized domain name provider service.

For me, the timeout issue appears any time I try to either set up a remotewebaccess.com domain name for the very first time (on a newly setup 2016 Essentials server), or whenever I attempt to change an existing remotewebaccess.com domain name when one has already been set up previously on the Essentials server (i.e. open Settings, go to the Anywhere Access tab, click the Set up button under the domain name section, in the domain name set up wizard that appears click Next -> choose “Use another domain name or domain name service provider” (do not choose the release option or you may loose your existing domain prefix) -> choose “I want to set up a new domain name” -> click Next -> Next -> sign in to your Live account -> choose “Choose a registered name” and select your existing domain prefix from the drop-down list -> click Next -> timeout error happens every time after about 30 seconds or so).

Thus, it definitely appears to be an issue taking place over on Microsoft's (back)end to me. I'm just wondering if others are able to reproduce the issue. I have lots of customers running Windows Server 2016 Essentials that are reporting the issue to me, but I'm not seeing anyone else reporting it over here on these Microsoft forums (which seems a bit odd). Thanks again for your input.
ChrisWY27 136 Reputation points

2024-03-28T14:23:03.55+00:00

My best guess is either not many are changing domains, or there are few users like us freshly installing WSE '16. Perhaps I can spin up a VM later and try to verify the same is happening on my end, though if multiple customers are reporting it to you it's most likely an issue on the Microsoft end. Perhaps @Samriddhi Chaturvedi can chime in if they still work there.
ChrisWY27 136 Reputation points

2024-03-28T17:59:44.6733333+00:00

@The Office Maven I found a VM with WSE already installed and attempted to set up a domain name unfortunately also seeing the following:

The error in the Dashboard.log was "The request channel timed out while waiting for a reply".
The Office Maven 131 Reputation points

2024-03-29T13:48:40.8933333+00:00

@ChrisWY27 Yes, that's the (generic timeout) error I'm seeing as well... So it's definitely reproducible by others. Hopefully someone from Microsoft sees this thread and can get the issue resolved for everyone. Thanks again.
Olaf Brachvogel 0 Reputation points

2024-04-07T15:53:47.82+00:00

Hello Yes, Essentials also stopped working on my Server 2016Essentials since April 4th, 2024. All Netframework registry settings are present

With (Get-ItemProperty "HKLM:SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full").Version the currently installed version is displayed from .net version 4 onwards. With (Get-ItemProperty "HKLM:SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.5").Version the currently installed version is displayed from .net version 3.5 onwards. # PowerShell New-ItemProperty -Path "HKLM:\SOFTWARE\WOW6432Node\Microsoft.NETFramework\v2.0.50727" -Name "SystemDefaultTlsVersions" -Value 1 -PropertyType DWORD -Force New-ItemProperty -Path "HKLM:\SOFTWARE\WOW6432Node\Microsoft.NETFramework\v2.0.50727" -Name "SchUseStrongCrypto" -Value 1 -PropertyType DWORD -Force New-ItemProperty -Path "HKLM:\SOFTWARE\WOW6432Node\Microsoft.NETFramework\v4.0.30319" -Name "SystemDefaultTlsVersions" -Value 1 -PropertyType DWORD -Force New-ItemProperty -Path "HKLM:\SOFTWARE\WOW6432Node\Microsoft.NETFramework\v4.0.30319" -Name "SchUseStrongCrypto" -Value 1 -PropertyType DWORD -Force New-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft.NETFramework\v2.0.50727" -Name "SystemDefaultTlsVersions" -Value 1 -PropertyType DWORD -Force New-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft.NETFramework\v2.0.50727" -Name "SchUseStrongCrypto" -Value 1 -PropertyType DWORD -Force New-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft.NETFramework\v4.0.30319" -Name "SystemDefaultTlsVersions" -Value 1 -PropertyType DWORD -Force New-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft.NETFramework\v4.0.30319" -Name "SchUseStrongCrypto" -Value 1 -PropertyType DWORD -Force v4.5.23026 v4.5.1 -------------------------------------------------- -------------------------------------------------- -------------------------------------------------- ------------ New-ItemProperty -Path "HKLM:\SOFTWARE\WOW6432Node\Microsoft.NETFramework\v4.5.1" -Name "SystemDefaultTlsVersions" -Value 1 -PropertyType DWORD -Force New-ItemProperty -Path "HKLM:\SOFTWARE\WOW6432Node\Microsoft.NETFramework\v4.5.1" -Name "SchUseStrongCrypto" -Value 1 -PropertyType DWORD -Force New-ItemProperty -Path "HKLM:\SOFTWARE\WOW6432Node\Microsoft.NETFramework\v4.5.23026" -Name "SystemDefaultTlsVersions" -Value 1 -PropertyType DWORD -Force New-ItemProperty -Path "HKLM:\SOFTWARE\WOW6432Node\Microsoft.NETFramework\v4.5.23026" -Name "SchUseStrongCrypto" -Value 1 -PropertyType DWORD -Force

TLS 1.0., 1.1, 1.2 on

The DNS information for the server cannot be updated because it cannot connect to the domain name provider. Contact the domain name provider

Domain Name Provider pleas help Thanks
Giorgio 0 Reputation points

2024-04-29T13:24:07.54+00:00

Still not working its desolating , what a service microsoft gives , shame on microsoft
Jesse Flintoff 226 Reputation points

2024-04-29T22:59:23.22+00:00

Samriddhi will look after us.
Samriddhi Chaturvedi 226 Reputation points Microsoft Employee

2024-05-03T21:31:13.22+00:00

We are still actively investigating this. Thanks for your patience.
Samriddhi Chaturvedi 226 Reputation points Microsoft Employee

2024-10-22T18:34:53.4233333+00:00

I get emails but i dont see the latest comments here.
Susan E Bradley, CPA/CITP/CFF, GSEC 5 Reputation points

2024-10-22T18:42:39.7+00:00

It's like the threads from OfficeMaven have been moved.
Susan E Bradley, CPA/CITP/CFF, GSEC 5 Reputation points

2024-10-22T18:43:51.27+00:00
You have to sort by newest and not by helpful and then it shows up. OfficeMaven said:

@Samriddhi Chaturvedi apparently the ability to set up a remotewebaccess.com Microsoft personalized domain name is once again broken in the Anywhere Access feature of Windows Server 2016 Essentials. I'm absolutely flabbergasted that you guys cannot keep this feature working. It gets broken (by Microsoft) every few months, and then it takes multiple months to get you guys to become aware of the issue and then finally resolve it again. I've never seen anything like it in all my years of computer programming. It really is quite maddening. I realize that it's not your fault, but you do have to admit that it's more than a bit ridiculous.

Anyway... Attempting to set up a remotewebaccess.com domain name in Essentials is once again producing the generic "unknown error occurred" error message. Looking in the server's Dashboard.log file shows the following error getting logged:

YAMLCopy

[10188]

I assume that this has something to do with the fact that Microsoft has now disabled the use of basic authentication in their Live accounts as is mentioned here (although I cannot be sure):

Modern Authentication Methods now needed to continue syncing Outlook Email in non-Microsoft email apps

My understanding is that Windows Server 2016 Essentials is supported until January 12, 2027 and so it would be really nice if this issue could be resolved (again).

Thank you!
Anna Ragaglia - R.I.H. IT Services 0 Reputation points

2024-11-29T11:38:38.4766667+00:00

Hello @Samriddhi Chaturvedi, unfortunately it seems to be down again.Windows Server 2016. Our Dashboard.log reports:

[9096] 241129.122823.6490: DomainConfigWizard: Next Page: progressPage [5676] 241129.122827.3279: DomainManagerObjectModel: InvokeAsync: action resulted in exception: System.ServiceModel.FaultException1[Microsoft.WindowsServerSolutions.RemoteAccess.Domains.DomainManagerFault]: Il creatore dell'errore non ha specificato Reason. (Dettaglio errore è uguale a DomainManagerFault:[Reason:CommunicationFailure, Message:SubmitCertificateRequest failed, Detail:System.Web.Services.Protocols.SoapException: Live Dynamic DNS has encountered an internal error. This error has been logged. ---> System.Net.WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. ---> System.Security.Authentication.AuthenticationException: The remote certificate is invalid according to the validation procedure. at System.Net.Security.SslState.StartSendAuthResetSignal(ProtocolToken message, AsyncProtocolRequest asyncRequest, Exception exception) at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.Check...). [5676] 241129.122827.3279: DomainManagerObjectModel: InvokeAsync: handling exception by transferring to eventArgs [9096] 241129.122827.3299: DomainConfigWizard: Error occurred in Domain Manager Object Model operations: System.ServiceModel.FaultException1[Microsoft.WindowsServerSolutions.RemoteAccess.Domains.DomainManagerFault]: Il creatore dell'errore non ha specificato Reason. (Dettaglio errore è uguale a DomainManagerFault:[Reason:CommunicationFailure, Message:SubmitCertificateRequest failed, Detail:System.Web.Services.Protocols.SoapException: Live Dynamic DNS has encountered an internal error. This error has been logged. ---> System.Net.WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. ---> System.Security.Authentication.AuthenticationException: The remote certificate is invalid according to the validation procedure. at System.Net.Security.SslState.StartSendAuthResetSignal(ProtocolToken message, AsyncProtocolRequest asyncRequest, Exception exception) at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.Check...). [9096] 241129.122827.3299: DomainConfigWizard: FailReason from Domain Manager Object Model operations: CommunicationFailure

Could you help us to solve this issue?

Thank you so much
Jesse Flintoff 226 Reputation points

2024-11-30T01:30:41.2733333+00:00

Same for me
Gordon Currie 1 Reputation point

2024-12-10T21:20:27.8733333+00:00

The DynDNS service seems to be borked.
Amy Stinson 11 Reputation points

2024-12-21T01:16:20.7033333+00:00

It is December 20th, and I'm having the same problem.

Client's SSL certificate apparently expired, which broke adding a machine to the domain and broke remote access. I've been trying for days to get the remote access working. I have a client's certificate expiring in 17 days and another in 42 days.
Gordon Currie 1 Reputation point

2025-01-18T19:37:16.3433333+00:00

Has been failing since August 2024. Can we somehow escalate this?

Accepted answer

Samriddhi Chaturvedi 226 Reputation points Microsoft Employee

2022-05-14T00:32:02.177+00:00

We were able to get things working on our local test setups.
Can you please verify your setups and see if the issue went away for you.

Thanks and Regards
Samriddhi
Please sign in to rate this answer.

5 people found this answer helpful.
David and Michelle Kouts 56 Reputation points

2024-05-03T03:07:07.81+00:00

@Samriddhi Chaturvedi , this is happening again. Are you still able to assist?

Jesse Flintoff 226 Reputation points

2024-10-19T22:47:07.39+00:00

Good morning @Samriddhi Chaturvedi .I hope you're well. This seems to be down again. Can you work your magic please? Kindest regards.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

41 additional answers

Samriddhi Chaturvedi 226 Reputation points Microsoft Employee

2022-11-14T20:35:00.497+00:00

We are investigating this with highest priority.
Please sign in to rate this answer.

5 people found this answer helpful.
mcbsys 126 Reputation points

2022-11-14T21:01:22.147+00:00

@Samriddhi Chaturvedi , great to see you are on it. See also this thread where one user posted a log:

https://learn.microsoft.com/en-us/answers/questions/1088241/domain-register-and-update-for-remotewebaccesscom.html

It seems that the dynamic DNS computer is offline:

C:\>curl https://dyndns.domains.live.com/service/livedyndns.asmx curl: (28) Failed to connect to dyndns.domains.live.com port 443 after 21091 ms: Timed out

The Office Maven 131 Reputation points

2022-11-15T19:07:24.833+00:00

@Samriddhi Chaturvedi , while you're at it, can you find out why these Microsoft online services links are no longer working in Windows Server Essentials?

https://go.microsoft.com/fwlink/?LinkID=785361
OnlineServicesConfigFile.xml
OnlineServicesConfigLanguageResourceFile.xml

https://go.microsoft.com/fwlink/?LinkID=785361
CloudServiceEnvironment.xml

Microsoft is constantly breaking all of this stuff and it's getting to be really annoying. I don't understand why the online services backend stuff in Essentials can't just be left alone. I understand Microsoft wanting to push everyone over to using Azure, but Windows Server 2016 Essentials is supported until 1/12/2027, and so its feature set should actually work until that time. No?

mcbsys 126 Reputation points

2022-11-15T19:27:29.173+00:00

One does wonder why there isn't some automated monitoring and alerting when a core service goes down, followed by automatic or manual remediation. It's basic WebOps. Would really like to see Microsoft assign at least one person to monitor and maintain Essentials so that it continues to function as promised.

David and Michelle Kouts 56 Reputation points

2022-11-16T21:01:17.503+00:00

@Samriddhi Chaturvedi , any updates on this?

Samriddhi Chaturvedi 226 Reputation points Microsoft Employee

2022-11-16T21:03:46.543+00:00

We are still investigating this on priority.
And have no favorable updates at this moment.
Will keep you all posted as soon as we have one.

Sorry for the inconvenience.
Regards
Samriddhi

Jesse Flintoff 226 Reputation points

2022-11-16T21:12:04.737+00:00

Thank you
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Samriddhi Chaturvedi 226 Reputation points Microsoft Employee

2022-11-17T00:25:55.757+00:00

We have pretty much identified the root cause of the issue and are working on a fix.
As far as I can say, it is a new issue and not related to TLS or any recent updates.
The endpoint VMs have gone into an inconsistent state and we are trying to revive them.

Thanks and Regards
Samriddhi
Please sign in to rate this answer.

4 people found this answer helpful.
David and Michelle Kouts 56 Reputation points

2022-11-17T00:28:36.35+00:00

Thank you so much! That description certainly fits with the server timeout we've seen in the logs.

Jesse Flintoff 226 Reputation points

2022-11-17T00:41:04.487+00:00

Thank you

ChrisWY27 136 Reputation points

2022-11-17T02:44:02.4+00:00

Big shout out to @Samriddhi Chaturvedi for the complete transparency, not something you see in support these days.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Samriddhi Chaturvedi 226 Reputation points Microsoft Employee

2022-11-18T20:48:05.573+00:00

The issue seems to be resolved and our VMs (endpoints are back up).
Can you please check and confirm if things are fine at your end.

Thanks and Regards
Samriddhi
Please sign in to rate this answer.

3 people found this answer helpful.
David and Michelle Kouts 56 Reputation points

2022-11-18T20:50:53.347+00:00

Confirmed, on my (WS Essentials 2016) box!

Thank you so much, @Samriddhi Chaturvedi !!

ChrisWY27 136 Reputation points

2022-11-18T23:14:21.647+00:00

Confirmed working as well.

Thanks!!!

Brian Stevens 36 Reputation points

2022-11-19T04:15:23.867+00:00

Problem solved here too. Thank you! Been traveling for the last week but luckily my IP hasn't changed. Wouldn't have known except for the Health Reports.

Jesse Flintoff 226 Reputation points

2023-09-19T21:09:50.2533333+00:00

Appears to be fixed now. Nice work everyone.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Rob 66 Reputation points

2022-05-05T09:13:40.907+00:00

I am seeing the same issue after a router reboot changed the external IP address. I am not seeing the same error in my Dashboard.log but I am seeing something odd, the old external IP address is shown

[7788] 220505.095922.2483: ConnectivityCenter: DomainNameProviderCredentials.CredentialsStatus: True
[3512] 220505.095922.2483: ConnectivityCenter: Job finish. Result: Success
[10524] 220505.095922.2483: ConnectivityCenter: Job DomainNameProviderCredentialsDiagnosticsJob complete, 64% done.
[6420] 220505.095922.4824: ConnectivityCenter: DomainServiceReachableInfo.ReachableStatus: True
[11200] 220505.095922.4824: ConnectivityCenter: Job finish. Result: Success
[10524] 220505.095922.4824: ConnectivityCenter: Job DomainServiceReachableDiagnosticsJob complete, 71% done.
[4720] 220505.095922.4980: ConnectivityCenter: DomainNameResolveableInfo.ExternalIP: 86.170.204.53
[9816] 220505.095922.4980: ConnectivityCenter: Job finish. Result: Success
[10524] 220505.095922.4980: ConnectivityCenter: Job DomainNameResolveableDiagnosticsJob complete, 78% done.
[10260] 220505.095922.4980: ConnectivityCenter: DDNSUpdateAttemptionInfo.DDNSUpdateStatus: False
[7456] 220505.095922.4980: ConnectivityCenter: Job finish. Result: Success
[10524] 220505.095922.4980: ConnectivityCenter: Job DDNSUpdateDiagnosticsJob complete, 85% done.
[10016] 220505.095922.4980: ConnectivityCenter: Global event triggered for port: 80.
[8224] 220505.095922.6543: ConnectivityCenter: Service Call Finished on Port: 443
[8224] 220505.095922.6543: ConnectivityCenter: Global event triggered for port: 443.
[10016] 220505.095922.6543: ConnectivityCenter: ConnectivityInfo.HttpsInbound: True
[10016] 220505.095922.6543: ConnectivityCenter: ConnectivityInfo.Inbound: True
[216] 220505.095922.6543: ConnectivityCenter: Job finish. Result: Success
[10524] 220505.095922.6543: ConnectivityCenter: Job InboundConnectivityDiagnosticsJob complete, 92% done.
[7052] 220505.095928.8261: DomainManagerObjectModel: Calling KeepAlive for instanceID=2
[7052] 220505.095928.8261: DomainManagerObjectModel: KeepAlive succeeded for instanceID=2
[7280] 220505.095938.1855: ConnectivityCenter: NdfDiagnoseIncident returns 0x0,
[7280] 220505.095938.1855: ConnectivityCenter: 0 root causes identfied
[7280] 220505.095938.1855: ConnectivityCenter: DoubleNatInfo.DoubleNat: False
[4540] 220505.095938.1855: ConnectivityCenter: Job finish. Result: Success
[10524] 220505.095938.1855: ConnectivityCenter: Job DoubleNatDiagnosticsJob complete, 100% done.
[6164] 220505.095938.2168: ConnectivityCenter: Microsoft.WindowsServerSolutions.Connectivity.Analyzers.FirewallConfigurationAnalyzer analyze completed. 0 suggestions found.
[6164] 220505.095938.2168: ConnectivityCenter: Microsoft.WindowsServerSolutions.Connectivity.Analyzers.InboundConnectivityAnalyzer analyze completed. 0 suggestions found.
[6164] 220505.095938.2168: ConnectivityCenter: Microsoft.WindowsServerSolutions.Connectivity.Analyzers.DoubleNatConfigurationAnalyzer analyze completed. 0 suggestions found.
[6164] 220505.095938.2168: ConnectivityCenter: RemoteAccessAnalyzer: VPN server deployment result: InstallationSucceeded
[6164] 220505.095938.2168: ConnectivityCenter: Microsoft.WindowsServerSolutions.Connectivity.Analyzers.RemoteAccessAnalyzer analyze completed. 0 suggestions found.
[6164] 220505.095938.2168: ConnectivityCenter: Microsoft.WindowsServerSolutions.Connectivity.Analyzers.DomainNameConfigAnalyzer analyze completed. 0 suggestions found.
[6164] 220505.095938.2168: ConnectivityCenter: Microsoft.WindowsServerSolutions.Connectivity.Analyzers.DomainNameExpireAnalyzer analyze completed. 0 suggestions found.
[6164] 220505.095938.2168: ConnectivityCenter: Microsoft.WindowsServerSolutions.Connectivity.Analyzers.DomainNameNearlyExpireAnalyzer analyze completed. 0 suggestions found.
[6164] 220505.095938.2168: ConnectivityCenter: Microsoft.WindowsServerSolutions.Connectivity.Analyzers.DomainNameProviderCredentialsAnalyzer analyze completed. 0 suggestions found.
[6164] 220505.095938.2324: ConnectivityCenter: Microsoft.WindowsServerSolutions.Connectivity.Analyzers.DomainNameResolveableAnalyzer analyze completed. 0 suggestions found.
[6164] 220505.095938.2324: ConnectivityCenter: Microsoft.WindowsServerSolutions.Connectivity.Analyzers.DomainServiceReachableAnalyzer analyze completed. 0 suggestions found.
[6164] 220505.095938.2793: ConnectivityCenter: DDNSUpdateAnalyzer: DDNS update failed, should be manual fixed
[6164] 220505.095938.2793: ConnectivityCenter: Microsoft.WindowsServerSolutions.Connectivity.Analyzers.DDNSUpdateAnalyzer analyze completed. 1 suggestions found.
[6164] 220505.095938.2793: ConnectivityCenter: Microsoft.WindowsServerSolutions.Connectivity.Analyzers.CertificateAnalyzer analyze completed. 0 suggestions found.
[6164] 220505.095938.2793: ConnectivityCenter: Microsoft.WindowsServerSolutions.Connectivity.Analyzers.IisConfigurationAnalyzer analyze completed. 0 suggestions found.
[6164] 220505.095938.2793: ConnectivityCenter: Microsoft.WindowsServerSolutions.Connectivity.Analyzers.TsGatewayConfigurationAnalyzer analyze completed. 0 suggestions found.
[6164] 220505.095938.2793: ConnectivityCenter: Current SQM Data is 2064383.
[10524] 220505.095938.2793: ConnectivityCenter: Diagnositcs completed. Status: Success
[10524] 220505.095938.2949: ConnectivityCenter: Suggestion: An error occurred while updating the dynamic DNS information for your server with the information that you gave your domain name service provider. Please try again later. If this problem continues, contact your domain name service provider for support.
[10524] 220505.095938.2949: ConnectivityCenter: Overall status: Error
[10524] 220505.095938.2949: ConnectivityCenter: Properties updated.

I have updated .Net to 4.8 just in case there is something odd there but I can't test that until I restart the server which will be later this evening
Please sign in to rate this answer.

2 people found this answer helpful.
ChrisWY27 136 Reputation points

2022-05-05T11:47:15.1+00:00

The dashboard log might only happen if you try to repair or alter the anywhere access domain name through the wizard.

Where did you find the other log? I'll check mine.

Josh K 16 Reputation points

2022-05-05T20:55:53.803+00:00

Same issue here. Service when down after a router reboot and public IP address change.
If I ping my old domain (domain).remotewebaccess.com it returns the OLD public address I had before.

Very strange.

Rob 66 Reputation points

2022-05-06T08:35:30.44+00:00

So the .Net update didn't have any effect, I suspected it wouldn't but it was worth a shot.

Samriddhi Chaturvedi 226 Reputation points Microsoft Employee

2022-05-14T00:33:05.22+00:00

We were able to get things working on our local test setups.
Can you please verify your setups and see if the issue went away for you.

Thanks and Regards
Samriddhi
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

remotewebaccess.com Anywhere access broken on Server 2016 Again?

41 additional answers

Your answer