Discussion Locked

Some client cant open Exchnge Info Store

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Running Exchange 5.5 on a Windows 2000 pure Active Directory environment. Clients are Windows 2000 Pro. using Outlook 2000. System has been up and running just fine for nearly 2 years. Recently, some users log in on their workstations to access their exchange outlook email. Error message indicates that Exchange server cannot be accessed, and information store cannot be opened. Normally this would indicate a DNS resolution problem, IP problem, or exchange server service problem. DNS info is correct and has not been changed recently. The IP information is correct, workstations in question CAN ping DNS servers and the exchange server, also, can ping using the host name. So IP and name resolution is ruled out. users can still use domain and other network resources, outlook web still functions for them. please note that other users are still using outlook/exchange normally without any problems whatsoever. this problem is happening to a handful and are in the minority. There are no errors in the error logs, neither on the server, nor on the workstations. the problem virtually doesn't exist! yet these staff members can't open their mailboxes. looking on support pages has yielded no solutions but the typical problems (the things i listedabove).

absolutely out of ideas and energy. any help or point in the right direction would be most appreciated.

5 replies

by tim.mills

Have you contacted Microsoft, I am sure that there are issues with name resolution when using Exchange 5.5

by mike

That doesn't look like it. The problem is the actual SERVER name can't be resolved as an exchange host from a few PCs. This seemed to have "just stopped working", more specificly, nothing of major consequence was done at or around that time that could explain this. Also, it continues to work just fine for all the other clients. this problem is happening only to a handful of clients.

by mike

It turned out that reinstalling TCP/IP services on these machines work. It looks like corrupted registry data was the culprit.

This discussion is closed to new replies.