Link to home
Start Free TrialLog in
Avatar of Forinsight
Forinsight

asked on

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

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.
ASKER CERTIFIED SOLUTION
Avatar of eexchangetech
eexchangetech
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Forinsight
Forinsight

ASKER

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?
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?
I am not sure about any buys.
You may go to properties and enable IPv6.

There won't be any problems.