Lỗi outlook we are having trouble connecting to your account năm 2024
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support. Show Outlook connection issues with Exchange mailboxes caused by the RPC encryption requirement
In this articleOriginal KB number: 3032395 The article only applies to the Microsoft Outlook connection issues that are caused by the RPC encryption requirement. SymptomsWhen you start Microsoft Office Outlook by using a profile that includes a mailbox on a server that's running Microsoft Exchange Server 2010, Exchange Server 2013, or Exchange Server 2016, you may receive the following error messages: Cannot start Microsoft Office Outlook. Unable to open the Outlook window. The set of folders could not be opened. Unable to open your default e-mail folders. The Microsoft Exchange Server computer is not available. Either there are network problems or the Microsoft Exchange Server computer is down for maintenance. The connection to the Microsoft Exchange Server is unavailable. Outlook must be online or connected to complete this action. Unable to open your default e-mail folders. The information store could not be opened. Outlook could not log on. Check to make sure you are connected to the network and are using the proper server and mailbox name. The connection to the Microsoft Exchange Server is unavailable. Outlook must be online or connected to complete this action. However, if you're using a cached mode profile, Outlook doesn't display an error. You may experience the following symptoms:
When you try to create a new Outlook profile for a mailbox on a server that's running Exchange 2010 or Exchange Server 2013, you may receive the following error messages: The action could not be completed. The connection to the Microsoft Exchange Server is unavailable. Outlook must be online or connected to complete this action. The name could not be resolved. The connection to the Microsoft Exchange Server is unavailable. Outlook must be online or connected to complete this action. Outlook could not log on. Check to make sure you are connected to the network and are using the proper server and mailbox name. The connection to the Microsoft Exchange Server is unavailable. Outlook must be online or connected to complete this action. The name could not be resolved. The action could not be completed. Your Server or Mailbox names could not be resolved. ResolutionNote If you are using one of the automated methods (Group Policy or a .prf file), make sure that you fully test the method before you deploy it on a large scale. Method 1: Update or create your Outlook profile with RPC encryptionManually update an existing profileTo manually update an existing Outlook profile so that it uses RPC encryption, follow these steps:
Deploy a Group Policy setting to update existing Outlook profiles with RPC encryptionFrom a client perspective, deploying the Outlook-Exchange encryption setting is probably the simplest solution for organizations that have many Outlook clients. This solution involves a single change on a server (domain controller), and your clients are automatically updated after the policy is downloaded to the client. Outlook 2010By default, the RPC encryption setting is enabled in Outlook 2010. So you should only deploy this setting by using Group Policy for either of the following reasons:
The default Group Policy template for Outlook 2010 contains the Group Policy setting that controls Outlook-Exchange RPC encryption. To update existing Outlook 2010 profiles by using Group Policy, follow these steps:
At this point, the policy setting will be applied on your Outlook client workstations when the Group Policy update is replicated. To test this change, run the following command:
After you run this command, start Registry Editor on the workstation to make sure that the following registry data exists on the client:
If you see this registry data in the registry, the Group Policy setting is applied to this client. Start Outlook to verify that the change resolves the problem. Outlook 2013By default, the RPC encryption setting is enabled in Outlook 2013. So you should only deploy this setting by using Group Policy for either of the following reasons:
The default Group Policy template for Outlook 2013 contains the Group Policy setting that controls Outlook-Exchange RPC encryption. To update existing Outlook 2013 profiles by using Group Policy, follow these steps:
At this point, the policy setting will be applied on your Outlook client workstations when the Group Policy update is replicated. To test this change, run the following command on a workstation:
After you run this command, start Registry Editor on the workstation to make sure that the following registry data exists on the client:
If you see this registry data in the registry, the Group Policy setting is applied to this client. Start Outlook to verify that the change resolves the problem. Method 2: Disable the encryption requirement on all CAS serversImportant Microsoft strongly recommends you leave the encryption requirement enabled on your server, and to use one of the other methods listed in this article. Method 2 is only provided in this article for situations where you cannot immediately deploy the necessary RPC encryption settings on your Outlook clients. If you use Method 2 to allow Outlook clients to connect without RPC encryption, please re-enable the RPC encryption requirement on your CAS servers as quickly as possible to maintain the highest level of client-to-server communication. To disable the required encryption between Outlook and Exchange, follow these steps:
CauseOne possible cause is that you're using Outlook and you disable the Encrypt data between Microsoft Office Outlook and Microsoft Exchange profile setting. The default configuration for Exchange Server 2013 requires RPC Encryption from the Outlook client. This prevents the client from being able to connect. Note The default Exchange Server 2010 Release to Manufacturing (RTM) configuration requires RPC encryption. This behavior is a change from Exchange Server 2010 Service Pack 1 where the RPC encryption requirement is disabled by default. However, any Client Access Server (CAS) deployed prior to Service Pack 1, or upgraded to Service Pack 1, will retain the existing RPC encryption requirement setting which could still prevent the client from being able to connect. |