• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1120
  • Last Modified:

Outlook 2010 and OWA slow to access Exchange 2010, Server 2008

I have recently installed the above environment upgrading from Server/Exchange 2003. The mailboxes connect to the Exchange no problem when setting up Outlook but keep timing out during the day - that message pops up 'Trying to connect to Exchange Server' in the bottom right corner. OWA is also slow and it's nothing to do with ADSL speed - it just says WAITING.  The TS machine's Outlook also crashes too often when using Outlook.  There's 16GB RAM in ther on a Proliant ML370 G6 and is otherwise a speedy machine.  Just seems to be slow authentication issues with the Exchange. The Exch MGNT tool still sees the 2003 server although that machine has gone and all roles seem to have transferred fully. Could the PC's still be looking for the OLD 2003 Exchange? Thanks in advance.
0
ljkal
Asked:
ljkal
  • 3
  • 2
1 Solution
 
Iain MacMillanCommented:
its possible the domain/DC's are still seeing the old server and your clients are still looking to the old server, timing out and then looking for the next SMTP server.  you might want to check your DNS settings/records (inc. reverse PTR's) on your DC(s) to make sure that all MX, Mailhost & OWA entries are all pointing the new server.

have you updated your office GPO settings to point to the new mail server??
are you using Cached Mode??   is everyone now using Outlook 2010 (no older clients)?
what OS is your users on - XP, Vista or 7?

You may need to do a IPCONFIG /flushdns on some systems to clean-up their connectivity.
0
 
ljkalAuthor Commented:
Thanks for this. All the above was fine - it looks like it was the Kaspersky for Exchange. Have disabled it and the mail is now faster. Going to give them 72 (working) hours and will report back!
0
 
Iain MacMillanCommented:
remember AV packages for servers need separate policies/rules so they they do not scan things like Java Installs, Exchange DB's and IIS folders which will cause performance issues.  I think MS did a best practices guide for AV for SQL and Exchange servers, i will see if i can find it.

good to know if it was Kaspersky, as i was considering their corporate package to move to later in the year.
0
 
ljkalAuthor Commented:
Update: It was the Exch KAV.  I've got the same set up running on over a dozen servers all in different offices with no problem on default KAV settings. Looks like a bad install.  Have to take it up with Kaspersky at a future date but Exchange flynig again now!!!
0
 
ljkalAuthor Commented:
Sorted the problem in house.
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

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