Tony -
We just completed the switch. We're just a small site (single exchange server).
I'd like to see a summary of any private responses you get!
Biggest problem we've had has been with the new improved Outlook Web Access. Users
have had problems with it being EXTREMELY slow. Slow as in 2-3 minutes to open from a
dial-up connection. Even worse with AOL connections. Here's our short
troubleshooting list for OWA:
1. Make sure user has IE version 6 (some versions of 5.5 seem to just get "stuck")
2. Make sure user does NOT have IE content advisor enabled
3. For XP users, the user must put domainname\username in the username box
(we haven't gotten the "default" domain name to work in this instance and
XP won't show the "domain" field on the login)
This is actually good for all users to start using!
4. Remember that AOL sucks. Since AOL dialup doesn't use TCP/IP, each packet from a
dialup user must be encapsulated inside an AOL packet, which is then "unpacked" at the
AOL system before it hits the internet. When a packet comes back from your server to
the client, AOL encapsulates the packet from the Internet and then delivers it to the
dialup system (which unpacks it and passes it back to the client browser). The
IMPORTANT part of this is the fact that when a packet is encapsulated it might not fit
into a single AOL packet [most of the time it won't] so you end up sending twice the
number of packets. So a user dialing into Earthlink at 28.8 might take 10-15 seconds
to open an OWA session, but same user dialing into AOL at 28.8 might take 20-30
seconds!
Actual times for FIRST session with AOL for us is about 2 minutes, SECOND session
takes 30 seconds because of the cached graphics.
5. Remembering that dialup is slow to begin with, make sure you don't have your SSL
key set to 4096 bit length. This will really slow down your users.
-----Original Message-----
From: EXTERN Hlabse Tony (Tek Systems;RBNA/CIT1)
[mailto:[EMAIL PROTECTED]]
Sent: Tuesday, September 10, 2002 3:23 PM
To: Exchange Discussions
Subject: Common Exchange 2000 problems
After a company has moved and installed Exchange 2000, not including any of
the migration, upgrade or installation problems. What are the most common
problems you Exchange Admins have to deal with. With 5.5, IS store failure
and having a good knowledge of disaster recovery are top on my list. Any
common area one should be aware of and have knowledge. Just curious.
Tony Hlabse
Exchange Administrator
574-237-5726
Robert Bosch Corporation
_________________________________________________________________
List posting FAQ: http://www.swinc.com/resource/exch_faq.htm
Archives: http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin: [EMAIL PROTECTED]
_________________________________________________________________
List posting FAQ: http://www.swinc.com/resource/exch_faq.htm
Archives: http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin: [EMAIL PROTECTED]