Update. It appears to have been related to IPv6 DNS entries for the DCs. While troubleshooting, I noticed that I could not ping them via IPv6. Odd. I next discover that there are 2 IPv6 AAAA records for each DC. Also Odd. I deleted them both for DC2 (I chose this one because it holds all the FSMO roles) and ran ipconfig /registerdns. Nothing seemed to change, so I rebooted DC2. Lo and behold, in a few minutes the next 2080 event goes back to CDG 1 7 7 1 0 1 1 7 1 for DC2 and stays CDG 1 0 0 1 0 0 0 0 0 for DCs 1 and 4. I deleted the IPv6 AAAA records for the other two, rebooted them, and now Exchange can communicate with all my DCs again.
Clearly I need to understand IPv6 better. During all of this I noticed that ipconfig /all gives different output from before and after the reboots. Before rebooting the last DC, I redirected the output of ipconfig /all to a text file, and did the same after rebooting. The differences were: 1) Before rebooting, ipconfig /all had entries for IPv6 Address, Site-local IPv6 Address, and Link-local IPv6 Address. After rebooting, only Link-local IPv6 Address remained. 2) Before rebooting, there was no section for Tunnel adapter 6TO4 Adapter. After rebooting, this section is present. Lastly, I have just gone back to DNS and all of the domain level IPv6 AAAA records for all of my DCs are gone. Dcdiag /test:dns shows missing AAAA records at both the domain level and for gc._msdcs.domain.local, however there are AAAA records at gc.msdcs.domain.local for each DC. These match the addresses in each 6TO4 adapter. Despite this latest oddity, Exchange is now happy, and everything appears to be functioning normally, so I'm heading home. I'll see how things are in the morning and will post if there are changes. Does anyone have any pointers about the behavior described? 6TO4 adapters appearing after reboot, AAAA records appearing then disappearing, etc? Thanks, Richard On Sat, Jun 30, 2012 at 5:38 PM, Richard Stovall <[email protected]> wrote: > Forgot to mention that all DCs are GCs. > > On Sat, Jun 30, 2012 at 5:34 PM, Richard Stovall <[email protected]>wrote: > >> I applied SP2 UR3 today to my single Exchange 2010 server. Now, after a >> few minutes of uptime, the AD topology service appears to lose the ability >> to reach any of the DCs in the server's local site. The App log's 2080 >> events go from this: >> >> In-site: >> DC4.domain.local CDG 1 7 7 1 0 1 1 7 1 >> DC2.domain.local CDG 1 7 7 1 0 1 1 7 1 >> dc1.domain.local CDG 1 7 7 1 0 1 1 7 1 >> Out-of-site: >> SLCDC.domain.local CDG 1 7 7 1 0 1 1 7 1 >> >> to this: >> >> In-site: >> DC4.domain.local CDG 1 0 0 1 0 0 0 0 0 >> DC2.domain.local CDG 1 0 0 1 0 0 0 0 0 >> dc1.domain.local CDG 1 0 0 1 0 0 0 0 0 >> Out-of-site: >> SLCDC.domain.local CDG 1 7 7 1 0 1 1 7 1 >> >> >> In about 15 minutes after a reboot. >> >> Everything is still working, but I have no idea what's going on. One >> thing to note, I did try to install UR3 without running it from an elevated >> command prompt and it failed. That's when I first noticed this. A reboot >> of the server cleared up the 2080 issue briefly, but it returned when I >> installed RU3 and it succeeded. The local DCs are all up and running >> without issue. >> >> There are also tons of 2084 and 2085 events on the Exchange server >> related to this. For example: >> >> "Process STORE.EXE (PID=5800). No Global Catalog server is up in the >> local site 'Default-First-Site-Name'. Exchange Active Directory Provider >> will use the following out of site global catalog servers: >> SLCDC.domain.local" >> >> Any thoughts out there about how to fix this? >> >> >> --- >> To manage subscriptions click here: >> http://lyris.sunbelt-software.com/read/my_forums/ >> or send an email to [email protected] >> with the body: unsubscribe exchangelist >> > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to [email protected] > with the body: unsubscribe exchangelist > --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe exchangelist
