Update – for some odd reason I thought about creating a new Administrator account (named something else) and assigned it the correct rights (same as Administrator).? Oddly, that worked and I am able to now pull the Databases.
So it appears that this fixed the issue.? Thanks for your fast assistance!
Rick
Further note on this issue (for the benefit of others reading it). ?The problem came back again, however it made no sense as Exchange worked fine and we could login to the CP server in Windows with no problems authenticating to the domain.
Long story short, we found that we had neglected to setup a reverse lookup zone in the domain controllers, and thus the systems in the domain could do lookups on the machine name (i.e., “exchange”) but not the full name (exchange.domain.local). ?Once the reverse lookup zone was put in place and PTR records made (by going into the forward lookup zone and hitting properties on each machine, uncheck the box “create PTR record”, apply, re-check the box “create PTR record”, then hit okay) everything worked fantastic. ?And if an IP address changes the PTR record will change as well.
So, hard lesson learned. ?FYI, the reverse lookup zone in DNS is not created automatically when installing AD on a Server 2012 R2 server so you’ll need to do this manually.
Rick
