Solved

Windows 8 pro and enterprise fail to join Windows server 2012 domain controller

Posted on 2013-07-01
4
1,265 Views
Last Modified: 2013-07-02
Windows 8 pro and enterpise editions fail to join
Windows server 2012 with the error code 1355. DNS does not exist. But
I can ping both the server and the workstation. I was able to join Windows 7 pro workstation
to the same domain fast and easy.

one subnet

Windows Server 2012 Standard
192.168.0.0/24
server name & domain controller  : dcapps   dcapps.corp.janicelakes.net
domain controller: 192.168.0.110 (static)
dns & dhcp: 192.168.0.110
gateway: 192.168.0.1
able to  join the following:
Windows Server 2012 Standard > server name: dalakes    dalakes.corp.janicelakes.net
ip: 192.168.0.120 (static)
Windows 7 Pro:  client name: taxexp     taxexp.corp.janicelakes.net
ip: 192.168.0.56 (DHCP) same DNS AND gateway

ISSUE: Can not join both Windows 8 Pro and Enterprise to the DC > dcapps.janicelakes.net with the error code 1355.
0
Comment
Question by:Forinsight
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
  • 2
4 Comments
 
LVL 2

Accepted Solution

by:
eexchangetech earned 500 total points
ID: 39291794
On Windows 8, uncheck IPv6
Start CMD
ping dcapps
dcapps.corp.janicelakes.net

If you have multiple DNS in Windows 8 client, configure 192.168.0.110 as primary
0
 

Author Comment

by:Forinsight
ID: 39291837
before i do your advice, let me tell you that it's mandatory for me to use also
ipv6. how do i bring back ipv6 then without messing my net and domain configuration?
0
 

Author Comment

by:Forinsight
ID: 39293901
I've requested that this question be closed as follows:

Accepted answer: 0 points for Forinsight's comment #a39291837

for the following reason:

exactly as  specified my windows 8 pro and enterprise seamlessly connected and joined the domain controller on Windows Server 2012 Standard under hyper-V. how i wish you would tell me why it was so. is this a bug? what happens now if i revived the ipv6 on my clients?
0
 
LVL 2

Expert Comment

by:eexchangetech
ID: 39294676
I am not sure about any buys.
You may go to properties and enable IPv6.

There won't be any problems.
0

Featured Post

Free eBook: Backup on AWS

Everything you need to know about backup and disaster recovery with AWS, for FREE!

Question has a verified solution.

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

Understanding the various editions available is vital when you decide to purchase Windows Server 2012. You need to have a basic understanding of the features and limitations in each edition in order to make a well-informed decision that best suits y…
Resolve DNS query failed errors for Exchange
In this Micro Tutorial viewers will learn how to restore their server from Bare Metal Backup image created with Windows Server Backup feature. As an example Windows 2012R2 is used.
With the advent of Windows 10, Microsoft is pushing a Get Windows 10 icon into the notification area (system tray) of qualifying computers. There are many reasons for wanting to remove this icon. This two-part Experts Exchange video Micro Tutorial s…

688 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