Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1126
  • Last Modified:

Outlook 2007 on RDS frequently loses connection to Exchange 2013

Hi there,

we have a bit of a situation at one of our clients.
Case is as follows:

Exchange 2013 server on windows 2012 R2, RDS on an other Windows 2012 R2 with outlook 2007 (client couldn't afford to replace Office as well at this time).

Exchange is migrated from exchange 2007 on a Windows 2003 server.

All mailbox have been migrated and after a few weeks we removed the exchange 2007 from the coexistance.
And that's when the problems started.

No day later after we moved the Public folders to exchange 2013, recreated some connectors and de-install exchange 2007, we are getting calls from the users that that outlook is repeatedly telling that the connection to exchange was lost and and recreated. Ofcourse when they try to send an e-mail and the connection gets lost the mail gets stuck in the out-box untill outlook reconnects.

Accourding to the event logs on the remote desktop server, the connection losing and reconnecting occurse ever 2 or 3 minutes. And stops when most people go home at the end of the day. Ofcourse it starts in the morning again.

So. What we already know:

- Users are opening multiple mailboxes (their own + shared mailboxes)
- We can't turn on cache mode cause it's not supported on outlook 2007 in RDS. We tried a registry tweak to enable it anyway, but that didnt work
- We notice that one outlook session makes a lot of RPC over HTTP connections (6 for a single mailbox, 24 for someone using multiple mailboxes).

Strangest thing is. We didn't have the problem when the exchange 2007 server was still up but not in use. All outlook 2007 were already connecting through the http/rpc connection via the new exchange 2013/iis apppool.

So... what to do.

I know we can force the client to buy office 2013 for all users (VLK license) but since Outlook 2007, Exchange 2013 should work together, I am wondering if there is any limit we can tweak so there are less reconnections.

Hope someone can help.
0
Joost
Asked:
Joost
  • 3
  • 3
2 Solutions
 
it_saigeDeveloperCommented:
Open Exchange Powershell and check your outlook anwhere settings.

Get-OutlookAnywhere

I am willing to bet that you do not have Negotiate set in your IISAuthenticationMethods, ExternalClientAuthenticationMethod or InternalClientAuthenticationMethod settings.

Try setting this with:

Get-OutlookAnywhere –Server (hostname) | Set-OutlookAnywhere -InternalClientAuthenticationMethod Negotiate -InternalClientsRequireSsl $true -ExternalClientAuthenticationMethod Negotiate -ExternalClientsRequireSsl $true -IISAuthenticationMethods NTLM,Basic,Negotiate

Dont forget to run an iisreset when finished.

-saige-
0
 
JoostAuthor Commented:
IISAuthenticationMethods, ExternalClientAuthenticationMethod or InternalClientAuthenticationMethod settings, were set to "NTLM".

So you were right about it not having Negotiate.

I've changed the settings. So tomorrow morning I will hopefully see improvement.

I noticed that the RPC/HTTP settings in Outlook automatically were set to NTLM authentication. Should I also change them to Negotiate?
0
 
it_saigeDeveloperCommented:
That was going to be my next question.  Yes, set them to negotiate as well.
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
JoostAuthor Commented:
Thanks for the tip. To bad. This morning after a few users had logged in on the Remote Desktop server the Application Event ID 26 were popping up again and users were getting the same connection messages from outlook.

On an other forum I was reading something about Outlook using public folders for "ready/busy" status and such. Not that it directy had anything to do with my problem I started a search on the new Exchange 2013 server and noticed that de "publicfolder mailbox" that was created during the migration from exchange 2007, still was in "HoldforMigration" status.

Since the company never used the PF, nobody noticed that the whole public folder wasn't accessible. One google search lead me to a tip to recreate the PF-mailbox.

Since it wasn't containing any information I removed it with the Exchange 2013 Admin Center. And created a new one.
At the exact moment the new PF was created and I could access it with outlook on the RDS. The event 26 stopped !!!

So, it turned out to be a public folder issue. Some how during the transition from the public folders in exchange 2007 to 2013 something went wrong.
0
 
it_saigeDeveloperCommented:
Glad to hear that you got the issue resolved.
0
 
JoostAuthor Commented:
Saige helped me a lot in directing me to the right path. Though it turned out to be an other problem that we stumbled upon while looking for settings that could help.
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now