Outlook crisis post update/reboot

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.
mediatechnicaAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

David Johnson, CD, MVPOwnerCommented:
Try restarting your exchange services as shown in this post http://forums.msexchange.org/m_30795900/mpage_1/key_/tm.htm#1800536445
0
mediatechnicaAuthor Commented:
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

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
mediatechnicaAuthor Commented:
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
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server OS

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.