Solved

Unable to Join Windows 8 to Windows 2008 2 domain Controller

Posted on 2016-08-02
9
76 Views
Last Modified: 2016-08-28
I am quite a newbie to system admin world but have sorted out random problems in the past.

I had a task to prepare domain controller which i think i did and create a DC with dns on a windows 2008 R2 as DCPROMO ran fine.

Now i am trying to join Windows 8 To this server but getting this error:


DNS was successfully queried for the service location (SRV) resource record used to locate a domain controller for domain "test.tus.com":
The query was for the SRV record for _ldap._tcp.dc._msdcs.test.tus.com

The following domain controllers were identified by the query: win-iokdrl8pn6l.test.tus.com

However no domain controllers could be contacted.

Common causes of this error include:

Host (A) or (AAAA) records that map the names of the domain controllers to their IP addresses are missing or contain incorrect addresses.
Domain controllers registered in DNS are not connected to the network or are not running.

I have given DNS ip address in the windows 8 machine and able to ping both test.tus.com as well as win-iokdrl8pn6l.test.tus.com. Just to let you know these are completely FRESH INSTALLATIONS AND THERE ARE NO SETTINGS AT ALL.

Finally i went to the server and on server manager was seeing few errors. screenshot is attached below.activedirectory-error.png
I have also ran dcdiag command though i hardly know about it (internet research) and here are the results.dcdiag-results.png
Please help me as i have already spent too much time in research.
0
Comment
Question by:TUS11
  • 5
  • 3
9 Comments
 
LVL 34

Expert Comment

by:Paul MacDonald
ID: 41739586
If the DC has a firewall, it may be blocking traffic used by Active Directory.  I would start there.
0
 
LVL 16

Accepted Solution

by:
FOX earned 500 total points
ID: 41739608
1.  On the nic of the domain controller  IPV4 properties set the preferred DNS to the same Ip that the domain controller has.
2.  If IpV6 is has a check mark, uncheck it.
3.   On your domain controller turn off all windows firewalls.  On your workstations turn off all windows firewalls
4.   After you have set the preferred DNS to point to itself and possibly a reboot, Go in to Administrative Tools> DNS of the domain controller and look in forward lookups verify if you can see the Domain controller servername with the correct IP
0
 
LVL 16

Assisted Solution

by:FOX
FOX earned 500 total points
ID: 41739642
Go to Administrative Tools>Active Directory Sites and Services>Default First Site Name>Servers, expand your domain controller>right-click NTDS settings and click properties>PUT A CHECKMARK IN GLOBAL CATALOG to set it as a Global catalog
1
DevOps Toolchain Recommendations

Read this Gartner Research Note and discover how your IT organization can automate and optimize DevOps processes using a toolchain architecture.

 

Author Comment

by:TUS11
ID: 41742788
@Foxluv - This is reply to your 2nd comment. I am trying your first comment now.Got this error when tried to clicked on Active Directory Sites and Services
error3.png
and when clicked ok, got below screenshot.
err4.png
Please help!

@paulmacd

disabled the firewall at the server. Nothing helped.
0
 

Author Comment

by:TUS11
ID: 41742797
just a point @Foxluv - if i point dns on dc to itself then if tomorrow i want to route traffic through this server itself to the clients attached to this then how will it allow? hence dns should point to the router gateway (which i hope have external dns addresses) or external dns. Just a thought as i think our Windows 2003 server has been configured in similar fashion. Though i am trying your first comment now.
0
 

Author Comment

by:TUS11
ID: 41742820
regarding point 1 it is pointing to itself - as it is 127.0.0.1 and gateway is 192.168.1.1 which i believe is our router.

point 2 - unchecked it though again didnt understand why this is required. this should not be a problem.

point 3 - done on both server and client.

point 4 - there is a A record. verified.

your 2nd comment answer i sent you already.

After performing all this, still same error.
0
 
LVL 16

Assisted Solution

by:FOX
FOX earned 500 total points
ID: 41742827
The proper way is to set up DNS is for the workstations to get their DNS from the domain controller.  The domain controller itself resolves names from its ISP (configure forwarders)

ref link: https://support.microsoft.com/en-us/kb/323380   (same for all versions)
0
 

Author Comment

by:TUS11
ID: 41742836
thats what i was saying. Though will follow your microsoft link. But performed all steps and no luck.
0
 

Author Closing Comment

by:TUS11
ID: 41773681
Thanks alot my friend. You have been great help!
0

Featured Post

Live: Real-Time Solutions, Start Here

Receive instant 1:1 support from technology experts, using our real-time conversation and whiteboard interface. Your first 5 minutes are always free.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Find out how to use Active Directory data for email signature management in Microsoft Exchange and Office 365.
A safe way to clean winsxs folder from your windows server 2008 R2 editions
This tutorial will walk an individual through the steps necessary to configure their installation of BackupExec 2012 to use network shared disk space. Verify that the path to the shared storage is valid and that data can be written to that location:…
This tutorial will show how to configure a single USB drive with a separate folder for each day of the week. This will allow each of the backups to be kept separate preventing the previous day’s backup from being overwritten. The USB drive must be s…

785 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question