Software

We had a very simmilar problem when we went from groupwise to exchange 2000. I don't remember exactly what we did but here are a few things to look at. First, try to add the server in the host file. Second, make sure your dns server has all the correct IP addresses and non of the old ones. Third, try to do a continues ping to the server and open outlook when that is running. I believe it's just a matter of getting the name resolved to the IP address.

To give you a little more background info:

The exchange server \\company2 is also the authentication server (Active Directory).

In addition, we are using WINS and the new server (company2) is listed there. The client is getting the correctWINS server address from DHCP. (I know, I know... DNS is installed, but we haven't upgraded the clients yet!)

I can go \\company2 and get the shares in under a second. I can also map shares, ping, and open webpages on the same server. However,Outlook Web Access, Outlook, and the old Exchange clients all have that same mailbox opening problem, even during or after the above.

*sigh*

Did I miss something? I know there is no "make it faster" checkbox, but a tech can dream, right?

E2K is a resource hog -- much more than 5.5. Since OWA as well as outlook is slow, it suggests an issue with the server. (Though configuring DNS on 9x clients may help) MS recommends against installing E2K on your authentication server, but it ispossible (and practical with small networks and tight budgets.) But you might want to consider installing or moving the information store to a separate drive as the OS. You may also think about throwing more hardware at it. Check the performance monitor to see where your bottlenecks are. Other than that, you may look at your indexing configuration. (Turn off full indexing if you don't absolutely need it!)

A few things to look at.

HTH...

Point value changed by question poster.

This question was closed by the author