Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!
Windows Server 2012 Domain error
We installed a new Windows Server 2012 to replace an existing Windows 2008 Server. We attached the Windows 2012 to the network and then ran the command to transfer the FSMO roles over to the new server, there were no error messages and the 2012 server became the new domain controller.
We turn off the old server and remove it. We go into active directory for users and computers and received the following message that is attached. "Naming Information cannot be located"
We then ran commands to seize the FSMO and AD following the steps listed here:
https://www.petri.com/forums/forum/server-operating-systems/windows-server-2008-2008-r2/52670-dns-error-after-the-upgrade
We received errors that the started with "the role owner attribute cannot be read"
The issue still persists being able to access any active directory tools. The users can still log in and everything runs.
We are at a lost, any suggestions to get this corrected is appreciated.
Thanks
AD-Error.tiff
We turn off the old server and remove it. We go into active directory for users and computers and received the following message that is attached. "Naming Information cannot be located"
We then ran commands to seize the FSMO and AD following the steps listed here:
https://www.petri.com/forums/forum/server-operating-systems/windows-server-2008-2008-r2/52670-dns-error-after-the-upgrade
We received errors that the started with "the role owner attribute cannot be read"
The issue still persists being able to access any active directory tools. The users can still log in and everything runs.
We are at a lost, any suggestions to get this corrected is appreciated.
Thanks
AD-Error.tiff
Who is Participating?
Experts Exchange Solution brought to you by
Enjoy your complimentary solution view.
Get every solution instantly with Premium.
Start your 7-day free trial.
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.
It seems there is replication issue between DCs. I will recommend first to check dns setting as suggested by seth and run dcdiag /q to get more information about the issue. Check the event log too for more details and post the logs.
Best practices for DNS client settings on DC and domain members.
http://abhijitw.wordpress.com/2012/03/03/best-practices-for-dns-client-settings-on-domain-controller/
Check the share on Windows Server2012 by net share command both netlogon and sysvol share should be available. If it not available then you may have to perform authorative and non authorative restore of sysvol.Essentially the "http://support.microsoft.com/kb/290762/" article.
Best practices for DNS client settings on DC and domain members.
http://abhijitw.wordpress.com/2012/03/03/best-practices-for-dns-client-settings-on-domain-controller/
Check the share on Windows Server2012 by net share command both netlogon and sysvol share should be available. If it not available then you may have to perform authorative and non authorative restore of sysvol.Essentially the "http://support.microsoft.com/kb/290762/" article.
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
Just have a look into the below link. It might help you.
http://exchangeonline.in/windows-server-2012-naming-information-located-because-domain-exist-contacted/
But again, you have to check the AD & DNS of your new DC. Make sure that you check as suggested by Seth.
Zac.
http://exchangeonline.in/windows-server-2012-naming-information-located-because-domain-exist-contacted/
But again, you have to check the AD & DNS of your new DC. Make sure that you check as suggested by Seth.
Zac.
The server is pointing to the proper DNS which is itself. I ran the dcdiag and it does seem to indicate unable to login to netvol or connect to it, please see the screen shot. Would you run the steps in the microsoft article or the exchange online first
dcdiag.tiff
dcdiag.tiff
Changed the sysvolready regedit setting and now sysvol is up and can run the active directory tools, how do i get netlogon to show?
Thanks much
Thanks much
As I mention before perform authorative and non authorative restore of sysvol. On healthy DC windows server i.e perform authorative restore (d4) and on windows server 2012 run non authoratived(d2) of sysvol. This will fix the issue.
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
Active Directory
From novice to tech pro — start learning today.
Experts Exchange Solution brought to you by
Enjoy your complimentary solution view.
Get every solution instantly with Premium.
Start your 7-day free trial.
understood it used the 2008 server when you first built it but once you turn it off, it should point to itself for dns
if you previously transferred the fsmo roles, no reason to attempt a seize if they are already there