Exchange 2010 Setup Error (Cannot Find DC)

cyberchrisrock
cyberchrisrock used Ask the Experts™
on
I am installing Exchange 2010 on a 2008 standard Server platform. The server has been installed as a member server and has been in place for 4 week with no issues. It does not have the "AD" role installed. it is a member of the domain(single domain) 64bit with NAV 10.x installed. it is on the same LAN as the DC.

The DC has DHCP & DNS as well as "AD" roles and has been in please for 8 months with no issues
I am now installing Exchange 2010 on the member server. The prerequisites all passed except for the following error:
"Setup encountered a problem while validating the state of Active Directory. Could not find any Domain Controller in domain "CompanyDomain.local"
I am at the end of my rope with this and need some guidance from anyone who has experienced and this.

Thanks in advance

Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Awarded 2009
Top Expert 2010
Commented:
Disable any virus/firewall/security software on the exchange server and DC.

Check the exchange server is configured to use the DC as it's DNS server  there should be no other entries.  Make sure the DC is only configured to use itself as DNS.  If you make any changes here restart the NETLOGON service.  

Make sure you haven't disabled IPv6?  Can the exchange server PING the DC by netbios name and Fully Qualified domain Name?

If still no go run DCDIAG on the DC and post the results

Author

Commented:
Thanks for your speedy reply.
1:  I disabled the virus/firewall/security software on the exchange server and DC.

2: The exchange server is configured to use the DC as it's DNS server & there are no others

3: The DC is only configured to use itself as DNS.

4: IPv6 is has NOT been Disabled on either server

5: The Exchange server CAN Ping the DC via its FQDN & Netbios names........

and so I ran DCDIAG

the following are the results of the DCDIAG:
-----------------------------------------------------------------------------------------------

C:\>DCDIAG

Directory Server Diagnosis

Performing initial setup:
   Trying to find home server...
   Home Server = DC-Server
   * Identified AD Forest.
   Done gathering initial info.

Doing initial required tests

   Testing server: Default-First-Site-Name\DC-Server
      Starting test: Connectivity
         The host d2f06933-0787-472d-b30f-a05285b10354._msdcs.domain.local could
         not be resolved to an IP address. Check the DNS server, DHCP, server
         name, etc.
         ......................... DC-Server failed test Connectivity

Doing primary tests

   Testing server: Default-First-Site-Name\DC-Server
      Skipping all tests, because server DC-Server is not responding to
      directory service requests.


   Running partition tests on : ForestDnsZones
      Starting test: CheckSDRefDom
         ......................... ForestDnsZones passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... ForestDnsZones passed test
         CrossRefValidation

   Running partition tests on : DomainDnsZones
      Starting test: CheckSDRefDom
         ......................... DomainDnsZones passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... DomainDnsZones passed test
         CrossRefValidation

   Running partition tests on : Schema
      Starting test: CheckSDRefDom
         ......................... Schema passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... Schema passed test CrossRefValidation

   Running partition tests on : Configuration
      Starting test: CheckSDRefDom
         ......................... Configuration passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... Configuration passed test CrossRefValidation

   Running partition tests on : gomwi
      Starting test: CheckSDRefDom
         ......................... gomwi passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... gomwi passed test CrossRefValidation

   Running enterprise tests on : domain.local
      Starting test: LocatorCheck
         ......................... domain.local passed test LocatorCheck
      Starting test: Intersite
         ......................... domain.local passed test Intersite

C:\>

As you can see, it seems that I have a DNS problem. I do not know where to start.
There is an "A" records fro the DC as well as the Exchange server..

Thanks in advance
AkhaterSolutions Architect

Commented:
on your DNS server is dynamic updates enabled ?

is the server DC-Server still online or is it an old decommissioned server?


assuming your DNS server has dynamic updates enabled fro domain.local and that DC-Server is still up and running what is the DNS configuration of DC-server?


I mean what is DC-server using as DNS server?

try to net stop netlogon net start netlogon on DC-Server
Success in ‘20 With a Profitable Pricing Strategy

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!

Awarded 2009
Top Expert 2010

Commented:
Can you try running DCDIAG /FIX as the first step?
Awarded 2009
Top Expert 2010

Commented:
if DCDIAG /FIX doesn't work check your DNS, under your forward lookup zone is the _msdcs greyed out?
If so have a look at this post and follow the instructions: http://www.experts-exchange.com/Networking/Protocols/DNS/Q_24349599.html

Author

Commented:
I ran DCDIAG /FIX. the results are posted below:

-------------------------------------------------------------------------
C:\Users\Administrator>DCDIAG /FIX

Domain Controller Diagnosis

Performing initial setup:
   Done gathering initial info.

Doing initial required tests

   Testing server: Default-First-Site-Name\DC-Server
      Starting test: Connectivity
         ......................... DC-Server passed test Connectivity

Doing primary tests

   Testing server: Default-First-Site-Name\DC-Server
      Starting test: Replications
         ......................... DC-Server passed test Replications
      Starting test: NCSecDesc
         ......................... DC-Server passed test NCSecDesc
      Starting test: NetLogons
         ......................... DC-Server passed test NetLogons
      Starting test: Advertising
         ......................... DC-Server passed test Advertising
      Starting test: KnowsOfRoleHolders
         ......................... DC-Server passed test KnowsOfRoleHolders
      Starting test: RidManager
         ......................... DC-Server passed test RidManager
      Starting test: MachineAccount
         ......................... DC-Server passed test MachineAccount
      Starting test: Services
         ......................... DC-Server passed test Services
      Starting test: ObjectsReplicated
         ......................... DC-Server passed test ObjectsReplicated
      Starting test: frssysvol
         ......................... DC-Server passed test frssysvol
      Starting test: frsevent
         ......................... DC-Server passed test frsevent
      Starting test: kccevent
         ......................... DC-Server passed test kccevent
      Starting test: systemlog
         An Error Event occured.  EventID: 0x00000457
            Time Generated: 02/01/2010   22:27:45
            (Event String could not be retrieved)
         An Error Event occured.  EventID: 0x00000457
            Time Generated: 02/01/2010   22:27:46
            (Event String could not be retrieved)
         ......................... DC-Server failed test systemlog
      Starting test: VerifyReferences
         ......................... DC-Server passed test VerifyReferences

   Running partition tests on : ForestDnsZones
      Starting test: CrossRefValidation
         ......................... ForestDnsZones passed test CrossRefValidation

      Starting test: CheckSDRefDom
         ......................... ForestDnsZones passed test CheckSDRefDom

   Running partition tests on : DomainDnsZones
      Starting test: CrossRefValidation
         ......................... DomainDnsZones passed test CrossRefValidation

      Starting test: CheckSDRefDom
         ......................... DomainDnsZones passed test CheckSDRefDom

   Running partition tests on : Schema
      Starting test: CrossRefValidation
         ......................... Schema passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... Schema passed test CheckSDRefDom

   Running partition tests on : Configuration
      Starting test: CrossRefValidation
         ......................... Configuration passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... Configuration passed test CheckSDRefDom

   Running partition tests on : CompanyDomain
      Starting test: CrossRefValidation
         ......................... CompanyDomain passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... CompanyDomain passed test CheckSDRefDom

   Running enterprise tests on : CompanyDomain.hou
      Starting test: Intersite
         ......................... CompanyDomain.hou passed test Intersite
      Starting test: FsmoCheck
         ......................... CompanyDomain.hou passed test FsmoCheck

C:\Users\Administrator>

I deleted the main forward lookup zone and recreated it, but it never did recreate the msdcs I am truly stuck. What do I do? I know that I just can't delete and reinstall DNS.. It is integrated with AD. This is 2008 Server standard. I checked my stuff at home and my server is 2003 and it is setup and running fine. As matter of fact the msdcs and all other faculties are there and functioning correctly.

I seriously need some pointers...help me please.
Awarded 2009
Top Expert 2010

Commented:
Did you run DCDIAG /FIX after recreating the zone?

Author

Commented:
UPDATE

I ran net stop NETLOGON
        net start NETLOGON

Rebooted the server, and gues what? the msdcs, tcp udp folders were recreated. I will now continue to try the Exchange 2010 installation and will post the results later today.

demazter:
To answer you question, yes I di run DCDIAG /FIX after recreating the zone, and at that point the msdcs and accompanying folders were not recreated.  Thanks
AkhaterSolutions Architect

Commented:
so ur issue is solved now?

Author

Commented:
Hello everyone:

The problem was solved with "a little help from my friends" here her @ EE.

The DNS was jacked up so once I  ran net stop NETLOGON         net start NETLOGON, then that fixed the DNS is, which in turn fixed a ton of other miscellaneous issues.

I attempted to install Exchange again by 1st running the prerequisites and it came back with a grocery list of things that needed to be done to the DC and the server intended for Exchange. At that point I searched for Exchange 2010 prerequisites and found this link.
http://technet.microsoft.com/en-us/library/bb691354.aspx

It contained all the information necessary to pre-configure both the DC and the intended Exchange server. Once I followed that "Grocery" list Exchange installed without a hitch. I do thank all of you for your consistent high quality input.

What I have remaining now is to figure out setting up a MTA on the DMZ and forwarding the mail to this server which is on the inside. The MTA will be a Red Hat machine running send mail, which will forward all mail to the exchange server. If anyone is familiar with that and do not mind giving me a word. I would sincerely appreciate it.

Thanks again


Awarded 2009
Top Expert 2010

Commented:
Glad you got it sorted, don't forget to close the question down.

There is a zone for SendMail so your probably better off opening a new question in that zone.  Exchange doesn't really care who it receives milfrom.

One thing you will need to do though is on the server that has the hub transport role under Server Configuration > Hub Transport > receive connector under properties of the connector that starts with default on the last tab (permission groups) make sure the anonymous box has a check in it then restart the Microsoft Exchange Transport service

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial