JPTF
asked on
Exchange 2013 Public folder on Outlook
We have a new exchange 2013 installation in production, however the public folders cannot be accessed by any outlook version. The public folders show up under favorites if we enable those in the OWA interface. There (owa) it works fine and then it shows on outlook but only under favorites. When we try to expand the tree it says that it cannot find the server. All the other aspects of exchange are working great. We have autodiscover working and the cellphones working great. I'm really puzzled with this because I've been installed exchange servers for a long time since the 200 version... never had something like this happening.
Any input regarding this odd issue?
BTW, I performed all types of tests and all pass. The exchange connectivity test passes and the outlook setup is automatic. The server is attached to a domain.
Thanks!
Any input regarding this odd issue?
BTW, I performed all types of tests and all pass. The exchange connectivity test passes and the outlook setup is automatic. The server is attached to a domain.
Thanks!
Stelian Stan
Have a look on this KB: http://support.microsoft.com/kb/2839517
Exchange 2013 having lots of bugs. Microsoft released in hurry/burry due to Office 365 integration. Wait for future service packs or RU's.
ASKER
Thanks to both of you! The KB was looked at a while ago and was issued before the CU1 (that we have installed). After the CU1 it allows to see the folder but cannot expand (only outlook) them so it means (to me) that it connects to the server because it shows the correct folders created using OWA, why it doesn't show the contents... I don't know. I regret having accepted to use 2013 . We have several previous versions running without any issues. We checked DNS settings, autodiscover and all types of tests but no luck. Do you guys think it is better to go ahead with sharepoint 2013 instead of worry about having the PFs available? I don't have any experience with sharepoint 2013 but we have it available on the client's account. Thanks
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
Thanks to you all. It is the way to go.
our client decided that he is not willing to get the workers to learn a complex system like sharepoint.
So, I beg for any input regarding this issue because I tried everything from re-checking dns, autodiscover, SSL certificate (it is internally issued because client doesn't need public to access from outside.). Everything test fine. The https://www.testexchangeconnectivity.com/ passed without an error. I am at the point of quitting support for exchange due to the amount of time to find solutions for microsoft lack of care.
Besides the public folder taking long time to open (it shows the created folder on the OWA) we cannot access them because it says the server is not available or is down for maintenance.
I understand that there is authentication for each service but all is connecting fine.....
Please....
our client decided that he is not willing to get the workers to learn a complex system like sharepoint.
So, I beg for any input regarding this issue because I tried everything from re-checking dns, autodiscover, SSL certificate (it is internally issued because client doesn't need public to access from outside.). Everything test fine. The https://www.testexchangeconnectivity.com/ passed without an error. I am at the point of quitting support for exchange due to the amount of time to find solutions for microsoft lack of care.
Besides the public folder taking long time to open (it shows the created folder on the OWA) we cannot access them because it says the server is not available or is down for maintenance.
I understand that there is authentication for each service but all is connecting fine.....
Please....