[Case sharing] Exchange issue resolution process for IMAP

Environment:

AD + Two Exchange 2013

Cause:

The problem with the original Netizen's fault isIMAPThe problem occurs (535 5.7.3 authentication unsuccessful), I tested it.outlook was found to have a server disconnect error, Telnet is normal, not a foxmail prompt to verify the failure of information, and later I asked him to check Exchange Servercomponentstate(get-servercomponentstateServerName), and found that there are two components that are inactive state, activated by command set-servercomponentstate-identityServerName-componentcomponentname-requester healthapi-stateactive. IMAP can be used normally in the extranet. (A similar problem has occurred in the past that the POP3 component has a problem, causing the 110 port to connect to an instantaneous interrupt)

Process:

I thought it was solved, But at noon time Netizen also told me imap and No, I'll go up and see if the server has two net cards ( dmz NET, p rivate net) , so I configured the receiver to specify the intranet ip restart server, result ems failed to load the server, ECP 500 error occurred, OWA appeared not found NT AUTHORITY\SYSTEM

Fault:

found in log S Ource : MSExchange backendrehydration E Vent ID : 3002, this question is CAS the token for the server is missing.

650) this.width=650; "src=" Http://s4.51cto.com/wyfs02/M01/7E/EA/wKioL1cM1YniZHIpAACI4g_bjXQ413.png "title=" Untitled picture. png "alt=" Wkiol1cm1ynizhipaaci4g_bjxq413.png "/>

Workaround:

1. in theEMSInput Get-clientaccessserver | Add-adpermission-accessrights extendedright-extendedrights"ms-exch-epi-token-serialization","ms-exch-epi-impersonation"-userthe Domain\exchange Servers"

3. back to the original IMAP problem, I use telnet - Port to look at the situation:

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/7E/ED/wKiom1cM1PWxAGoNAAAku4z8Foc592.png "title=" Untitled picture 1.png "alt=" Wkiom1cm1pwxagonaaaku4z8foc592.png "/>

connect the NIC's DNS Configuring a domain-controlled IP (the original user is configured 8.8.8.8 There are also local DNS ), it solves the problem.

This article from "Gs_hao" blog, declined reprint!

[Case sharing] Exchange issue resolution process for IMAP