Windows 10: The underlying connection was closed: Could not establish trust relationship for the...

So, I have an app that wants to download some content, but when I launch it, even though I'm connected to the Internet, I get this error. Any solutions?

Here's a screenshot for your reference-




:)

 

Unable to establish a Synchronization Relationship

Problem: Unable to establish a Synchronization Relationship between my new handheld and my work PC.

Setup:

The Handheld is a HP iPAQ 111 Classic running Windows Mobile 6.1.

The Dell PC runs Windows XP Professional on a business LAN, with Outlook 2003.

I have downloaded ActiveSync 4.5 from the Microsoft website (the CD that came with the iPAQ was scratched), and installed it.

I am connecting the handheld to the PC using the USB-2 to mini-USB cable provided with the handheld.

Expectation:

The various documents and help files tell me that when I connect the handheld to the PC for the first time, ActiveSync will open a Synchronization Setup wizard that will allow me to specify what Outlook modules to synchronize with the respective handheld modules.
Cancelling the wizard will cause me to connect in a Guest mode that allows communication but not synchronization.

Reality:

Each time when I connect the handheld to the PC, ActiveSync "thinks" for 20-30 seconds and initiates a Guest connection. I am able to explore the handheld from the PC and transfer Office files via the Guest connection as advertised, but cannot establish the
Synchronization Relationship. All menu items related to Synchronization are grayed out on both machines.

Troubleshooting so far:

I have restarted both machines. I have removed and reinstalled ActiveSync on the PC, using both the ActiveSync installation program and the Windows Add/Remove Programs function. I have toggled Advanced Network Functionality on the handheld. None of these
steps has materially affected the results.

Any suggestions on what else to try will be greatly appreciated.

 

Trust Relationship between Server and DC Fails

I am having problems establishing a trust relationship between a server and a DC.

Here are the things I have tried(that I can rememeber):

• Unjoining and rejoining the Domain
• Running: netdom reset 'computername' /domain:abc /userO:xxx /passwordO:*
• Running Test-ComputerSecureChannel -Repair -Verbose
• Resetting the password of the computer from the DC
• After all of these, Test-ComputerSecureChannel still returns false

Many of the error messages I get revolve around 'Access is Denied'. However, all of these commands are run from elevated PowerShell, as a domain administrator, with the netdom command run on both the local machine and the DC. The local machine is running
Server 2012 and the DC is Server 2016. Any thoughts would be appreciated.

 

Trust relationship between this workstation and the primary domain failed

I want to know the root cause for trust relationship error so please let me know which logs to check to find out exact reason for workstation-domain trust relationship error.

I want to identify issue using the logs available in workstation machine.