Outlook Address Book hangs
Hello All,
I've got a screwy one here. I am running an Exchange 2003 server. My clients are running Outlook 2000 and 2003.
Many of my clients have a problem when clicking on there "To" button in a new email or a reply email. Once in a while it just hangs. Now it's not locked up and it's not every time but every so often it will hang trying to open the address book. It takes about 3 to 5 minutes to open it. If they kill Outlook and go back in it will pop right open. This one has really got me stumped.
We've had this problem for quite some time. I even went so far as to build a new Exchange server from scratch and move everything to it and then kill the old Server. Still doing it on the client side. I should mention that this only happens on the WAN machines. All machine that are on the LAN don't have this problem.
Any ideas would be great.
Thanks
Eric
I've got a screwy one here. I am running an Exchange 2003 server. My clients are running Outlook 2000 and 2003.
Many of my clients have a problem when clicking on there "To" button in a new email or a reply email. Once in a while it just hangs. Now it's not locked up and it's not every time but every so often it will hang trying to open the address book. It takes about 3 to 5 minutes to open it. If they kill Outlook and go back in it will pop right open. This one has really got me stumped.
We've had this problem for quite some time. I even went so far as to build a new Exchange server from scratch and move everything to it and then kill the old Server. Still doing it on the client side. I should mention that this only happens on the WAN machines. All machine that are on the LAN don't have this problem.
Any ideas would be great.
Thanks
Eric
ASKER
The WAN is 4 VPN connections back to the main office. As far as the systems are concerned they are 1 hop away from the server.
We actually have domain controllers at each site as well. I configure all of our systems here at the main office and then take them to the WAN buildings. They always work fine at the main office.
I agree that it is something to do with the WAN I'm just not sure what it could be. We don't have problems with anything else. This is the only issue I can see and it's very intermittent. I would say it's fine about 80% of the time.
Thanks
Eric
We actually have domain controllers at each site as well. I configure all of our systems here at the main office and then take them to the WAN buildings. They always work fine at the main office.
I agree that it is something to do with the WAN I'm just not sure what it could be. We don't have problems with anything else. This is the only issue I can see and it's very intermittent. I would say it's fine about 80% of the time.
Thanks
Eric
ASKER
Hmmm,
Well it's been a while but this is still an issue. I think maybe I have it narrowed down a bit. It looks like it could possibly have something to do with the relationship between Exchange, Global Catalog Server and Ldap. The problem is, I'm not sure what the correct way to even tell if there is a problem with these. The Global Catalog Server is Ticked/Enabled on the Primary Domain Controller. Ldap appears to be working and other than this issue Exchange works.
Can somebody point me in the right direction to determine if this is my problem?
Thanks
Eric
Well it's been a while but this is still an issue. I think maybe I have it narrowed down a bit. It looks like it could possibly have something to do with the relationship between Exchange, Global Catalog Server and Ldap. The problem is, I'm not sure what the correct way to even tell if there is a problem with these. The Global Catalog Server is Ticked/Enabled on the Primary Domain Controller. Ldap appears to be working and other than this issue Exchange works.
Can somebody point me in the right direction to determine if this is my problem?
Thanks
Eric
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
VPN, dedicated connection? Something else?
When you are using live data (ie not cached mode) then Outlook is making a connection to the domain controllers. Therefore if the problem has followed to a new server then it has to be something in that area.
Have you tried configuring an laptop, ensuring that it works, then taking it off site to see that it doesn't work?
The WAN connection is the most likely source of the problem.
Simon.
--
If your question has been answered, please remember to accept the answer and close the question.