Exchange 2010 Error 9104
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeOnline20132010Other VersionsLibraryForumsGalleryEHLO Blog Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: Error after changing IP of Exchange Server Previous Versions of Exchange > Exchange Server 2010 Question 0 Sign in to vote Hi, We have a test environment that we just made some modifications. We changed IP of all servers, including DC/GC and one Exchange 2010 Server. I thought this one should go smooth but I was wrong! hehe On the Exchange Server I can see tons of errors: EventID: 9104 Service MSExchangeMailSubmission. Exchange topology discovery can't find the local Exchange server. Any hints on what I can do or is this the point where I go boom (reset computer account and install the server again using recoverserver switch?) Tuesday, September 13, 2011 6:01 AM Reply | Quote Answers 0 Sign in to vote Problem solved, it has lost the DNS suffix... Thx for the help! Marked as answer by [zid] Tuesday, September 13, 2011 7:44 AM Tuesday, September 13, 2011 7:43 AM Reply | Quote All replies 1 Sign in to vote Hi, I would check and see if the new IP-Address have been registered in DNS and also run ipconfig /flushdns on the DC/GC and Exchange Servers. Also check the IP Addresses specificed on the Receive Connectors. Do they have the default value (All Available IPv4/Ipv6) or not.Martina Miskovic Tuesday, September 13, 2011 6:06 AM Reply | Quote 0 Sign in to vote Also check the EventID 2080 in the Application Log. Do the Exchange Servers find all GCs that are In-Site? A restart of the Active Directory Toplogy Service might not be a bad idea (will restart all exchange services) Martina Miskovic Edited by Martina_MiskovicMVP Tuesday, September 13, 2011 6:16 AM Spelling Tuesday, September 13, 2011 6
- Follow 43 Mentions12 Products Neal (Exclaimer) Sales & Marketing Manager GROUP SPONSORED BY EXCLAIMER TECHNOLOGY IN THIS DISCUSSION NetApp 135715 Followers Follow Cisco 344121 Followers Follow VMware 396220 Followers Follow Microsoft Wind...Server 2008 R2 Microsoft Exchange Server 2010 Join the Community! Creating your account only takes a few minutes. Join Now ◄ Prev 1 2 3 4 5 Next ► 97 Replies Pimiento OP jakapongc Jun 15, 2011 at 1:46 UTC Hi Scott, I plan to disable my NIC https://social.technet.microsoft.com/Forums/exchange/en-US/22dbe4c2-0c93-43a5-abcb-b5eff20fa4f8/error-after-changing-ip-of-exchange-server?forum=exchange2010 teaming and disable Chimney, RSS, and NetDMA. Not sure whether they will help or not? Could you please guide me what changes you did? 0 Pimiento OP Scott Feltmann Jun 15, 2011 at 4:54 UTC Hi Jakapongc, It may help. In my case it didn't help. I have been doing a number of things to test for a https://community.spiceworks.com/topic/134941-exchange-2010-ad-topology-failures-all-domain-controllers-unavailable?page=2 resolution. In about two weeks I should know if my last attempt has worked or not. I hate to say tyr this and this knowning that it won't help you.... 0 Jalapeno OP Martin4470 Jun 16, 2011 at 2:11 UTC Well ive tried lots more since, and still have the issue. IPV6 re-enabling Check SID and all SIDs are different. NIC Bindings Provider Order Domain GPO settings with regards to manage audit log privileges. Even the physical server is now experieicng the same fault. Now... i have added the virtual servers to "domain admins" as suggested by another Blog, and left the physical one without. Restarted the servers (because they did it again) and now it's a wiating game, circa 7-14 days before i will see if the Domain Admins trick has worked. 0 Pimiento OP jakapongc Jun 16, 2011 at 12:13 UTC Thanks a lot Scott & Martin for your responses, My tasks today were: - Find duplicate SPN by running setspn -x => no issue found - Verify DNS settings => no i
Active Directory Integration Tool Services Exchange Active Directory SharePoint OCS/Lync Customer Success Blog Support ENow Exchange & Office 365 Solutions Engine Blog (ESE) Exchange Can't Start Due to Misconfigured AD Sites Posted by Michel de Rooij on Aug 8, http://blog.enowsoftware.com/solutions-engine/bid/132664/Exchange-Can-t-Start-Due-to-Misconfigured-AD-Sites 2012 1:38:00 PM Find me on: Facebook LinkedIn Twitter Tweet Recently, a customer http://serverfault.com/questions/394533/new-exchange-2010-cas-cannot-find-domain-controllers had issues with their Exchange server which didn’t start properly after rebooting. After checking out the Eventlog, I noticed that it was full of messages, generated by all services. The most interesting events were the ones generated by MSExchange ADAccess: MSExchange ADAccess, EventID 2141 Process STORE.EXE (PID=2996). Topology discovery failed, error 0x8007077f MSExchange exchange 2010 ADAccess, EventID 2142 Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=1760). Topology discovery failed, error 0x8007077f Also, the results of the active directory discovery process generated every 15 minutes, which are normally logging in event 2080, “Exchange Active Directory Provider has discovered the following servers with the following characteristics”, was missing. Note that because the system could start the Microsoft Exchange Active Directory Topology service (until it failed and is exchange 2010 error restarted by dependent services), Exchange’s other services were also triggered, leading to almost indefinitely restarting services as configured in their corresponding service recovery actions sections. Now, since I had connected to a domain controller using an RDP session from my client, and I was able to connect to port 389 (Global Catalog) from Exchange using LDP, the communications looked fine. Then, I switched to Active Directory Sites and Services: As you can see from the shot, this was a potential cause of the problem. First, there was a site without domain controllers. Second, there were no subnets defined. So, in this situation, it is undetermined in which site Exchange is located. When a system can’t determine in which site a computer belongs, the function DSGetSiteName, used to retrieve the current site, returns an error 1919 0x77f (ERROR_NO_SITENAME). Consequently, the Exchange Active Directory discovery process fails and eventually Exchange fails. You can inspect the current discovered site usingnltest/dsgetsiteor by having a peek in the registry at HKLM\System\CurrentControlSet\Services\Netlogon\Parameters\DynamicSiteName. Now, to solve the situation we have three options: Making the site association static using a registry key, which isn’t a best practice. If you must, set registry key HKLM\SYSTEM\Curren
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top New Exchange 2010 CAS cannot find domain controllers up vote 2 down vote favorite I am experiencing problems migrating from Exchange 2003 to Exchange 2010. I am on the first step: installing a new 2010 Client Access Server role. The Active Directory domain functional level is 2003. All domain controllers are 2003 R2. The only existing Exchange 2003 server happens to be housed on one of the domain controllers. It is running Exchange 2003 Standard w/ SP2. IPv6 is enabled and working on all domain controllers, servers, and routers, including this new Exchange server. After installing the CAS role on a new 2008 R2 server (Hyper-V VM) I am receiving 2114 Events: Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=1600). Topology discovery failed, error 0x80040a02 (DSC_E_NO_SUITABLE_CDC). Look up the Lightweight Directory Access Protocol (LDAP) error code specified in the event description. 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. Use the Ping or PathPing command-line tools to test network connectivity to local domain controllers. Prior to each, I receive the following 2080 Event: Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=1600). Exchange Active Directory Provider has discovered the following servers with the following characteristics: (Server name | Roles | Enabled | Reachability | Synchronized | GC capable | PDC | SACL right | Critical Data | Netlogon | OS Version) In-site: b.company.intranet CDG 1 0 0 1 0 0 0 0 0 s.company.intranet CDG 1 0 0 1 0 0 0 0 0 Out-of-site: a.company.intranet CD- 1 0 0 0 0 0 0 0 0 o.company.intranet CD- 1 0 0 0 0 0 0 0 0 g.company.intranet CD- 1 0 0 0 0 0 0 0 0 Connectivity between the new Exchange server and all domain controllers via IPv4 and IPv6 are all working. I have verified that the new Exchange server is a member of the following groups: Exchange Servers Exchange Domain Servers Exchange Install Domain Servers Exchange Trusted Subsystem Heck, I even put the new Exchange server into Doma