Solved

Windows 2012 R2 Server Joins SBS 2003 Domain But then Fails to Find It on Reboot

Posted on 2014-03-17
2
443 Views
Last Modified: 2014-03-18
Greetings!

We're adding a new Win 2012 R2 member server to an existing SBS 2003 domain. It successfully joins the domain, but on successive reboots fails to id the network as a domain network and so it defaults to a "Public" network and fails to authenticate to the DC. On each reboot, in the Event Viewer, the NIC shows that it is "disconnected" and then 6 seconds later Netlogon reports that it can't find a DC.  We've experimented with adding "Netman" as a service that Netlogon depends on, but have not had any luck. The NIC has the newest available driver.  

Any advice?
0
Comment
Question by:FireFan
2 Comments
 
LVL 57

Accepted Solution

by:
Cliff Galiher earned 500 total points
ID: 39935750
The fact that NLA is reverting back to a public network os extremely concerning. I'd be very suspicious of a significant hardware issue in such circumstances.
0
 

Author Closing Comment

by:FireFan
ID: 39938318
For the record, it turned out to be missing records in DNS.  All of the Resource Records were missing.  Once I forced the SBS server to register itself in DNS they were recreated and all was right in the domain.

Thanks for your response!
0

Featured Post

Ransomware-A Revenue Bonanza for Service Providers

Ransomware – malware that gets on your customers’ computers, encrypts their data, and extorts a hefty ransom for the decryption keys – is a surging new threat.  The purpose of this eBook is to educate the reader about ransomware attacks.

Question has a verified solution.

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

Suggested Solutions

The recent Microsoft changes on update philosophy for Windows pre-10 and their impact on existing WSUS implementations.
A procedure for exporting installed hotfix details of remote computers using powershell
In this Micro Tutorial viewers will learn how they can get their files copied out from their unbootable system without need to use recovery services. As an example non-bootable Windows 2012R2 installation is used which has boot problems.
This tutorial will walk an individual through the process of configuring basic necessities in order to use the 2010 version of Data Protection Manager. These include storage, agents, and protection jobs. Launch Data Protection Manager from the deskt…

808 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