Creating a domain controller on small domain

We have two virtual servers, one the primary domain controller, the other the Exchange server.
The DNS is not running properly and I am trying to locate the problem .  I have checked the DNS server on both servers and they appear to be right, but to be honest there is still much I don't understand about configuring DNS.  

Because the server manager is puching me to upgrade the Exchange server to a domain controller, I am trying to do that.  This has highlighted an issues that might be the reason for the DNS problems. when trying to upgrade the Exchange server to be a domain controller, it is reporting that "an active directory domain for the domain could not be contacted"

Can anyone point me in the right direction here.  This has been hanging over me for days now.
CarmeldanITAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Andy MIT Systems ManagerCommented:
For starters you shouldn't really have an exchange server as a domain controller. Although this can work it's not a good practice and Microsoft do frown upon it. You'll probably be getting the message to do so becuase the exchange server cannot see the DC properly.

Based on the information provided the first step is to run some dns tests on your current DC and the Exchange server:

1. Run nslookup for the domain - does it come back with the DC details?
2. Is dns functional on the DC - can you resolve internal hostnames for the domain on it?
3. Any dns events on the DC?
4. Can the dc be reachable via it's hostname?
5. What are the dns settings on the DC/Exchange NICs?
0
Simon Butler (Sembee)ConsultantCommented:
It is not supported to change the role of a server with Exchange installed.
Promoting a server to domain controller with Exchange installed will usually break Exchange.
If Exchange was installed on a member server it must stay as a member server.

"Because the server manager is puching me to upgrade the Exchange server to a domain controller,"

The only reason I can think that it is doing that is because you installed the domain controller role. Remove that. It isn't required and you will not be doing anything with it because you need to stop trying to make this machine a domain controller.

If you suspect that the domain controller you have has a problem, you need to build another domain controller - a VM or mid range workstation will do the job. Using the Exchange server to assist with troubleshooting is not a good idea.

Simon.
0
CarmeldanITAuthor Commented:
Thanks Andy,

The first thing I see is that the PDC server is not being found.  It has an IP address starting 192 and it is correct on the server.  However, the Exchange server thinks it is 182.  I've been looking for where this has happened, but not yet found it.
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

Muhammad MullaSystems AdministratorCommented:
Changing from 192 to 182 seems to indicate a typo to me.

Check IP settings as well as any manual entries in the hosts file.
0
CarmeldanITAuthor Commented:
Hello OfficeGeek, ref the typo on the IP Address.  Yes it must be a typo but as yet I have not been able to see where it is.  It must be in the Exchange server machine somewhere, as I can ping the PDC from elsewhere correctly.  It is just restarting at the moment so will look then.  Could well be the hosts file.
0
it_saigeDeveloperCommented:
First, validate your time settings for me.  If you have a virtualized PDC, then it is possible that your time could be off.  To correct you need to access the Hyper Visor and disable the Time Integration service:

Assuming Hyper-V:Capture.JPGSecond, lets validate your network card settings on the virtual DC (for example, I have multiple DC's with DNS running, this one has itself as the primary DNS server and an alternate DNS server [you don't *need* an alternate DNS serever for a small network but it would not hurt to have one]):Capture.JPGThird, lets validate your current DNS settings:Capture.JPGCapture.JPGFinally, run a DCDIAG from the command prompt on your domain controller and post the results here (you can redirect the output to a text file using the following command):Capture.JPG
-saige-
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
CarmeldanITAuthor Commented:
Hi,

Thank you. DCDIAG shown below.  I have run the checks on the DNS This appears to be OK now.  Next problem is to set up exchange to send out via SMTP.

 Trying to find home server...
   Home Server = Server2012
   * Identified AD Forest.
   Done gathering initial info.
Doing initial required tests
   Testing server: Default-First-Site-Name\SERVER2012
      Starting test: Connectivity
         ......................... SERVER2012 passed test Connectivity
Doing primary tests
   Testing server: Default-First-Site-Name\SERVER2012
      Starting test: Advertising
         ......................... SERVER2012 passed test Advertising
      Starting test: FrsEvent
         ......................... SERVER2012 passed test FrsEvent
      Starting test: DFSREvent
         ......................... SERVER2012 passed test DFSREvent
      Starting test: SysVolCheck
         ......................... SERVER2012 passed test SysVolCheck
      Starting test: KccEvent
         ......................... SERVER2012 passed test KccEvent
      Starting test: KnowsOfRoleHolders
         ......................... SERVER2012 passed test
KnowsOfRoleHolders
      Starting test: MachineAccount
         ......................... SERVER2012 passed test
MachineAccount
      Starting test: NCSecDesc
         ......................... SERVER2012 passed test NCSecDesc
      Starting test: NetLogons
         ......................... SERVER2012 passed test NetLogons
      Starting test: ObjectsReplicated
         ......................... SERVER2012 passed test
ObjectsReplicated
      Starting test: Replications
         ......................... SERVER2012 passed test Replications
      Starting test: RidManager
         ......................... SERVER2012 passed test RidManager
      Starting test: Services
         ......................... SERVER2012 passed test Services
      Starting test: SystemLog
         ......................... SERVER2012 passed test SystemLog
      Starting test: VerifyReferences
         ......................... SERVER2012 passed test
VerifyReferences
   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 : Domain2
      Starting test: CheckSDRefDom
         ......................... Domain2 passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... Domain2 passed test
CrossRefValidation
   Running enterprise tests on : Domain2.local
      Starting test: LocatorCheck
         ......................... Domain2.local passed test
LocatorCheck
      Starting test: Intersite
         ......................... Domain2.local passed test Intersite
C:\Users\Administrator>
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Networking

From novice to tech pro — start learning today.