Cannot Access Domain after migrating to DFSR

Question

Hi,

I migrated from FRS to DFSR and now I am not able to access \mydomain.com if I enter it in the run box. It says the domain could not be found. I can see only SYSVOL_DFSR and not SysVol folder under C:\windows. It is a single windows 2012 DC.

Thanks.

Answer 1

recommendations for IPV6 on DCs

I'd leave it alone

after I disabled IPV6 and Re-Enabled it

This may have been bogus. When NLA starts to detect the network location, the machine will contact a domain controller via port 389. If this detection is successful, it will get the domain firewall profile (allowing for correct ports) and we cannot change the network location profile.
If the domain was not found or process failed, NLA will let you to determine which firewall profile will be used, private or public.

Since a single DC there can be a race condition between NLA and network readiness. The teaming would have also contributed to this problem. If still a problem then likely restating NLA (Network Location Awareness) would have fixed it. If there only ever is going to be a single DC (never recommended) then the longer term solution is to create a scheduled task to restart the NLA (Network Location Awareness) shortly after reboot.

--please don't forget to upvote and Accept as answer if the reply is helpful--

Answer 2

The underlying folder on the DCs that were migrated (FRS to DFSR) will be Sysvol_DFSR but the share name for all is Sysvol

The folder name and share name for new DCs will be Sysvol

Might also check the steps here.
https://techcommunity.microsoft.com/t5/Storage-at-Microsoft/Streamlined-Migration-of-FRS-to-DFSR-SYSVOL/ba-p/425405

--please don't forget to upvote and Accept as answer if the reply is helpful--

Answer 3

It worked after I disabled IPV6 and Re-Enabled it. This is strange. Whenever I restart my DC, the network card starts showing private network but after I disable and re-enable IPV6, it starts showing the correct domain name. How can I resolve this issue as I need to upgrade to Win2019 DC? I also disabled NIC teaming on this DC a few minutes ago and using only one NIC now. The used NIC is at the top under the binding settings.

Answer 4

There really should not be a need for network teaming a domain controller. Doubt that it is even worth the complication. There should not be a bandwidth issue here.

As to IPv6 are you using it and is it configured? A very common issue is there is (unknowingly) an IPv6 DHCP server on network (often a router) that hands out bogus info and confuses active directory and also NLA which is responsible for deciding the correct network profile to use. Solution here may be to turn off the router's IPv6 DHCP server.

--please don't forget to upvote and Accept as answer if the reply is helpful--

Answer 5

No, I am not using IPV6 and my DC is the DHCP Server. There is no router working as DHCP Server in the network. What are the recommendations for IPV6 on DCs if not in use and the DC is also a DHCP Server?