"Cannot Load Information Store"

For some reason I am the only one on our networking experencing problems when loading Outlook 2000.  We currently are running Exchange 5.5.  Every time I go to load Outlook 2k it gives me "retry/work offline".  Sometimes after hitting retry a couple times it finally loads my email's and is awfully slow then normal.  I did a repair/reinstallation of Office 2000 and still the same problem is arising.. Has anyone ever had this problem before?  Any help would be greatly appreciated..

Thanks in advance..
ccostanzo78Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

VinceACommented:
Could be one of a couple of problems:

- If you're using TCP/IP take a look at these MS KB articles:
http://support.microsoft.com/support/kb/articles/q152/2/34.asp
http://support.microsoft.com/support/kb/articles/q155/0/48.asp

You can also get these articles by sending an E-mail with a subject of "Q152234 Q155048" (without the quotes) to mshelp@microsoft.com.

- You could have an RPC binding order problem. Take a look at this registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\Exchange Provider\RPC_Binding_Order

Move the token that represents the protocol that you're using to the front
of the pile. Occasionally I've found that the protocol that gets used isn't
always the one you think, so if it doesn't work right the first time try
reordering the protocols again.

However, many problems with slow client startup can be attributed to incorrectly configured TCP/IP stacks. Check the clients domain name. Is it the same as the servers? Is it the correct domain name? If it's incorrect, fix it. If it's correct but different to the server's, add the server's domain name to the "Domain Name Suffix Search Order." If all else fails, try adding a HOSTS file to the client.
0
slang9Commented:
We experienced this on our small network. we solved it by putting data into the C:\Windows\hosts file on the IP address and name of the exchange server. The system will look there first insted of looking to your DNS server for the location of the Exchange server. ON NT the file is C:\winnt\system32\drivers\etc\lmhosts
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Outlook

From novice to tech pro — start learning today.