Hey everybody,

We are currently having problems with clients that are on another domain, than the Exchange server, to connect to the public folders and auto reply service.

Our current setup:

-We have 1 domain with multiple small sites (let's say Domain1) where the Exchange2013 server is connected to and the vast majority of the users are situated on.

-We have a second domain (let's say Domain2) with a few clients using outlook.
The clients on Domain2 can connect to outlook with outlook anywhere.
Both domains have their own domain controller and these domains are not joined.

These 2 domains are connected through a VPN network just like all the other sites.

The clients that are connected with outlook on Domain1 can use the auto reply service and can see the public folders. To verify this I can see the RPC/HTTP with the public folder in the outlook connection status.

The clients that are connected with outlook on Domain2 can't use the auto reply service ("Your automatic reply settings cannot be displayed because the server is currently unavailable. Try again later") or see the public folders.
In the outlook connection status there is no connection to public folders.

I have been searching far and wide on google, but have yet to find a situation where someone had this problem with 2 separate domains using the same Exchange server.

So any help or suggestions are more than welcome!

With regards,

Ken T.

Is Domain2 in the same forest?  Did you run setup /PrepareDomain in Domain2 or setup /PrepareAllDomains in Domain1?

Hi,

Does the issue occurs on OWA ?

On your server side, please run the following command to check your autodiscover and webserivices:
Get-ClientAccessServer | FL Identity,AutodiscoverServiceInternalUri

Get-WebServicesVirtualDirectory | fl Identity,name,*url*,*auth*

In addiction,we can do an Outlook connectivity test with https://testconnectivity.microsoft.com/   and see what went wrong.

Regards,

David

Hey Ed,

The 2 domains have separate forests and we did not run the /PrepareDomain setup on the second domain.

Is is necessary for the 2 domains to be joined together for the auto discovery to work?

With regards,

Ken

Hey David,

OWA is working perfectly fine. I can do everything on OWA that I can't do in outlook.

-Get-ClientAccessServer | FL Identity,AutodiscoverServiceInternalUri:

Identity                       : EXSERVER
AutoDiscoverServiceInternalUri : https://ExServer.domain1.be/Autodiscover/Autodiscover.xml

-Get-WebServicesVirtualDirectory | fl Identity,name,*url*,*auth*

Identity                      : EXSERVER\EWS (Default Web Site)
Name                          : EWS (Default Web Site)
InternalNLBBypassUrl          :
InternalUrl                   : https://ExServer.domain1.be/EWS/Exchange.asmx
ExternalUrl                   : https://mail.domain1.be/EWS/Exchange.asmx
CertificateAuthentication     :
InternalAuthenticationMethods : {Ntlm, WindowsIntegrated, WSSecurity, OAuth}
ExternalAuthenticationMethods : {Ntlm, WindowsIntegrated, WSSecurity, OAuth}
LiveIdNegotiateAuthentication :
WSSecurityAuthentication      : True
LiveIdBasicAuthentication     : False
BasicAuthentication           : False
DigestAuthentication          : False
WindowsAuthentication         : True
OAuthAuthentication           : True
AdfsAuthentication            : False

The ExternalUrl won't work at this moment because we are still in the process of getting our certificate.
(I'm strongly guessing that the external auto discovery is gonna resolve this issue)

I'll run some tests with the Outlook connectivity test tomorrow.

With regards,

Ken

We never did manage to find a solution for this problem.

But we now have a public SSL certificate instead of a self signed, and the second domain can do everything using that certificate.

• Marked as answer by Ken Thomassen 23 hours 13 minutes ago