Clients Outlook is slow

You don't mention what service pack you are running either for NT or for Exchange. I'm assuming you are running an Exchange 5.5 server. If so, I'd recommend upgrading NT to service pack 6a & Exchange to service pack 4. SP4 of Exchange 5.5 resolved a problem our company had w/ the Internet Mail Connector locking up every so often.

We had a similar issue and we had to change the order of the transport protocols in the registry of the clients. The clients were going through the entire list until it got to tcp/ip, then it connected.

What virus scanner are you using? I found when I upgraded my network to MyCIO by mcafee all my outllok clients slowed considably. To fix look for a "Trusted Cab Fix" on their web site. Run the program on all your clients, and the problem should stop.

For the Outlook Client slow response there have some points to check:
1.This very unlikely to be the reason:
The can be virus shield scanning process in progress. (That you get no choice, have to take it or take away the virus shield)

2. Thisshould be main reason:
A.As the relationship between MS Exchange Server (email server) and the Outlook client (email client) there are design as client/server structure, using the remote procedure call (RPC) to communicate betweeb client and server via network.

B.If you network segment is jam at the network partition during a lot of users open the outlook at sametime will slow.

C.Or the old and new network mix around also can make the network collison traffic.

D.To isolate this, you may change new network card for a few client and the server. And connect this few client machine and server machine to different segment(may be can alone itself).

E.Try to open the outlook see how the response. If OK, lift the new network inside the machine and connect this group of machine back original network segement. And open Outlook try again.

F. From here you can switch between the test procedure to find out the actual result.

Hope this will be help.

Thomas NG

Have you looked at if your mail server is registering correctly in WINS database.

This could be a WINS issue.

Hi,

i think the outlook client is still trying to recolve the exchange server name via DNS. Sometimes when this not functions properly outlooks seems to hang. Even if you have wins configured on the client side, when DNS is configured outlook takes the DNS resoulution, when the first DNS entry not functions then it tooks the second one, most time over WAN (So Outlook seems to hang !).

OK what could you do to speed up the things:
1.) Look if you have Problems with DNS namesrresolution.
2.) It speeds up the client connection, if you manually add the Exchange adress to host and Lmhost files. The name is then in the netbiosnames Chache table of the client, and outlook bursts on opening.

Hope it helps

Frobo

I experienced this same problem when our WINs database became corrupted. The easiest way to remove corruption is to stop your WINs servers service, remove the contents of c:\winnt\system32\wins folder, and restart WINs so that it can rebuild its database. It is best to do this after hours so that clients can reregister on startup. Else they may experience browser problems for a few minutes.

This question was closed by the author