FireFan
asked on
Windows 2012 R2 Server Joins SBS 2003 Domain But then Fails to Find It on Reboot
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?
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?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for your response!