Ask a question


How can we help you today?

Ask Question
Manage notifications
Subscribe to this question
Geoff Aukett

remotewebaccess.com

Is anyone aware of new issues with the remotewebaccess.com DDNS system?

We have two customers now that have had new WAN IP addresses assigned that have failed to update in their respective remotewebaccess.com domains.

One is using Server Essentials 2012R2 and one is using Server Essentials 2016.

asked05/13/2022 09:24
57 views
Add Comment
Last Activity 05/24/2022 08:17

1 Answer(s)

  • Mariette Knap

    Your server should default to TLS 1.2 as 1.1 and 1.0 are deprecated now and the wizard tries to connect to Microsoft to see if you use remoteaccess.com. Run the following from an elevated Powershell prompt:

    # 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

Restart-Computer -Force

     

    answered 05/24/2022 05:37
    Add Comment
    Geoff Aukett

    Thanks but I was ware of this and had made those changes some time ago. This issue turned to be a wider problem with the remotewebaccess.com DDNS system which is now resolved.

    Reply
    replied 05/24/2022 07:30
Add an Answer