It appears that my Outlook Anywhere configuration is screwed up on my Exchange 2010 SP1 server, and is causing a piece of third part software to give me errors. It looks for DOMAINNAME.info instead of DOMAINNAME.net, .net is the correct domain . Below is a report using the Exchange Connectivity Test. You can see below that <ASUrl> <OOFUrl> <UMUrl> and <EwsUrl> are all incorrect, they point to the .net address. I've searched on how to fix these errors. Any suggestions would really be appreciated. Thanks! Testing RPC/HTTP connectivity. The RPC/HTTP test completed successfully. Test Steps ExRCA is attempting to test Autodiscover for user@DOMAINNAME.net. Autodiscover was tested successfully. Test Steps Attempting each method of contacting the Autodiscover service. The Autodiscover service was tested successfully. Test Steps Attempting to test potential Autodiscover URL https://DOMAINNAME.net/AutoDiscover/AutoDiscover.xml Testing of the Autodiscover URL was successful. Test Steps Attempting to resolve the host name DOMAINNAME.net in DNS. The host name resolved successfully. Additional Details IP addresses returned: xxx.xxx.xxx.xxx Testing TCP port 443 on host DOMAINNAME.net to ensure it's listening and open. The port was opened successfully. Testing the SSL certificate to make sure it's valid. The certificate passed all validation requirements. Test Steps Validating the certificate name. The certificate name was validated successfully. Additional Details Host name DOMAINNAME.net was found in the Certificate Subject Alternative Name entry. Certificate trust is being validated. The test passed with some warnings encountered. Please expand the additional details. Additional Details ExRCA can only validate the certificate chain using the Root Certificate Update functionality from Windows Update. Your certificate may not be trusted on Windows if the "Update Root Certificates" feature isn't enabled. Testing the certificate date to confirm the certificate is valid. Date validation passed. The certificate hasn't expired. Additional Details The certificate is valid. NotBefore = 2/5/2010 3:52:07 PM, NotAfter = 2/5/2013 3:52:07 PM Checking the IIS configuration for client certificate authentication. Client certificate authentication wasn't detected. Additional Details Accept/Require Client Certificates isn't configured. Attempting to send an Autodiscover POST request to potential Autodiscover URLs. ExRCA successfully retrieved Autodiscover settings by sending an Autodiscover POST. Test Steps ExRCA is attempting to retrieve an XML Autodiscover response from URL https://DOMAINNAME.net/AutoDiscover/AutoDiscover.xml for user user@DOMAINNAME.net. The Autodiscover XML response was successfully retrieved. Additional Details Autodiscover Account Settings XML response: <?xml version="1.0"?> <Autodiscover xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006"> <Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a"> <User> <DisplayName>Firstname Lastname</DisplayName> <LegacyDN>/o=DOMAINNAME/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=Firstname Lastname</LegacyDN> <DeploymentId>efe839ab-f1c0-4e89-8a7a-340bad173a50</DeploymentId> </User> <Account> <AccountType>email</AccountType> <Action>settings</Action> <Protocol> <Type>EXCH</Type> <Server>MAIL.LOCALDOMAIN.net</Server> <ServerDN>/o=DOMAINNAME/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=MAIL</ServerDN> <ServerVersion>738180DA</ServerVersion> <MdbDN>/o=DOMAINNAME/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=MAIL/cn=Microsoft Private MDB</MdbDN> <ASUrl>https://www.DOMAINNAME.net/ews/exchange.asmx</ASUrl> <OOFUrl>https://www.DOMAINNAME.net/ews/exchange.asmx</OOFUrl> <OABUrl>https://www.DOMAINNAME.net/oab/4b125621-f119-4ee4-92ef-cc033646c9ac/</OABUrl> <UMUrl>https://www.DOMAINNAME.net/ews/UM2007Legacy.asmx</UMUrl> <Port>0</Port> <DirectoryPort>0</DirectoryPort> <ReferralPort>0</ReferralPort> <PublicFolderServer>MAIL.LOCALDOMAIN.net</PublicFolderServer> <AD>WIGGUM.LOCALDOMAIN.net</AD> <EwsUrl>https://www.DOMAINNAME.net/ews/exchange.asmx</EwsUrl> <EcpUrl>https://mail.LOCALDOMAIN.net/ecp/</EcpUrl> <EcpUrl-um>?p=customize/voicemail.aspx&amp;exsvurl=1</EcpUrl-um> <EcpUrl-aggr>?p=personalsettings/EmailSubscriptions.slab&amp;exsvurl=1</EcpUrl-aggr> <EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?exsvurl=1&amp;IsOWA=&lt;IsOWA&gt;&amp;MsgID=&lt;MsgID&gt;&amp;Mbx=&lt;Mbx&gt;</EcpUrl-mt> <EcpUrl-ret>?p=organize/retentionpolicytags.slab&amp;exsvurl=1</EcpUrl-ret> <EcpUrl-sms>?p=sms/textmessaging.slab&amp;exsvurl=1</EcpUrl-sms> </Protocol> <Protocol> <Type>EXPR</Type> <Server>www.DOMAINNAME.net</Server> <ASUrl>https://mail.DOMAINNAME.info/ews/exchange.asmx</ASUrl> <OOFUrl>https://mail.DOMAINNAME.info/ews/exchange.asmx</OOFUrl> <OABUrl>https://www.DOMAINNAME.net/OAB/4b125621-f119-4ee4-92ef-cc033646c9ac/</OABUrl> <UMUrl>https://mail.DOMAINNAME.info/ews/UM2007Legacy.asmx</UMUrl> <Port>0</Port> <DirectoryPort>0</DirectoryPort> <ReferralPort>0</ReferralPort> <SSL>On</SSL> <AuthPackage>Ntlm</AuthPackage> <EwsUrl>https://mail.DOMAINNAME.info/ews/exchange.asmx</EwsUrl> <EcpUrl>https://www.DOMAINNAME.net/ecp/</EcpUrl> <EcpUrl-um>?p=customize/voicemail.aspx&amp;exsvurl=1</EcpUrl-um> <EcpUrl-aggr>?p=personalsettings/EmailSubscriptions.slab&amp;exsvurl=1</EcpUrl-aggr> <EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?exsvurl=1&amp;IsOWA=&lt;IsOWA&gt;&amp;MsgID=&lt;MsgID&gt;&amp;Mbx=&lt;Mbx&gt;</EcpUrl-mt> <EcpUrl-ret>?p=organize/retentionpolicytags.slab&amp;exsvurl=1</EcpUrl-ret> <EcpUrl-sms>?p=sms/textmessaging.slab&amp;exsvurl=1</EcpUrl-sms> </Protocol> <Protocol> <Type>WEB</Type> <Port>0</Port> <DirectoryPort>0</DirectoryPort> <ReferralPort>0</ReferralPort> <Internal> <OWAUrl AuthenticationMethod="Basic, Fba">https://mail.LOCALDOMAIN.net/owa/</OWAUrl> <Protocol> <Type>EXCH</Type> <ASUrl>https://www.DOMAINNAME.net/ews/exchange.asmx</ASUrl> </Protocol> </Internal> <External> <OWAUrl AuthenticationMethod="Fba">https://www.DOMAINNAME.net/owa/</OWAUrl> <Protocol> <Type>EXPR</Type> <ASUrl>https://mail.DOMAINNAME.info/ews/exchange.asmx</ASUrl> </Protocol> </External> </Protocol> </Account> </Response> </Autodiscover> Autodiscover settings for Outlook Anywhere are being validated. ExRCA validated the Outlook Anywhere Autodiscover settings. Attempting to resolve the host name www.DOMAINNAME.net in DNS. The host name resolved successfully. Additional Details IP addresses returned: xxx.xxx.xxx.xxx Testing TCP port 443 on host www.DOMAINNAME.net to ensure it's listening and open. The port was opened successfully. Testing the SSL certificate to make sure it's valid. The certificate passed all validation requirements. Test Steps Validating the certificate name. The certificate name was validated successfully. Additional Details Host name www.DOMAINNAME.net was found in the Certificate Subject Common name. Certificate trust is being validated. The test passed with some warnings encountered. Please expand the additional details. Additional Details ExRCA can only validate the certificate chain using the Root Certificate Update functionality from Windows Update. Your certificate may not be trusted on Windows if the "Update Root Certificates" feature isn't enabled. Testing the certificate date to confirm the certificate is valid. Date validation passed. The certificate hasn't expired. Additional Details The certificate is valid. NotBefore = 2/5/2010 3:52:07 PM, NotAfter = 2/5/2013 3:52:07 PM Checking the IIS configuration for client certificate authentication. Client certificate authentication wasn't detected. Additional Details Accept/Require Client Certificates isn't configured. Testing HTTP Authentication Methods for URL https://www.DOMAINNAME.net/rpc/rpcproxy.dll. The HTTP authentication methods are correct. Additional Details ExRCA found all expected authentication methods and no disallowed methods. Methods found: Negotiate, NTLM Testing SSL mutual authentication with the RPC proxy server. Mutual authentication was verified successfully. Additional Details Certificate common name www.DOMAINNAME.net matches msstd:www.DOMAINNAME.net. Attempting to ping RPC proxy www.DOMAINNAME.net. RPC Proxy was pinged successfully. Additional Details Completed with HTTP status 200 - OK Attempting to ping RPC endpoint 6001 (Exchange Information Store) on server MAIL.LOCALDOMAIN.net. The endpoint was pinged successfully. Additional Details RPC Status Ok (0) returned in 855 ms. Testing the Name Service Provider Interface (NSPI) on the Exchange Mailbox server. The NSPI interface was tested successfully. Test Steps Attempting to ping RPC endpoint 6004 (NSPI Proxy Interface) on server MAIL.LOCALDOMAIN.net. The endpoint was pinged successfully. Additional Details RPC Status Ok (0) returned in 918 ms. Testing NSPI "Check Name" for user user@DOMAINNAME.net against server MAIL.LOCALDOMAIN.net. The test passed with some warnings encountered. Please expand the additional details. Tell me more about this issue and how to resolve it Additional Details NspiBind returned ecNotSupported. This typically indicates that your server requires RPC encryption. ExRCA will attempt the NSPI test again with encryption. Testing NSPI "Check Name" for user user@DOMAINNAME.net against server MAIL.LOCALDOMAIN.net. Check Name succeeded. Additional Details DisplayName: Firstname Lastname, LegDN: /o=DOMAINNAME/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=Firstname Lastname Testing the Referral service on the Exchange Mailbox server. The Referral service was tested successfully. Test Steps Attempting to ping RPC endpoint 6002 (Referral Interface) on server MAIL.LOCALDOMAIN.net. The endpoint was pinged successfully. Additional Details RPC Status Ok (0) returned in 918 ms. Attempting to perform referral for user /o=DOMAINNAME/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=Firstname Lastname on server MAIL.LOCALDOMAIN.net. ExRCA successfully got the referral. Additional Details The server returned by the Referral service: MAIL.LOCALDOMAIN.net Testing the Exchange Information Store on the Mailbox server. ExRCA successfully tested the Information Store. Test Steps Attempting to ping RPC endpoint 6001 (Exchange Information Store) on server MAIL.LOCALDOMAIN.net. The endpoint was pinged successfully. Additional Details RPC Status Ok (0) returned in 74 ms. Attempting to log on to the Exchange Information Store. ExRCA successfully logged on to the Information Store.

Please describe the exchange topology Please check the external URL of the WEB virtual directories, see if it’s using “DOMAINNAME.info” instead of “DOMAINNAME.net” Get-WebServicesVirtualDirectory | Fl James Luo TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Thanks for the reply. We have one Exchange 2010 server and two DC's. Below are my results from the command you recommended. Thanks again for helping me with this! RunspaceId : 2514244f-f2e3-4d98-a00c-903180918ac7 CertificateAuthentication : InternalNLBBypassUrl : https://mail/ews/exchange.asmx GzipLevel : High Name : EWS (Default Web Site) InternalAuthenticationMethods : {Ntlm, WindowsIntegrated, WSSecurity} ExternalAuthenticationMethods : {Ntlm, WindowsIntegrated, WSSecurity} LiveIdSpNegoAuthentication : False WSSecurityAuthentication : True LiveIdBasicAuthentication : False BasicAuthentication : False DigestAuthentication : False WindowsAuthentication : True MetabasePath : IIS://MAIL.LOCALDOMAIN.net/W3SVC/1/ROOT/EWS Path : C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\exchweb\EWS ExtendedProtectionTokenChecking : None ExtendedProtectionFlags : {} ExtendedProtectionSPNList : {} Server : MAIL InternalUrl : https://www.DOMAINNAME.net/ews/exchange.asmx ExternalUrl : https://mail.DOMAINNAME.info/ews/exchange.asmx AdminDisplayName : ExchangeVersion : 0.10 (14.0.100.0) DistinguishedName : CN=EWS (Default Web Site),CN=HTTP,CN=Protocols,CN=MAIL,CN=Servers,CN=Exchange Adminis trative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=DOMAINNAME,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=LOCALDOMAIN,DC=net Identity : MAIL\EWS (Default Web Site) Guid : 8b9b6200-fa08-46d5-a1f0-cae983249df1 ObjectCategory : LOCALDOMAIN.net/Configuration/Schema/ms-Exch-Web-Services-Virtual-Directory ObjectClass : {top, msExchVirtualDirectory, msExchWebServicesVirtualDirectory} WhenChanged : 11/18/2010 5:23:37 PM WhenCreated : 2/3/2010 1:23:41 PM WhenChangedUTC : 11/19/2010 12:23:37 AM WhenCreatedUTC : 2/3/2010 8:23:41 PM OrganizationId : OriginatingServer : WIGGUM.LOCALDOMAIN.net IsValid : True

Glad to help. So, the test report returns correct URL after you changed “ExternalUrl” to .net, right?Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

To be honest I'm not really sure how to do this. Can it be done through the GUI or do I need to use a command line? Sorry, still teaching myself Exchange.

Please refer to the article below to run the cmdlet via EMS (Exchange Management Shell) Set-WebServicesVirtualDirectory For example: Set-WebServicesVirtualDirectory -Identity MAIL\EWS(default Web site)-ExternalUrl https://www.DOMAINNAME.net/EWS/exchange.asmxPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

How's the issue currently? Any further information?Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

My apologies, I didn't get a chance to try this Friday. However, I did do it today and got this running the above command again. RunspaceId : 13abe390-6b42-4368-9e9f-1eda30d230c8 CertificateAuthentication : InternalNLBBypassUrl : https://mail/ews/exchange.asmx GzipLevel : High Name : EWS (Default Web Site) InternalAuthenticationMethods : {Ntlm, WindowsIntegrated, WSSecurity} ExternalAuthenticationMethods : {Ntlm, WindowsIntegrated, WSSecurity} LiveIdSpNegoAuthentication : False WSSecurityAuthentication : True LiveIdBasicAuthentication : False BasicAuthentication : False DigestAuthentication : False WindowsAuthentication : True MetabasePath : IIS://MAIL.ntsrv5.net/W3SVC/1/ROOT/EWS Path : C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\exchweb\EWS ExtendedProtectionTokenChecking : None ExtendedProtectionFlags : {} ExtendedProtectionSPNList : {} Server : MAIL InternalUrl : https://www.EXTERNALDOMAIN.net/ews/exchange.asmx ExternalUrl : https://www.EXTERNALDOMAIN.net/EWS/exchange.asmx AdminDisplayName : ExchangeVersion : 0.10 (14.0.100.0) DistinguishedName : CN=EWS (Default Web Site),CN=HTTP,CN=Protocols,CN=MAIL,CN=Servers,CN=Exchange Adminis trative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=EXTERNALDOMAIN,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=ntsrv5,DC=net Identity : MAIL\EWS (Default Web Site) Guid : 8b9b6200-fa08-46d5-a1f0-cae983249df1 ObjectCategory : INTERNALDOMAIN.net/Configuration/Schema/ms-Exch-Web-Services-Virtual-Directory ObjectClass : {top, msExchVirtualDirectory, msExchWebServicesVirtualDirectory} WhenChanged : 1/17/2011 8:42:13 AM WhenCreated : 2/3/2010 1:23:41 PM WhenChangedUTC : 1/17/2011 3:42:13 PM WhenCreatedUTC : 2/3/2010 8:23:41 PM OrganizationId : OriginatingServer : 2kdc.INTERNALDOMAIN.net IsValid : True So it did fix that part of things, however, when I run the RPC/HTTS test on the Exchange Connectivity Web Site I was still getting the same results. I ran iisreset and then Outlook Anywhere was dead. I then ran the instructions here: http://social.technet.microsoft.com/Forums/en-US/exchangesvradmin/thread/8b01fb32-5781-4d45-a2a4-2926956749f6/ , that seems to have fixed it up, I still get a few warnings when I run the test (shown below in bold) but I'm not sure they're anything to worry about. Testing RPC/HTTP connectivity. The RPC/HTTP test completed successfully. Test Steps ExRCA is attempting to test Autodiscover for username@EXTDOMAIN.net. Autodiscover was tested successfully. Test Steps Attempting each method of contacting the Autodiscover service. The Autodiscover service was tested successfully. Test Steps Attempting to test potential Autodiscover URL https://EXTDOMAIN.net/AutoDiscover/AutoDiscover.xml Testing of the Autodiscover URL was successful. Test Steps Attempting to resolve the host name EXTDOMAIN.net in DNS. The host name resolved successfully. Additional Details IP addresses returned: EXT IP Testing TCP port 443 on host EXTDOMAIN.net to ensure it's listening and open. The port was opened successfully. Testing the SSL certificate to make sure it's valid. The certificate passed all validation requirements. Test Steps Validating the certificate name. The certificate name was validated successfully. Additional Details Host name EXTDOMAIN.net was found in the Certificate Subject Alternative Name entry. Certificate trust is being validated. The test passed with some warnings encountered. Please expand the additional details. Additional Details ExRCA can only validate the certificate chain using the Root Certificate Update functionality from Windows Update. Your certificate may not be trusted on Windows if the "Update Root Certificates" feature isn't enabled. Testing the certificate date to confirm the certificate is valid. Date validation passed. The certificate hasn't expired. Additional Details The certificate is valid. NotBefore = 2/5/2010 3:52:07 PM, NotAfter = 2/5/2013 3:52:07 PM Checking the IIS configuration for client certificate authentication. Client certificate authentication wasn't detected. Additional Details Accept/Require Client Certificates isn't configured. Attempting to send an Autodiscover POST request to potential Autodiscover URLs. ExRCA successfully retrieved Autodiscover settings by sending an Autodiscover POST. Test Steps ExRCA is attempting to retrieve an XML Autodiscover response from URL https://EXTDOMAIN.net/AutoDiscover/AutoDiscover.xml for user username@EXTDOMAIN.net. The Autodiscover XML response was successfully retrieved. Additional Details Autodiscover Account Settings XML response: <?xml version="1.0"?> <Autodiscover xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006"> <Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a"> <User> <DisplayName>User Name</DisplayName> <LegacyDN>/o=EXTDOMAIN/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=User Name</LegacyDN> <DeploymentId>efe839ab-f1c0-4e89-8a7a-340bad173a50</DeploymentId> </User> <Account> <AccountType>email</AccountType> <Action>settings</Action> <Protocol> <Type>EXCH</Type> <Server>MAIL.INTDOMAIN.net</Server> <ServerDN>/o=EXTDOMAIN/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=MAIL</ServerDN> <ServerVersion>738180DA</ServerVersion> <MdbDN>/o=EXTDOMAIN/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=MAIL/cn=Microsoft Private MDB</MdbDN> <ASUrl>https://www.EXTDOMAIN.net/ews/exchange.asmx</ASUrl> <OOFUrl>https://www.EXTDOMAIN.net/ews/exchange.asmx</OOFUrl> <OABUrl>https://www.EXTDOMAIN.net/oab/4b125621-f119-4ee4-92ef-cc033646c9ac/</OABUrl> <UMUrl>https://www.EXTDOMAIN.net/ews/UM2007Legacy.asmx</UMUrl> <Port>0</Port> <DirectoryPort>0</DirectoryPort> <ReferralPort>0</ReferralPort> <PublicFolderServer>MAIL.INTDOMAIN.net</PublicFolderServer> <AD>2kdc.INTDOMAIN.net</AD> <EwsUrl>https://www.EXTDOMAIN.net/ews/exchange.asmx</EwsUrl> <EcpUrl>https://mail.INTDOMAIN.net/ecp/</EcpUrl> <EcpUrl-um>?p=customize/voicemail.aspx&amp;exsvurl=1</EcpUrl-um> <EcpUrl-aggr>?p=personalsettings/EmailSubscriptions.slab&amp;exsvurl=1</EcpUrl-aggr> <EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?exsvurl=1&amp;IsOWA=&lt;IsOWA&gt;&amp;MsgID=&lt;MsgID&gt;&amp;Mbx=&lt;Mbx&gt;</EcpUrl-mt> <EcpUrl-ret>?p=organize/retentionpolicytags.slab&amp;exsvurl=1</EcpUrl-ret> <EcpUrl-sms>?p=sms/textmessaging.slab&amp;exsvurl=1</EcpUrl-sms> </Protocol> <Protocol> <Type>EXPR</Type> <Server>www.EXTDOMAIN.net</Server> <ASUrl>https://www.EXTDOMAIN.net/ews/exchange.asmx</ASUrl> <OOFUrl>https://www.EXTDOMAIN.net/ews/exchange.asmx</OOFUrl> <OABUrl>https://www.EXTDOMAIN.net/OAB/4b125621-f119-4ee4-92ef-cc033646c9ac/</OABUrl> <UMUrl>https://www.EXTDOMAIN.net/ews/UM2007Legacy.asmx</UMUrl> <Port>0</Port> <DirectoryPort>0</DirectoryPort> <ReferralPort>0</ReferralPort> <SSL>On</SSL> <AuthPackage>Ntlm</AuthPackage> <EwsUrl>https://www.EXTDOMAIN.net/ews/exchange.asmx</EwsUrl> <EcpUrl>https://www.EXTDOMAIN.net/ecp/</EcpUrl> <EcpUrl-um>?p=customize/voicemail.aspx&amp;exsvurl=1</EcpUrl-um> <EcpUrl-aggr>?p=personalsettings/EmailSubscriptions.slab&amp;exsvurl=1</EcpUrl-aggr> <EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?exsvurl=1&amp;IsOWA=&lt;IsOWA&gt;&amp;MsgID=&lt;MsgID&gt;&amp;Mbx=&lt;Mbx&gt;</EcpUrl-mt> <EcpUrl-ret>?p=organize/retentionpolicytags.slab&amp;exsvurl=1</EcpUrl-ret> <EcpUrl-sms>?p=sms/textmessaging.slab&amp;exsvurl=1</EcpUrl-sms> </Protocol> <Protocol> <Type>WEB</Type> <Port>0</Port> <DirectoryPort>0</DirectoryPort> <ReferralPort>0</ReferralPort> <Internal> <OWAUrl AuthenticationMethod="Basic, Fba">https://mail.INTDOMAIN.net/owa/</OWAUrl> <Protocol> <Type>EXCH</Type> <ASUrl>https://www.EXTDOMAIN.net/ews/exchange.asmx</ASUrl> </Protocol> </Internal> <External> <OWAUrl AuthenticationMethod="Fba">https://www.EXTDOMAIN.net/owa/</OWAUrl> <Protocol> <Type>EXPR</Type> <ASUrl>https://www.EXTDOMAIN.net/ews/exchange.asmx</ASUrl> </Protocol> </External> </Protocol> </Account> </Response> </Autodiscover> Autodiscover settings for Outlook Anywhere are being validated. ExRCA validated the Outlook Anywhere Autodiscover settings. Attempting to resolve the host name www.EXTDOMAIN.net in DNS. The host name resolved successfully. Additional Details IP addresses returned: EXT IP Testing TCP port 443 on host www.EXTDOMAIN.net to ensure it's listening and open. The port was opened successfully. Testing the SSL certificate to make sure it's valid. The certificate passed all validation requirements. Test Steps Validating the certificate name. The certificate name was validated successfully. Additional Details Host name www.EXTDOMAIN.net was found in the Certificate Subject Common name. Certificate trust is being validated. The test passed with some warnings encountered. Please expand the additional details. Additional Details ExRCA can only validate the certificate chain using the Root Certificate Update functionality from Windows Update. Your certificate may not be trusted on Windows if the "Update Root Certificates" feature isn't enabled. Testing the certificate date to confirm the certificate is valid. Date validation passed. The certificate hasn't expired. Additional Details The certificate is valid. NotBefore = 2/5/2010 3:52:07 PM, NotAfter = 2/5/2013 3:52:07 PM Checking the IIS configuration for client certificate authentication. Client certificate authentication wasn't detected. Additional Details Accept/Require Client Certificates isn't configured. Testing HTTP Authentication Methods for URL https://www.EXTDOMAIN.net/rpc/rpcproxy.dll. The HTTP authentication methods are correct. Additional Details ExRCA found all expected authentication methods and no disallowed methods. Methods found: Negotiate, NTLM Testing SSL mutual authentication with the RPC proxy server. Mutual authentication was verified successfully. Additional Details Certificate common name www.EXTDOMAIN.net matches msstd:www.EXTDOMAIN.net. Attempting to ping RPC proxy www.EXTDOMAIN.net. RPC Proxy was pinged successfully. Additional Details Completed with HTTP status 200 - OK Attempting to ping RPC endpoint 6001 (Exchange Information Store) on server MAIL.INTDOMAIN.net. The endpoint was pinged successfully. Additional Details RPC Status Ok (0) returned in 405 ms. Testing the Name Service Provider Interface (NSPI) on the Exchange Mailbox server. The NSPI interface was tested successfully. Test Steps Attempting to ping RPC endpoint 6004 (NSPI Proxy Interface) on server MAIL.INTDOMAIN.net. The endpoint was pinged successfully. Additional Details RPC Status Ok (0) returned in 294 ms. Testing NSPI "Check Name" for user username@EXTDOMAIN.net against server MAIL.INTDOMAIN.net. The test passed with some warnings encountered. Please expand the additional details. Tell me more about this issue and how to resolve it Additional Details NspiBind returned ecNotSupported. This typically indicates that your server requires RPC encryption. ExRCA will attempt the NSPI test again with encryption. Testing NSPI "Check Name" for user username@EXTDOMAIN.net against server MAIL.INTDOMAIN.net. Check Name succeeded. Additional Details DisplayName: User Name, LegDN: /o=EXTDOMAIN/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=User Name Testing the Referral service on the Exchange Mailbox server. The Referral service was tested successfully. Test Steps Attempting to ping RPC endpoint 6002 (Referral Interface) on server MAIL.INTDOMAIN.net. The endpoint was pinged successfully. Additional Details RPC Status Ok (0) returned in 915 ms. Attempting to perform referral for user /o=EXTDOMAIN/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=User Name on server MAIL.INTDOMAIN.net. ExRCA successfully got the referral. Additional Details The server returned by the Referral service: MAIL.INTDOMAIN.net Testing the Exchange Information Store on the Mailbox server. ExRCA successfully tested the Information Store. Test Steps Attempting to ping RPC endpoint 6001 (Exchange Information Store) on server MAIL.INTDOMAIN.net. The endpoint was pinged successfully. Additional Details RPC Status Ok (0) returned in 93 ms. Attempting to log on to the Exchange Information Store. ExRCA successfully logged on to the Information Store. If those are anything to worry about please let me know. Otherwise, thank you very much for your help!