Fix an AD 2003–Exchange 2000–IMAP Bug
Learn why IMAP users on Active Directory 2003 can't authenticate to Exchange 2000 Server.
by Ben Schorr and Jim McBee
Posted June 15, 2004
I upgraded my domain controllers to Active Directory 2003 and now my Internet Message Access Protocol (IMAP) users can't authenticate to our Exchange 2000 Server. The IMAP log shows this error message:
server version 6.0.6389.0
05/23/2004 11:24:26.527 <<<
(TID:f20): A1 LOGIN "user"
05/23/2004 11:24:26.527 >>>
(TID:1820): A1 NO
The service has not been started.
05/23/2004 11:24:26.527 (TID:f20):
Closing connection to
I think you guys may be my last hope. What do you say?
Marshall, Sydney, Australia
Ben: Offhand I'd say you're in trouble if we're your last hope. That said, have you checked to see that your Exchange Server Information Store is running?
Jim: That's the first thing to check, although if it wasn't running none of your Exchange clients would be working and you didn't mention that. Another thing to check, on the off chance that your IMAP clients are in their own mailbox stores, is that the stores they're in are mounted.
How can I use multiple e-mail addresses with my Outlook Web Access (OWA) clients? In Outlook or Outlook Express, I can specify which account I want to send from and open additional mailboxes. How can I do that with OWA?
Jim: Well, you can't do it the way you're thinking. You can open the separate mailboxes separately by changing the username in the URL for the mailbox, but there isn't any way to select which account you send from.
I have several Outlook 2003 clients trying to connect through a Terminal Services application server. Every time they start Outlook 2003, it crashes. We've tried reinstalling but that doesn't seem to solve the problem. Running Outlook 2003 on our local workstations works fine. Any clues you could throw my way would be great.
Paul, Los Angeles
Ben: My first instinct was to suggest that perhaps cached mode was turned on, but then I remembered that cached mode is disabled in Terminal Services mode. However, I still think there's a good chance that you somehow have Outlook 2003 trying to create files on the local hard drive.
Jim: I had the same thought and I wonder if maybe your profiles have the default data store set to be Personal Folders (PST) files on the C: drive of the terminal server rather than to their Exchange mailboxes where they should be.
Ben: As usual Jim has a good insight on this one. This is another good example of where PST is bad. Despite improvements to 2003 PST files, such as changing them to Unicode format, they're still not the best way for Exchange users to store data in most cases.
Back to top