• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 427
  • Last Modified:

Autodiscover not working after DC upgrade

Our Network Admin had demoted old 2007 DC and forced new DC (2013) IP address to all servers. Problem 1: CAS servers in the DMZ did not pickup new IP's. Problem 2: Barracuda spam appliance did not pickup new DC IP's. Problem 3: no one can connected with their Outlook client and fails at Autodiscover. The few clients that were previously connected (like myself) are able to still connect.

It seems this DNS change has wreaked havoc in the Exchange environment. In the meantime I am upgrading to CU3 as it is forcing me to re-install RSAT tool for Active directory preparation.
0
Group_007
Asked:
Group_007
1 Solution
 
MarkMichaelCommented:
What is the DNS of your CAS servers set to?

Can you confirm DNS is working from the CAS servers?

Ensure they have DNS pointing to operating DCs and complete a ipconfig /flushdns and ipconfig /registerdns on each CAS server.
0
 
Simon Butler (Sembee)ConsultantCommented:
"Problem 1: CAS servers in the DMZ did not pickup new IP's"

That is an unsupported configuration to begin with. No role of Exchange is supported in a DMZ other than the Edge role - you have just seen a clear reason of why that is usually a bad idea.

Have the Exchange services been restarted since the domain controllers were changed?

Simon.
0
 
Group_007Author Commented:
Simon: it has worked well for the past 4-5 months. The culprit is the old DNS was still taking requests. IP flush DNS done the trick. Our net admin needed to force an early IP renew.

I should have added that although our host Hyper V is in the DMZ our IP are all configured as though it sits in the production LAN. Otherwise 'yes' we would probably experience more issues.
0

Featured Post

Prep for the ITIL® Foundation Certification Exam

December’s Course of the Month is now available! Enroll to learn ITIL® Foundation best practices for delivering IT services effectively and efficiently.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now