Microsoft Remote Connectivity Analyzer

What is the version of Exchange?

Sorry, forgot to mention that...it is exchange 2019 cu 11

Did you configure your MAPi/RPC VDs?
if not please configure
Try disabling IPv6 as well

@MAS,

Thats RPC,


Server           :***
ExternalHostname : mail.mydomainname.com.kw
InternalHostname : mail.mydomainname .com.kw

thats mapi

Server      :***
ExternalUrl : https://mail.mydomainname.com.kw/mapi
InternalUrl : https://mail.mydomainname.com.kw/mapi

found this fix on the registry would it work?

HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc\RpcProxy



Value name: ValidPorts

Value data: ExchangeServer :6001-6002; ExchangeServerFQDN :6001-6002; ExchangeServer :6004; ExchangeServerFQDN :6004


Note:   * ExchangeServer should be the NetBIOS name of Mailbox server.

   * ExchangeServerFQDN should be the fully qualified domain name (FQDN) of Mailbox server.


my current value is

myExchangeServerName:593;myExchangeServerName :49152-65535

Yes. That would fix your issue.

I will take snapshot of my vm and apple that fix

@MAS,

I did change it to

ServerName:6001-6002;ServerName.MyDomainName.com.kw:6001-6002;ServerName:6004;ServerName.MyDomainName.com.kw:6004

yet i still get that error,

These are warnings, not errors, and they are benign.

Exchange 2019 uses MAPI/HTTP not RPC/HTTP.

@Michael,
I see, thanks for the tip.

But when I test via remote connectivity i'm getting an error not a warning,


I got about 12 Exchange servers and i tested another without any errors.

Does it succeed under the MAPI/HTTP tree? ExRCA tests both.

@Michael,
Sorry I didnt get you?

On remote connectivity there is no options to select for testing

Do you have ARR or firewall behind ?
If yes you will have to check that first.


Did you update your server to the latest build?
If not please do that test..

Both MAPI over HTTP and RPC over HTTP should be tested. Just one needs to work.
(I have warnings for both for the standard reason:
.)

You can also look at managed availability on the server to see what specific components are marked off line (if any) and see if there is an additional error reason logged with MA.

@MAS,

No we dont have ARR in our IIS and for the firewall, I will double check with our network engineer if there is any exchange port that is not open on the new exchange server and i will get back to you.

Yes, running the latest CU

Thanks,

@Smith,

I understand if it was a warning but it is an error not a warning.

Thanks,

@MAS,

Ports are open,

Thanks,

Please try the same after patching with the latest CU and security ups.

@MAS,

I already have the latest version, cu and updates.

I also have another issue i already posted here, every morning mail flow becomes so slow and the only way to make it work again is rebooting the server. I've checked everything, disk capacity, cpu, ram, host.

Restarting the services doesnt work. as soon i reboot everything goes back to normal all day.
thanks,

Are there warnings on both or just on one?

Hello,
its an error not warning,

I understand. But do BOTH "RPC over HTTP connectivity" and "MAPI over HTTP connectivity" fail?

Hello,

Mapi over is a warning,



rpc over http is an error

Do you have any clients so old as to require RPC over HTTP? (Outlook 2010 or before)

@Smith,

Not really, they're office 2016/2019.

So I can ignore that error in this case?

There is no workaround it to change it to warning instead?

Not that I know of. There is probably something wrong, perhaps Get-OutlookAnywhere or Get-OutlookProvider would show it. But since you have newer clients, they aren't using RPC/HTTP anyway. I wouldn't spend too much time on it.

get-outlookanywhere results,


[PS] C:\Windows\system32>Get-OutlookAnywhere
The task wasn't able to connect to IIS on the server 'ABC-EXCHMB-01.MyDomainName.com.kw'. Make sure that the server exists
and can be reached from this computer: The RPC server is unavailable.
    + CategoryInfo          : ReadError: (ABC-EXCHMB-01\Rpc (Default Web Site):ADObjectId) [Get-OutlookAnywhere], IISN
   otReachableException
    + FullyQualifiedErrorId : [Server=ABC-EXCH02,RequestId=fbbe9501-b8a1-434f-b21d-ec74db0ca583,TimeStamp=11/29/2021 7
   :00:47 PM] [FailureCategory=Cmdlet-IISNotReachableException] 9B02FD9C,Microsoft.Exchange.Management.SystemConfigur
  ationTasks.GetRpcHttp
    + PSComputerName        : abc-exch02.MyDomainName.com.kw



RunspaceId                         : b6020bc9-2534-4a36-bd27-f93e7ebe95d1
ServerName                         : ABC-EXCH02
SSLOffloading                      : True
ExternalHostname                   : mail.MyDomainName.com.kw
InternalHostname                   : mail.MyDomainName.com.kw
ExternalClientAuthenticationMethod : Ntlm
InternalClientAuthenticationMethod : Negotiate
IISAuthenticationMethods           : {Basic, Ntlm, Negotiate}
XropUrl                            :
ExternalClientsRequireSsl          : True
InternalClientsRequireSsl          : True
MetabasePath                       : IIS://ABC-EXCH02.MyDomainName.com.kw/W3SVC/1/ROOT/Rpc
Path                               : C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\rpc
ExtendedProtectionTokenChecking    : None
ExtendedProtectionFlags            : {}
ExtendedProtectionSPNList          : {}
AdminDisplayVersion                : Version 15.2 (Build 986.5)
Server                             : ABC-EXCH02
AdminDisplayName                   :
ExchangeVersion                    : 0.20 (15.0.0.0)
Name                               : Rpc (Default Web Site)
DistinguishedName                  : CN=Rpc (Default Web
                                     Site),CN=HTTP,CN=Protocols,CN=ABC-EXCH02,CN=Servers,CN=Exchange Administrative
                                     Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=MyDomainName,CN=Microsoft
                                     Exchange,CN=Services,CN=Configuration,DC=MyDomainName,DC=com,DC=kw
Identity                           : ABC-EXCH02\Rpc (Default Web Site)
Guid                               : 8a791447-ba07-4996-b2cf-84d23dc6995d
ObjectCategory                     : MyDomainName.com.kw/Configuration/Schema/ms-Exch-Rpc-Http-Virtual-Directory
ObjectClass                        : {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirectory}
WhenChanged                        : 11/17/2021 12:48:34 PM
WhenCreated                        : 11/12/2021 2:43:34 PM
WhenChangedUTC                     : 11/17/2021 9:48:34 AM
WhenCreatedUTC                     : 11/12/2021 11:43:34 AM
OrganizationId                     :
Id                                 : ABC-EXCH02\Rpc (Default Web Site)
OriginatingServer                  : ABC-DC-02.MyDomainName.com.kw
IsValid                            : True
ObjectState                        : Changed



outlook provider results,


[PS] C:\Windows\system32>Get-OutlookProvider

Name Server CertPrincipalName TTL
---- ------ ----------------- ---
EXCH        msstd:MyCertName 1
EXPR        msstd:MyCertName  1
WEB         msstd:MyCertName  1


NOTE: ABC-EXCHMB-01 is my old exchange name which i switchedit off at the moment i did not remove it yet.

I think you found your error right there.

@Smith,

U mean because the existing exchange server still exists in the forest?

I'm planning to remove it soon, in this case I will remove it tomorrow.