Brian M
asked on
Outlook 2013 Cannot display folder, on public folders only
Everyone in the building at least once a day gets a cannot display folder message when clicking on a random public folder. We use Exchange 2013, outlook 2013 and MAPI for out connections. If they shut down and restart Outlook they can get to the folder.
Not sure what is going on, we use a DAG with two servers, one at primary site, the other over a L2 WAN, both servers are on the same vlan (spanned across the WAN).
Issue started immediately upon bringing the second CAS server online, prior to establishing the DAG.
Not sure what is going on, we use a DAG with two servers, one at primary site, the other over a L2 WAN, both servers are on the same vlan (spanned across the WAN).
Issue started immediately upon bringing the second CAS server online, prior to establishing the DAG.
make sure Your auth and url settings are identical for you CAS servers, especially MAPI, RPC and EWS Virtual directory
ASKER
For EWS internal url is the CNO for the DAG, external url is (server1.mail.org and server2.mail.org) - examples used.
For Mapi no external url is set, and the internal urls are (server1.mail.org/mapi and server2.mail.org/mapi) - examples used.
So the internal urls for Mapi and external urls for everything else are set to the server specific FQDN.
For Mapi no external url is set, and the internal urls are (server1.mail.org/mapi and server2.mail.org/mapi) - examples used.
So the internal urls for Mapi and external urls for everything else are set to the server specific FQDN.
you should use a single namespace for all services and not (!) use the DAG name or IP for anything.
ASKER
So how do I get one url with the same FQDN to point to both servers?
I see in most examples that people use the same url for both internal and external, should I create a CNAME for both servers and let round robin DNS do the work? Then set each url, both external and internal identically?
Thank you.
I see in most examples that people use the same url for both internal and external, should I create a CNAME for both servers and let round robin DNS do the work? Then set each url, both external and internal identically?
Thank you.
ASKER
I am looking at using Round robin dns for both external and internal, and having all urls, both external and internal be identical, does this sound like a solution?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Ok, setting this up now, thanks for the input, I'll be back.
Great ---- good luck !
ASKER
I made the changes and checked by turning off one of my exchange servers, after a minute timeout all services reconnected automatically. Not sure if this will fix my public folder issue, but has solved my redundancy problems, all urls (both internal and external) are now using the same name in dns, and the round robin is working. I will keep an eye out for the public folder issue, but I think I am good.
Thank you so much for your help!
Thank you so much for your help!
ASKER
Very clear and concise, easy to follow directions worked like a charm!
great -- good luck
ASKER
It looks like its been a few weeks without any problems, I am guessing this fix really did the trick, thank you again.