exchange 2010 error 0x80040a02 dsc_e_no_suitable_cdc De Valls Bluff Arkansas

Unlike other computer consultants that charge an hourly rate in case of "unexpected circumstances," we will provide you with one flat rate per project and guarantee to deliver you the solutions you need without charging a penny more.

Virus or Spyware removal, speed up computer, wireless network setup, data backup, Hardware, software installed.

Address Pine Bluff, AR 71603
Phone (870) 872-0832
Website Link
Hours

exchange 2010 error 0x80040a02 dsc_e_no_suitable_cdc De Valls Bluff, Arkansas

The new Exchange server can ping any of the domain controllers (and anything else, for that matter) by hostname. –NorbyTheGeek May 31 '12 at 22:14 And the Exchange server And just like magic, the topology error is gone. Sunday, August 15, 2010 6:18 PM Reply | Quote Answers 0 Sign in to vote The issue is resolved. Use the Ping or PathPing command-line tools to test network connectivity to local domain controllers.

Reply Manhar says: January 17, 2013 at 2:55 am Hey Gents, Enabling IPv6 did it again. It is running client, hub and transport roles. Reply Andrew from TN says: June 21, 2010 at 1:36 pm The Exchange 2010 servers (All Roles) should be in the Exchange Trusted SubSystem group. This link explains the codes:http://support.microsoft.com/kb/316300 Thanks to all for the help.

Use the Ping or PathPing command-line tools to test network connectivity to local domain controllers. To do this, use Microsoft Knowledge Base article 218185, "Microsoft LDAP Error Codes." Use the information in that article to learn more about the cause and resolution to this error. Topology discovery failed. The event viewer would show MAD.EXE with an error code of 0x80040a02 (DSC_E_NO_SUITABLE_CDC).

Make all the statements true The mortgage company is trying to force us to make repairs after an insurance claim How do computers remember where they store things? THANK YOU. Use the Ping or PathPing command-line tools to test network connectivity to local domain controllers.The KB article mentioned gave outdated information (applicable to Windows 2000) and proved useless.An information entry was How is the Heartbleed exploit even possible?

The Exchange Server group wasn't in the policy. broken. The Microsoft Exchange Transport service would also be stuck in a "starting" state. View my complete profile Total Pageviews Followers Blog Archive ► 2016 (2) ► August (1) ► June (1) ► 2015 (2) ► February (1) ► January (1) ► 2014 (7) ►

Near Earth vs Newtonian gravitational potential Any better way to determine source of light by analyzing the electromagnectic spectrum of the light Unusual keyboard in a picture Are independent variables really Vikas says: 27th October 2013 at 16:22 I enabled IPv6 and resolved my issue. This group is in turn a member of the Administrators group. current community blog chat Server Fault Meta Server Fault your communities Sign up or log in to customize your list.

They are my own personal thoughts so take it for what it's worth. | Search MSDN Search all blogs Search this blog Sign in Anything And Everything by Keith McGuinness Anything And Everything by Keith McGuinness Exchange 07: Topology discovery failed, error 0x80040a02 (DSC_E_NO_SUITABLE_CDC) thanks for taking the time ot put this info up fo newbies like me to find. I cleared the messages and for the last 50 minutes have had no topology messages.

It worked as soon as I added the computer to the group. Powered by Blogger. As it turns out the organization may have modified their Default Domain Controllers GPO. Social github linkedin google-plus stack-overflow Tags Scripts PowerShell Linux Security Mysteries Solved Active Directory Ruby Windows Chef One-Liner Group Policy Bash SharePoint Python Ramblings HTTP Registry Programming Kerberos Event Log FileSystem

Lucia Storbritannien Surinam Swaziland Sverige Sydafrika Tadzjikistan Taiwan Tanzania Tchad Thailand Tjeckien Togo Trinidad och Tobago Tunisien Turkiet Turkmenistan Turks- och Caicosöarna Tyskland Uganda Ukraina Ungern Uruguay USA Uzbekistan Vanuatu Venezuela I have been in IT for the last 14 years, with interests in Active Directory, Exchange, Office 365 & Windows Azure. I just enabled IPv6 (still wonder why/when it got disabled) and everything got back to normal, and I can finally sleep!!!!! It really helped me orient my troubleshooting in the right direction since I'm not a windows person.

This fixed all of my issues! I cloned a working system so I can practice an upgrade. Made this change in my GPO and now my Exchange 2010 server boots up in no time with all services started! I am not sure if it was re-enabling IPv6 or adding DC to the domain admins group.

Newer Post Older Post Home Subscribe to: Post Comments (Atom) About Me Martijn Westera Technical Consultant at KPN Consulting View my complete profile Blog Archive ► 2015 (5) ► August (1) The Exchange servers won't finish loading (they'd get stuck on "Applying computer settings", while actually waiting for the Microsoft Exchange System Attendant service to finish starting). Reply Uffe says: November 19, 2013 at 7:07 pm Just wanted to say a BIG THANKS for turning my attention to the IPv6! As I review the logs again (and for the benefit of anyone else that runs into this), the post I put above that shows the 2080 event id log and the

worked a treat. To do this, use Microsoft Knowledge Base article 218185, "Microsoft LDAP Error Codes." Use the information in that article to learn more about the cause and resolution to this error. Well, sorta.lemmi on OpenCart is slow with many categoriesLorraine on Conditional Woocommerce Product Tabsray on Exchange 2003, 2007 & 2010 Topology discovery failed, error 0x80040a02 (DSC_E_NO_SUITABLE_CDC)Kieran Barnes on Show saving on Something needs to be fixed here.

After putting a new Exchange 2010 Server to our organization (only one Ex 2003 server) without problems, almost all Exchange services at the new server refused to start after the first All domain controllers are 2003 R2. Thanks a lot !!!ReplyDeleteAnonymousOctober 6, 2010 at 4:06 PMI experienced the same symptoms you describe with Exchange 2010 installed on a domain controller, but the "Exchange Servers" group WAS present in Exchange 2010 needs to see all subnets containing domain controllers in Active Directory.

Thanks! This is very nice article about topology issues in exchange server. Reply David says: October 8, 2009 at 4:53 pm Wow, after working on this for nearly 16 hours and beating my head agains the wall, your suggestion to add the computer As soon as the Exchange 2003 uninstall was complete, we started getting the same errors.

This was associated when a system joins a domain by default. I checked the registry to see whether it was fully disabled and it wasn't. Only thing to fix it was to run Exchange 2003 SP2 command " update /DomainPrep " 24 hours later, same problem. Seemed odd to me.

We are running 2010 on a DC and not sure how IPv6 became unchecked. It's an ugly fix, but something M$ should have addressed by now. This is the article that helped me determine this… http://msmvps.com/blogs/ehlo/archive/2008/06/12/1634433.aspx BTW, this article also references a way to complete disable IPV6 to resolve the issue, but I just enabled IPV6 on The setting they've changed is "Manage auditing and security log" which contained the global group called "Exchange Enterprise Servers" among others.

I wish I knew that a day ago. Great to know how to resolve this issue.ReplyDeleteAnonymousJune 24, 2015 at 7:32 AMalmost just shat my pants doing an AD project where we demoted the last DC that had this set Fixed that problem and another, dcdiag now runs clean. As such Quick Tips have not been reviewed, validated or approved by Dell and should be used with appropriate caution.