Check names - Outlook 2003

  • Thread starter Thread starter Adispi
  • Start date Start date
A

Adispi

Hello
If some of our workers type a wrong name in the two field of a new message
and than click on check names, Outlook is blocking for up to 30 seconds.
Sometimes even the message pops up, that the connection to the Ms Exchange
Server has been lost.
Other users, including me, do not experience the problems but the
installation is the same.
We have an Exchange Server 2003 and Office 2003.
Thanks for your help
 
Not enough information... for example, everyone have the same type of
network connection (e.g. wired, wireless, .etc) to Exchange? Is everyone in
cached mode? Is everyone connecting the same way (e.g. TCP or RPC/HTTPS)?

Hello
If some of our workers type a wrong name in the two field of a new message
and than click on check names, Outlook is blocking for up to 30 seconds.
Sometimes even the message pops up, that the connection to the Ms Exchange
Server has been lost.
Other users, including me, do not experience the problems but the
installation is the same.
We have an Exchange Server 2003 and Office 2003.
Thanks for your help
 
Everyone has the same type of network connection (wired). There are a few
users (Laptop) who use the cached mode but the most of them do not use the
cached mode. The two stations (users) I am comparing to find out the mistake
do not use the cached mode. I activated the cached mode once in both
profiles, but the behavior was the same. Also, both machines are in the same
subnet. Outlook is updated correctly and identically on both stations.
Exchange Server is also up to date and does not show any related warnings or
errors. Additionally, both clients have the same add-ins. Any hints?
 
Anything in the event logs of the workstation to indicate an issue with the
network card, dhcp lease renewal, .etc?


Everyone has the same type of network connection (wired). There are a few
users (Laptop) who use the cached mode but the most of them do not use the
cached mode. The two stations (users) I am comparing to find out the mistake
do not use the cached mode. I activated the cached mode once in both
profiles, but the behavior was the same. Also, both machines are in the same
subnet. Outlook is updated correctly and identically on both stations.
Exchange Server is also up to date and does not show any related warnings or
errors. Additionally, both clients have the same add-ins. Any hints?
 
I think that I found the bottleneck. Some of the users have an additional
addressbook attached. One of those addressbooks has over 20'000 contacts.
Once I connect this addressbook, also my outlook has a long time until I
receive a result. If I disconnect this addressbook, the name resolution works
perfectly fine.
 
Back
Top