Outlook clients trying to connect

Current Exchange Server: 8.3.389.2 - 2007 SP3 update roll-up 15
We are seeing an issue with Outlook clients trying to connect anywhere from 1 minute to 20 minutes plus. We have Outlook 2010 and Outlook 2013 in the environment. All clients are up to date with the latest Microsoft Updates.
The issue will happen to multiple users and the same users have no issues connecting to web-mail or email on the phone. Its just the outlook client.
Outlook will just hang and sometimes haven't updated for hours or the previous day.
Office 2010 and Office 2013 are both updated.
I've tried disabling our Anti-Virus, turning the policy off and the issue is still present.
Email will update on phones and web-mail.
We've tried rebuilding profiles, repairing Office and nothing seems to fix the issue.
Any help or suggestions would be appreciated.

Hi,
According to your description, I understand that Outlook client sometimes hang or can't auto sync mailbox, however ActiveSync and OWA works fine.
If I misunderstand you concern, please do not hesitate to let know.
I want to double confirm whether all Outlook client experience this question at same time or not, how about restart Outlook client while problem arise.
If so, please open Event log to collect relevant warning or error message for further troubleshooting. Meanwhile, please run ExBPA to test Exchange server.
On the contrary, this may be related to client side. Please try to run Outlook with safe mode to prevent virus and add-ins, or enable Cache mode.
Besides, uncheck “Download Shared Folder” for testing.
Best Regards,
Allen Wang

Similar Messages

Exchange 2010 - Outlook Anywhere trying to connect to internal server name first before connecting to proxy server

Hello,
I have an Exchange 2010 question which I will post in the Exchange 2013 section since the Ask a question button in the legacy Exchange Servers section of technet takes me back to the part of Technet where I can only ask questions regarding Exchange 2013.
If someone can point me to a part where I can place a question in an Exchange 2010 forum please let me know.
We have Exchange 2010 setup with a CAS array listening to outlook.internaldomain.com
We have TMG 2010 setup with a rule for Outlook Anywhere, the rule listens to mail.externaldomain.com and traffic that meets this rule is let through to outlook.internaldomain.com.
When I fire up my laptop, which is connected to the internet, and start Outlook and let it configure my profile through autodiscover it sets it up correct and fills the Outlook profile with a servername stating outlook.internaldomain.com and a proxyserver
to be used stating mail.externaldomain.com. After initial setup when my Outlook starts it almost immediatly prompts me for a username and a password so this is working fine.
At the office we have an internal network segment where DHCP is servicing the connecting clients and giving them our internal DNS servers because they need connection to some other network segments which are not available to the internet. This network segment
does not have access to our internal Exchange environment but has full access to the internet. Clients in this network segment do want to use Outlook so using Outlook Anywhere for them is the logical way to go. When I connect my laptop to this network segment
I get handed an IP address and our internal DNS servers, when I start Outlook it takes about two minutes before a the credential prompt pops up and another 2 to 6 minutes after entering credentials before it says all folders are in sync. This is quite long
and our clients find this unacceptable.
I started testing what might be going on here and I have found that when I manually enter external DNS servers the Outlook password prompt will popup in seconds and all is working as expected so it seems Outlook is trying to connect to the internal servername
when using our internal DNS servers (which can resolve outlook.internalnetwork.com) instead of directly going to the proxy server which is to be used for Outlook Anywhere.
When I start a network monitor trace my thoughts are confirmed because when I am connected to the internal network segment OUTLOOK.EXE first tries to connect to outlook.internaldomain.com, it almost immediately gets a response stating that this route is
inaccessible but OUTLOOK.EXE keeps on trying to connect untill some sort of time out is reached (somewhere around two minutes) after which it connects to mail.externaldomain.com and Outlook shows the credential prompt.
So to round it up, when connected to DNS servers that can resolve the internal servername Outlook tries to connect to the internal servername in stead of the external name, Outlook does not reckognize the answer from the network that the internal route is
not acessible (or it does but does nothing with this information).
Has anybody experienced this behaviour in Outlook?
Does anyone have a solution in where I can force Outlook to connect to it's proxyserver and disregard the internal servername?

Thank you for your reply.
The client computers that are experiencing the issues are not domain joined, the only reason I can think of why this is occurring is because the DNS servers are able to resolve the internal hostname of the server, but I would expect Outlook to always use
the proxy server that has been set in the configuration of the Outlook profile. Or at least acknowledging the answer that the initially tried route is inaccessible and immediately continue to the proxy server.
For setting the same hostname for internal and external use, we use different namespaces internally and externally, do you mean setting the external hostname on the CAS array for internal use ? Wouldn't that push all internal communication to the internet
and to the outside interface of the TMG where the server is published with that hostname ?

Outlook disonnected / trying to connect/ server lost connection

Dear friends,
On my exchange 2010 i am now getting this error frequently on most of the client computers where outlook looses the connection and hosws outlook is trying to connect and in few cases it shows disconnected and then i have to close the browser and start the
app again.. this is becoming big issue now .. Can some one please advise why this is happening and how can i resolve the same.
MARK AS USEFUL/ANSWER IF IT DID
Thanks
Happiness Always
Jatin

Hi,
Does the issue happen to all users, internal users or external users? What about OWA? Does it still work?
If OWA can work normally, please try to use ping to test both the Exchange Server FQDN and the IP address of the Exchange Server.
If OWA cannot work either, please collect some Event logs or error message/code
for further troubleshooting.
Additionally, here is a related KB that may be helpful:
Outlook connection issues with Exchange 2010 mailboxes because of the RPC encryption requirement
http://support.microsoft.com/kb/2006508
Thanks,
Winnie Liang
TechNet Community Support

Outlook client can't connect in but OWA works

You need to make sure your OutlookAnywhere and AutoDiscover settings are setup properly along with Split-DNS. OutlookAnywhere and Split-DNS are vital for future-proofing your Exchange configuration and making it work properly now, regardless if you use Exchange 2007, 2010, or 2013. For Exchange 2013, OutlookAnywhere is a requirement and Split-DNS is Best Practice. If you are on Exchange 2007 or 2010, and you do not have OutlookAnywhere enabled, enable OutlookAnywhere and follow this guide.You should always use NTLM over Basic authentication, as Basic sends the username and password in the clear, and NTLM is Windows Authentication. On Exchange 2013, you also have a new option called Negotiate, which is recommended. As you follow this guide, you will set the ClientAuthenticationMethod (Internal and External if on Exchange 2013) to NTLM...

Outlook client can't connect in configured outlook on workstation but OWA works.
This topic first appeared in the Spiceworks Community

CRM 2015 outlook client does not connect to CRM

Hi,
I am trying to run the configuration wizard to connect the office 2010 outlook to Dynamics CRM 2015 server and get the error below (outlook client 2015 is successfully installed). All the required components
are installed on both server and client side.
Any idea?
captainsina

Hi Nico,
How is it going? :)
I am going against on-prem. Not being prompted for credentials. I can go to the services using the browser, but the outlook client fails.
I am using the same credentials on the local machine as the CRM user credentials.
Cheers.
captainsina

External outlook clients can't connect to Exchange 2013

Currently running server 2012 r2 and exchange 2013 sp1...
Internally everything works fine, clients can also connect externally to owa/ecp. However when using an outlook client they are unable to connect. This is my first experience with exchange 2013 so I am at a loss. What steps should I be following to get this
working properly? Or if anyone has some suggestions to get more information I can do that as well.
Thanks!
Connecting from a mobile-phone using mail.mail.com works fine.
We are using a self-signed certificate for testing purposes..

Testing Outlook connectivity.
The Outlook connectivity test failed.
Additional Details
Elapsed Time: 941 ms.
Test Steps
Testing RPC over HTTP connectivity to server mail.mail.com
RPC over HTTP connectivity failed.
Additional Details
Elapsed Time: 941 ms.
Test Steps
Attempting to resolve the host name mail.mail.com in DNS.
The host name resolved successfully.
Additional Details
IP addresses returned: xxx.xxx.xx.x
Elapsed Time: 535 ms.
Testing TCP port 443 on host mail.mail.com to ensure it's listening and open.
The port was opened successfully.
Additional Details
Elapsed Time: 176 ms.
Testing the SSL certificate to make sure it's valid.
The SSL certificate failed one or more certificate validation checks.
Additional Details
Elapsed Time: 229 ms.
Test Steps
The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server mail.mail.com on port 443.
The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
Additional Details
Remote Certificate Subject: CN=mail.mail.com, Issuer: CN=mail.mail.com.
Elapsed Time: 154 ms.
Validating the certificate name.
The certificate name was validated successfully.
Additional Details
Host name mail.mail.com was found in the Certificate Subject Common name.
Elapsed Time: 0 ms.
Certificate trust is being validated.
Certificate trust validation failed.
Test Steps
The Microsoft Connectivity Analyzer is attempting to build certificate chains for certificate CN=mail.mail.com
A certificate chain couldn't be constructed for the certificate.
Tell me more about this issue and how to resolve it
Additional Details
The certificate chain didn't end in a trusted root. Root = CN=mail.mail.com
Elapsed Time: 33 ms.

Unrecognized certificate when Outlook 2010 tries to connect to Exchange 2007 on SBS 2008

Hi all,
I believe this is a security issue rather than a connectivity or configuration problem.
Running Outlook 2010 on Windows 7 trying to connect to Exchange 2007 on SBS 2008, I receive the following error:
"The name of the security certificate is invalid or does not match the name of the site"
When I view the certificate I see that it was issued to "zx-server" by "zx". This is NOT my domain CA nor is it a certificate I recognize. I use a self-issued certificate (i.e. issued by the SBS box). I also receive this certificate error when I browse to
the internal website (companyweb). No other computers on the network are seeing this behaviour.
I have checked the certificate stores in certmgr and I can't find any such certificate or CA. I have also searched the entire hard drive with no luck. I have run Kaspersky AV, Malwarebytes and MS Security Essentials several times but I can't find any malware.
I also recently installed Comodo Firewall (the problem began after this).
I need to find and remove the certificate and prevent it from being presented to me every time I try to connect to the server. All help, advice and suggestions appreciated.
Aide

Hi,
It’s really a common issue.
This issue occurs if the following conditions are true:
You replace the default self-signed Exchange Server 2007 or Exchange Server 2010 certificate with a different certificate.
Note The Setup program in Exchange Server 2007 or in Exchange Server 2010 creates a default self-signed certificate when Exchange Server 2007 or Exchange Server 2010 is installed.
The common name on the replacement certificate does not match the fully qualified domain name (FQDN) of the URL that is stored in the following objects:
o
The Service Connection Point object for the Autodiscover service
o
The
InternalUrl attribute of Exchange 2007 Web Service (EWS)
o
The
InternalUrl attribute of the Offline Address Book Web service
o
The
InternalUrl attribute of the Exchange unified messaging (UM) Web service
By default, the URL that is stored in these objects references the NetBIOS name of the server. For example, a URL that resembles the
following URL is stored:
https://NetBIOS_name.contoso.com/autodiscover/autodiscover.xml
This may differ from the host name that is used in the FQDN of the replacement certificate. For example, the replacement certificate
may have an FQDN that resembles the following FQDN:
mail.contoso.com
This issue causes a name mismatch error to occur. Therefore, you receive the security warning message when you try to connect Outlook
2007 to the mailbox.
For more detailed information about the procedures to fix the issue, please refer to the following KB article:
Title: Security warning when you start Outlook 2007 and then connect to a mailbox
that is hosted on a server that is running Exchange Server 2007 or Exchange Server 2010: "The name of the security certificate is invalid or does not match the name of the site"
URL:
http://support.microsoft.com/kb/940726
Regards,
James
James Xiong
TechNet Community Support

Outlook 2013 trying to connect

Hi all,
lately we been experiencing that some users Outlook takes some minutes before it success Connection to Exchange (2013),At bottom right corner of Outlook it says trying to Connect and will freeze/hang if try to click or mark another folder.Most of the times
it Connects after 2-3 minutes.It started this week and for other users there are no issues at all.When try to add share mailboxes it also take 2-3 minutes after you hit ok.Both Windows (8 and 8.1) and Outlook (2013) have latest updates.
Network Department said they have implemented teredo,but that shouldnt be the cause of problem.
Any ideas?
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Off2work

Hi,
yes we also tried to setup New profile and it also hangs on last stage at finding server.After 2-3 minutes it fine,but when try to add shared mailboxes it hangs for 2-3 min each mailbox we try to add.Those shared mailboxes varies from 100mb to 5gb.
When check Connection status it says connecting and type is Exchange mail.So i Guess it hangs for each time it try to Connect to shared mailboxes.
On server all Resources are fine,disk Space is good,no event log,no Queue.
Even test-mapiconnection it has good response time.We are still on CU3,since have heard some issue With CU5 and waiting.Again this have been working fine until this week.No updates have been done at all on those servers (2 Exchange 2013,with CAS and mailbox
on each).
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Off2work

Outlook clients unable to connect to Exchange / Windows user profile

Exchange 2010
Outlook 2010/2013
I've seen a dozen or so computers in the last few weeks with this problem. The user suddenly cannot connect to the Exchange server in Outlook. (Sorry, I don't have specific error messages for this part.)
If I try a repair on the Email account or try to create a new Mail profile, I get this error:
"The action cannot be completed. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action."
I have verified all Exchange and mail security settings. Outlook configuration is not the problem.
I tried deleting %appdata%\microsoft\outlook and %localappdata%\microsoft\outlook.
I tried a repair on Microsoft Office.
I tried creating a new Mail profile for a different email account.
The only thing that has fixed this problem is a completely new Windows user profile, which tells me there is something else broken in the user profile. Does anyone have any idea what it might be?
Blog /
Twitter

Hi,
Please try to access Exchange via OWA.
This issue may occur when the HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders registry key does not contain all of the required data. Specifically, these problems occur if the AppData string value is missing from this
registry key.
To resolve this issue, import the User Shell Folders registry key from a working Windows User Profile.
Steps to perform on a working computer
Start Registry Editor. Click Start , type regedit in the Search programs and files box, and then press Enter.
Locate and then select the following registry subkey: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders
On the File menu, click Export.
Specify the name of the .reg file and then click Save.
Copy the .reg file to the computer exibiting this problem.
Close Registry Editor.
Steps to perform on the computer displaying the above error(s)
Start Registry Editor.
On the File menu click Import.
Locate and select the .reg file exported from the working computer.
Click Open.
Close Registry Editor.
Best Regards.

Outlook client in different subnet unable to connect to Exchange 2010 CAS using Windows 2008 R2 NLB multicast mode

Hi all,
need urgent assistance on the following issue
this is my Exchange 2010 setup
2 x CAS/Hub servers with HP network teaming, and load balanced using Windows NLB multicast mode. There are 2 VIPs on the NLB, one for outlook anywhere, one for autodiscover
2 DNS records were created for the 2 VIPs
Clients use Outlook Anywhere (HTTPS) to connect to the CAS servers from external segment via a Palo Alto firewall, which also acts as a layer 3 router
static arp was set on the Palo Alto firewall, with both virtual MACs pointing to the primary virtual MAC used by the NLB.
Observations
1. within same segment - no issue accessing Exchange servers, even when one CAS node is offline
2. external segment (via firewall)
a. when both nodes are up
outlook client able to connect to Exchange CAS VIP on 443, but will disconnect after around 30 seconds. Client will retry and the pattern will repeat
Exchange CAS RPC logs shows client connections and disconnections to the outlook anywhere VIP address
Firewall logs shows allowed traffic from client to the VIPs
unable to complete profile creation
b. with only CAS2 (CAS1 stopped/deleted from NLB cluster)
no issues accessing Exchange servers, creating profiles etc
c. with only CAS1
same behaviour as (a)
reinstalled NLB, but doesn't resolve
deleted CAS1 from NLB cluster, and re-add. issue remain
Q1. is teaming supported? Teaming is currently set to automatic mode, instead of specified Fault Tolerant
Q2. are there additional settings we need to set or verify on the Palo Alto firewall, since the issue only happen to external segment? Thanks!

Yes - I've been scarred with this for many years :(
If it is just CAS 1 that is causing issues, then focus in on that. The support statement for Win 2008 R2 is that NLB is still a 3rd party component and support may ask for it to be disabled.
http://support.microsoft.com/kb/278431
Does CAS1 and CAS2 have the same NICs (firmware as well), driver, teaming software, and teaming config?
I also want to ask what the network team did for configuring the switch ports on the servers? This will vary from vendor to vendor - did they do the same config on both?
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter:   LinkedIn:
  Facebook:
  XING:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.
Thanks Rhoderick, issue still persists
can you also help clarify what you meant by "configuring the switch ports on the servers"?
thanks again

Outlook clients periodically trying to connect to hard-coded autodiscover links ...

Hello,
We have an different internal and external domain names, e.g., company.local and company.com respectively. All our users have both @company.local and @company.com e-mail addresses but @company.com is the
primary SMTP address. We have two AD sites, s1 and s2. Our SCP records appear to be fine and point to autodiscover-s1.company.local and autodiscover-s2.company.local and we have DNS entries for them.
For various reasons, we use a first-time logon script with Redemption Profman to create the Outlook profile with a specific name. It works fine, the profile is created the first time the user logs on.
However, if we scan the firewall logs, we see that *some* clients are periodically trying to connect to "autodiscover.company.com" as well as autodiscover-s1/s2.company.local and we can't understand why. We don't have DNS entries for "autodiscover.company.com".
Strangely, the clients appear to work fine, the users don't complain about anything.
Presumably, that comes from the right-hand side of the user's email address. Can anyone explain why Outlook is doing that for users on domain-joined PCs?
We migrated from Exchange 2003; we have Exchange 2010 latest SP/RU and Outlook 2010 with latest patches too. The issue affects Outlook 2011 Mac users too.
If we use the autodiscover instead of the logon script, it does create a working profile. The Test Configuration in Outlook doesn't show any problems either or mention autodiscover.company.com. This problem seems to happen when Outlook uses autodiscover
to connect periodically and scan for changes (the "outlook layer" and "MAPI layer" in the documentation). Repairing or re-creating the profiles doesn't change anything.
Thanks in advance for any suggestions,
- Alan.

This is the order of autodiscover search in outlook
1. Try to access DC to get the autodiscover scp
2. Local DNS to locate autodiscover.emaildomain.com
3. Local XML
4. SRV record
If the user is not joined to domain or out of domain network outlook will search for
https://domain.com/autodiscover/autodiscover.xml
https://autodiscover.domain.com/autodiscover/autodiscover.xml
May be you might have mentioned external DNS in your PCs or it may be logs of external user access
MAS

Internal outlook client connectivity in exchange 2010 when coexist with exchange 2013

Hi all ,
on my side i would like to clarify few queries.
Say for instance i am coexisting exchange 2010 with exchange 2013 .Unfortunately if all of my exchange 2013 servers goes down .
Q1 .On that time will the internal outlook users having their mailboxes on exchange 2010 can be able to connect mailboxes without any issues ? In case if they face any issues what kind of issues will they be? Because why i am asking is we should have pointed
the autodiscover service to exchange 2013 during coexistence.
When an user closes and reopens the outlook after whole exchange 2013 environment failure ,outlook will first query the autodiscover service for the profile changes to get it updated on users outlook profile.In such case autodiscover service will not be
reachable and i wanted to know will that affects the internal client connectivity for outlook users having their mailboxes on exchange 2010.
Q2. Apart from outlook internal users connectivity ,what kind of exchange services(i.e owa,active sync,pop,external OA and imap) will get affected when whole exchange 2013 environment goes down during coexistence ?
I have read the below mentioned statement on this awesome blog but still i wanted to clarify with you all on my scenario.
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx<o:p></o:p>
Internal Outlook Connectivity
For internal Outlook clients using RPC/TCP connectivity whose mailboxes exist on Exchange 2010, they will still connect to the Exchange 2010 RPC Client Access array endpoint.
For internal Outlook clients using RPC/TCP connectivity whose mailboxes exist on Exchange 2007, they will still connect directly to the Exchange 2007 Mailbox server instance hosting the mailbox.
Please share me your suggestions and that would help me a lot .
Regards
S.Nithyanandham

Hi Winnie Liang ,
Thanks a lot for your reply.
Scenario 1 : for internal outlook connectivity
We have below settings for exchange 2010 autodiscover.
mail.domain.com - will be the namespace for internal autodiscover URI for all the exchange 2010 cas serves
We are going to have below settings for exchange 2013 autodiscover.
mail.domain.com - will be the namespace for internal autodiscover URI for all the exchange 2013 cas serves
During coexistence mail.domain.com will be pointed to exchange 2013 cas servers . I mean to say if we try to resolve the mail.domain.com it will get resolved in to the exchange 2013 cas servers.
So on such case if anything happened wrong to the new environment or else if entire environment goes down .Do we face any issues while outlook users connect to existing mailboxes in exchange 2010 ?
Because why i am asking is ,on the below mentioned article i have read all the autodiscover request will go via exchange 2013 cas servers during coexistence.That means all the existing mailboxes in exchange 2010 will also have to query exchange 2013 cas
servers for autodiscover request.During the whole exchange 2013 environemnt failure whenever the user tries to close and open outlook .Outlook will first queries the autodiscover service for any changes happened on that particular mailbox and it will try to
get it updated on user profile.
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
Would it be possible to make the exchange 2010 mailbox users to query only the scp points which belongs to the exchange 2010 cas servers for autodiscover request ?
Scenario 2: For exchange services
mail.domain.com - will be the namespace for all the exchange 2010 services (i.e owa,activesync,external outlook anywhere,pop,imap)
mail.domain.com - will be the namespace for all the exchange 2013 services (i.e owa,activesync,external outlook anywhere,pop,imap)
What about the above services will it get affected during whole exchange 2013 environment failure ?
Note : We are not facing this issue , i hope everything goes well in my environment while doing coexistence i am just asking this question on my own interest?
Regards
S.Nithyanandham
Thanks S.Nithyanandham

Why does Outlook 2010/2013 tries to connect by rpc over http in LAN?

Hi All,
I have Exchange 2010 (Two CAS) Published by TMG (Basic Authentication). Also outlook anywhere is configured with Basic Authentication.
Some users have issues with "authentication prompt" (randomly). By the way, Outlook Clients(2007/2010/2013) are fully updated.
What I can see when "authentication prompt" shows up, Outlook tries to connect by rpc over https.
Is this a normal behavior?
Regards
Jo

Hi,
Firstly, I'd like to say, basic authentication requires user name and password. Thus, it's an expected behavior that credential will prompt once when users login Outlook with basic authentication.
Additionally, I'd like to confirm how you confirm it's Outlook Anywhere when the credential prompts. Based on my knowledge, the credential issue may be caused by connectivity issue and we can confirm the connection method through the tool "connection status".
Thus, I'd like to confirm if the connection is established when the credential issue happens.
Press ctrl and right click Outlook icon>connection status>status, protocol
Thanks,
Angela Shi
TechNet Community Support

Exchange 2013 Outlook Client connectivity

I'm migrating from Exchange 2010 to Exchange 2013 and on the final stages. I pointed the external and internal DNS records to Exchange 2013. I moved one mailbox to Exchange 2013 and then tried to create a new Outlook client profile and bring the mailbox
up however the client would not connect. It stated trying to connect encrypted and unencrypted. It did not work. I checked nslookup and the IPs are all set pointing to Exchange 2013. I then checked my certificates. I have a certificate that is a wild card.
When I checked assigned services on my wild card it had IIS and SMTP assigned. Also in IIS on the default site bindings what should you use as a certificate on the two https settings? Originally they were the local generated certificate. I changed them to
the wild card no luck. Please assist.

Try running through this and see if it gives you some ideas on what is wrong:
https://testconnectivity.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

Outlook clients are connecting to different site public folder rather than same site public folder on exchange 2010

Team,
users are unable to expand public folder from outlook, but they are able to navigate through outlook web access.
noticed the outlook connections are connected to other child domain PF server rather than local site public folder server.
due to this issue, users are unable to navigate to pf's , by restarting RPC Client access service , now users are able to connect to local public folder servers.
all the databases are pointed to local pf database. all the settings looks good.
any suggestions would be appreciated.
Regards
Srinivasa K
Srinivasa K

Hi Srinivasa,
How about OWA?
If it works in OWA, it seems an issue on the Outlook client side.
I suggest run Outlook under safe mode to avoid some AVs and add-ins.
I also suggest make sure the Outlook client has the latest patch.
Also try to re-install Outlook.
Thanks
Mavis
Mavis Huang
TechNet Community Support

Outlook clients trying to connect

Similar Messages

Maybe you are looking for