Exchange Server - Unable to open mailbox in MS Outlook client
Asked By chris
13-Sep-07 05:04 PM
All,
I have a user with a problem where she cannot open her Exchange 2003 mailbox
using Microsoft Outlook 2003 or 2000. She is getting the error:
unable to open your default e-mail folders. the Microsoft exchange server
computer is not available. either there are network problems or the microsoft
exchange server computer is down for maintenance.
The server is definitely up and running. I have her using OWA for now. I
initially thought it was an Outlook issue on her machine, since I could
connect to her mailbox logged on as the administrator on my laptop, but when
I logged onto my laptop with her acct, I get the same error. Its definitely
something with her AD account. But the wierd thing is its only for OUtlook
profiles, not OWA
I thought maybe the RPC client registry values were missing but they were
there.
I check her AD acct but I dont see anything different on her acct. I know
you can disable OWA, POP, IMAP but there's nothing to disable MAPI profile
access.
Has anyone seen this problem before? Luckily, she can get to mail through
OWA but users prefer the full client. Any help is appreciated.
Outlook 2003
(1)
Outlook
(1)
PSTs
(1)
Registry
(1)
Profiles
(1)
Firewall
(1)
Wierd
(1)
Brick
(1)
Ed Crowley [MVP] replied...
Did you check name resolution (DNS and WINS) and the personal firewall
settings on the client machine?
--
Ed Crowley
MVP - Exchange
Cannot add mailboxes to Outlook 2003 clients Exchange Server We are running Exchange 2003 and Outlook 2003. When I attempt to add a mailbox to a users Outlook 2003, I get the following error: The name could not be resolved. The action could not tried KB322832 to no avail. Any help would be greatly appreciated. Thanks! Exchange Clients Discussions Outlook 2003 (1) PSTs (1) Mailboxes (1) Brick (1) DNS (1) Check DNS settings on the
Outlook 2003 clients are not able to connect Exchange Server my outlook 2003 clients are not able to connect with cas & hub. Exchange Miscellaneous Discussions Outlook 2003 (1) Report (1) PSTs (1) Brick (1) Thanks for the status report. - - Ed Crowley MVP - Exchange keywords: Outlook, 2003, clients, are, not, able, to, connect description: my outlook 2003 clients are not able
Exchange 2003 & Outlook 2003 Exchange Server Hi all, we have Windows server 2003 environment setup; whenever a user sends / invites a meeting request through outlook the error "The following recipient could not be reached: "name, email account does not exist aware. Can anyone help with this error appearing when the meeting requests are initiated? Server 2003 SP2 Exchange 6.5 build 7638.2 SP2 Is there an advanced way i can search for users in AD to make sure they dont exist? Exchange Admin Discussions Outlook 2003 (1) PSTs (1) PublicDelegates (1) AltRecipient (1) Windows (1) Serverside (1) Mailboxes (1) Delegates (1
Exchange 2003 + Outlook 2003 message stuck in Outbox for 5 / 6 secon Exchange Server . . . then go in the sent still remain. Any idea? Thank you Exchange Admin Discussions Windows XP (1) Microsoft Exchange (1) Outlook 2003 (1) PSTs (1) SPs (1) U9rat3tlb9495v44mpijoi4sal41gt5nb3 (1) Dj24t35j05il662d9emptv0umhkrd8ql08 (1) Stefano (1) A 5-to-6-second delay mailto:melvin.mcphucknuckle@getronics.com mailto:melvin.mcphucknuckle@pinkroccade.com When you select another folder Outlook refreshes its view of the mailbox. It does the same thing when that UDP packet expected, or go with the exceptions now :P http: / / support.microsoft.com / kb / 839226 Added Outlook.exe in the Exception list. Thanks. keywords: Exchange, 2003, +, Outlook, 2003, message, stuck, in, Outbox
Exchange 2007 and Outlook 2003 Exchange Server Hi, I would like to know if it is good to use Outlook 2003 on an Exchange server 2007. How are the behaviors ? Does someone has experimented troubles with this kind of mix ? Thanks JC.Q Exchange Clients Discussions Outlook 2003 (1) PSTs (1) B6B8614E3711 (1) Jcquirin (1) Brick (1) Eoc (1) OOF (1) I've used Outlook 2003 clients against Exchange 2007 without issue. Outlook 2003 clients obviously won't have access