Exchange going really slow - outlook exclamation mark!

We have exchange 2003 running on server 2003 R2 across two sites, one domain. Was running fine until last week when people started getting "outlook is trying to contact exchange server" exlamation error. CPU was fine as was memory. We defraged just in case overnight but still no difference.
Then, by coincidence, we had to reboot our DC for the site. (which is also the GC). Immediately exchange recovered and was lighting fast. Since then we still get slowdowns, but these are immediatly resolved by rebooting the DC. Error logs don't seem to show anything untoward and now at a loss to explain/fix it..................
LVL 1
davelongmanAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

greesh_hemCommented:
Try to run a DCDiag on the exchange server with the switch

DCdiag /s:Servername

where Servername would be the NETBios name of your domain controller and try to look at the diagnostics to see if you find any failures.

Also try to take a network trace since there is a good possibility that the network packets may be getting dropped.
0
davelongmanAuthor Commented:
Dcdiag passed all tests - file attached.

What's the best way to take a network trace please?

Thanks,
dcdiag.txt
0
greesh_hemCommented:
Install Netmon on one of the Outlook client machine and then run it from there.

http://blogs.technet.com/netmon/
0
davelongmanAuthor Commented:
Thanks greesh hem, we didn't see packet loss so ran exchange tech assistant. This has shown RPC delays and also a disk bottleneck occuring (we believe due to MAPI clients increasing over time). I am going to install a new scsi drive and move the transaction logs over so hopefully this will resolve the situation. I am confused as to why booting the GC improved matters, but I think it may be because exchange then temporarily stops the processing that was hammering the disk access and then once it found the backup GC it started to slow down again.

Thanks for your help in at least proving it local to the exchange server itself, even though initial diags looked like a DC/AD problem.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.