Solved

Outlook crisis post update/reboot

Posted on 2012-03-14
3
269 Views
Last Modified: 2012-08-13
Hello Experts,

I am in a crisis.  Last night I performed regular updates on my Exchange server (2010) and was forced to reboot.

I also rebooted the BESX server , which happens to be one of two DCs and one of 3 DNS servers.

The DC's are server 2008 and the third DNS is Server 2003.  The2k3 box is the OLD DC but is still not totally ready for removal as all services are not fully migrated.

After reboot, I tested mail flow and confirmed it was working.  I also tested the admin account using Outlook.

Now all 40 plus users are having issues connecting to Exchange.  All Outlook clients get the same error:  0x8004011d .  

In order to get them back up, I had to recreate all Outlook profiles and NOT attach the profile to any other mailboxes but the user's own.  (there is ALOT of mailbox sharing as some users are assistants to other users)

No mailbox can connect to another mailbox even though the permissions are set in sharing in Outlook.

PFDAVAdmin does not work and I am pretty weak in Powershell.

I have checked DNS by pinging the mail server by name from random machines and all machines can find the mail server.

OWA works as does Active Sync and I believe all users in BESX.

I am very baffled and need much guidance.

Thank you in advance for any and all help.
0
Comment
Question by:mediatechnica
  • 2
3 Comments
 
LVL 78

Expert Comment

by:David Johnson, CD, MVP
Comment Utility
Try restarting your exchange services as shown in this post http://forums.msexchange.org/m_30795900/mpage_1/key_/tm.htm#1800536445
0
 

Accepted Solution

by:
mediatechnica earned 0 total points
Comment Utility
I believe the issue has been resolved.

Oddly, the Exchange server was ping-able by name, but nslookup could not resolve.

Checking DNS on all DNS servers, there was NO record of the Exchange server.  Adding A record to DNS and commands ipconfig /flushdns and ipconfig /registerdns on all machines resolved the Outlook mailbox connection issue.

Now my concern is "why did DNS "lose" the Exchange server?"

Thanks for reading and answering anyways.
0
 

Author Closing Comment

by:mediatechnica
Comment Utility
Further troubleshooting with the help of a second IT person led to the missing DNS record discovery.

As stated in previous post, as soon as DNS entries were made for Exchange server and DNS flushed and re-registered, all outlook connectivity issues were cleared up.
0

Featured Post

Do You Know the 4 Main Threat Actor Types?

Do you know the main threat actor types? Most attackers fall into one of four categories, each with their own favored tactics, techniques, and procedures.

Join & Write a Comment

Follow this checklist to learn more about the 15 things you should never include in an email signature from personal quotes, animated gifs and out-of-date marketing content.
Marketers need statistics and metrics like everybody else needs oxygen. In this article we explain how to enable marketing campaign statistics for Microsoft Exchange mail.
This tutorial will walk an individual through locating and launching the BEUtility application to properly change the service account username and\or password in situation where it may be necessary or where the password has been inadvertently change…
This tutorial will walk an individual through configuring a drive on a Windows Server 2008 to perform shadow copies in order to quickly recover deleted files and folders. Click on Start and then select Computer to view the available drives on the se…

771 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

12 Experts available now in Live!

Get 1:1 Help Now