We have a SBS2003 installation with 15 work stations connected and allworkstations are running XP PRO with the latest updates and service packs.(The system is a SBS 2003 SP2, Exchange server 2003 SP2.)The installation has been working fine for a little over a year when due to a bad battery in the UPS thebattery dropped out before the server could go into the hibernate mode.Over that weekend the local power company had a localized failure on Saturday and Sunday, when the owner came into the office Saturday afternoon he realized the server was shut down so he restarted it.Unfortunately the same thing happened on Sunday.When I powered up the server on Monday everything worked fine except exchange server's pop3 connector.The server booted with an error message that a device driver failed and to check the event viewer. The problem was resolved but when the pop3 dll's loaded and pop3 connector started all of the connections between the outlook installations and exchange no longer work, and outlook shows that it is disconnected.If you try to set up a new instance of outlook, after setting up the exchange server account through control panel, upon starting outlook you get an error message (the connection to Microsoft exchange is unavailable. Outlook must be online or connected to complete this action.), after clicking OK the window for exchange to check names pops up.When you put in a valid name and click OK you get the same error message,OWA however works fine. Any help that can be offered would be greatly appreciated since I am at my wits end with this problem. The Mailbox and public stores are both mounted and all services are running except imap4 which is disabled since we dont use imap. For what it's worth the original installation of SBS 2003 was installed on a 20gb hard drive with exchange server installed on another drive.Approximately 2 months after the server was set up the hard drive the OS was on started giving us problems so it was replaced with a 500gb hard drive.That said, since exchange is giving us problems I have been contemplating trashing the exchange installation on the other drive and installing it on the drive with the OS.I have spent two months fighting with exchange since the power failures and at this point a 357 magnum right between its hard drives is looking pretty good!I welcome any and all suggestions that might help me resolve this issue Thank you hdcameron Just a note: I just went against convention and setup outlook on the server under the administrator login and outlook connects to exchange with no problems.

Hi, I understand that all the Outlook could not access the Exchange server even though OWA was available. Before going on, I would like to explain that the basic process of communication between the client and Exchange Server when configuring the user account on the Outlook. First it resolves the Exchange Server that you inputted via the DNS on the DC (SBS 2003), then bind the Directory Service and Information Store through querying the EPM (135). Actually, based on the last test on the Exchange Server, that can manifest that our issue occurs on the first step. The DNS could not be resolved properly which results in the error message. Thus, I suggest we first check the DNS is functioning properly. Please first confirm the following questions: 1. Can we ping the Exchange sever FQDN/Netbios? 2. Can we ping GCs FQDN/Netbios? 3. How about the ports on Exchange (135) and GC (389, 3268?)? Are they available? Please run the nslookup command on the client in order to check the DNS can be resolved without any issue. http://support.microsoft.com/kb/200525 Thanks Allen