Issue with accessing accessing ECP in exchange2019

Nandan NK 50 Reputation points
2024-06-25T06:40:40.73+00:00

We are not able to login to the Exchange 2019 ECP after logging to the ECP portal on both internal and external URL.

We have performed IIS reset, CAS update, recreated virtual directory, rebooted exchange servers also validated IP domain restriction nothing is preset, can someone help on this.

Only we have client access rule restriction. that is allowing the source from where I'm trying to connect.

User's image

Exchange Server Management
Exchange Server Management
Exchange Server: A family of Microsoft client/server messaging and collaboration software.Management: The act or process of organizing, handling, directing or controlling something.
7,461 questions
Microsoft Exchange
Microsoft Exchange
Microsoft messaging and collaboration software.
442 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Jake Zhang-MSFT 2,635 Reputation points Microsoft Vendor
    2024-06-26T07:11:15.0866667+00:00

    Hi @Nandan NK，

    Welcome to the Microsoft Technical Support Forum.

    Based on your description, you are currently unable to log on to the Exchange 2019 ECP.

    I suggest that you try the following methods to troubleshoot the error:

    1. Clear your browser cache or try to access the ECP from another browser or incognito window.
    2. Make sure that the DNS configuration of the internal and external URLs is correct and can be resolved to the correct IP address.
    3. Make sure that the SSL certificate assigned to the ECP virtual directory is valid and has not expired. You can check this under the bindings of the ECP site in IIS Manager.
    4. Make sure that the client access rules are configured correctly. Sometimes they can inadvertently block access. Rules can be viewed and edited using the Exchange Management Shell.

    Get-ClientAccessRule | Format-Table Name, Action, Priority

    If necessary, you can temporarily disable client access rules to see if they are the cause:

    Disable-ClientAccessRule -Identity "RuleName"

    Please feel free to contact me if you have any queries.

    Best,

    Jake Zhang