Forum Discussion
Windows Server 2016 folder share problem
- Each domain controller should at a minimum have its own static ip address plus the loopback (127.0.0.1) listed for DNS. Its fine to have the other DCs listed as well but you should add the missing "own" static address to each.
- Server3 IsmServ Service is stopped on [SERVER3]
this one could help here
https://learn.microsoft.com/en-us/troubleshoot/windows-server/identity/ismserv-not-start-when-domain-controller-starts- Diagnostic Service Host service failed to start
I believe it should be set to Manual start so you could try that.- The bigger problem is they all three complain about sysvol replication issues. The DFS Replication event logs on all three should have more details. I don't know how long this has been happening or if the tombstone has been exceeded. If so you may need to pick one and rebuild the other two. The one you keep you can try an authoritative sync to fix that before adding new ones.
https://learn.microsoft.com/en-US/troubleshoot/windows-server/group-policy/force-authoritative-non-authoritative-synchronization#how-to-perform-an-authoritative-synchronization-of-dfsr-replicated-sysvol-replication-like-d4-for-frsAlso WINS is from the days of NT and somewhat windows 2000 so I'd get rid of that confusion as it is no longer needed.
Here's the link to the files.
https://1drv.ms/f/s!AgsdgwkJ9Sjnm3nCfGbceDOHaoUm?e=exle29
Thanks for the assistance.
- Each domain controller should at a minimum have its own static ip address plus the loopback (127.0.0.1) listed for DNS. Its fine to have the other DCs listed as well but you should add the missing "own" static address to each.
- Server3 IsmServ Service is stopped on [SERVER3]
this one could help here
https://learn.microsoft.com/en-us/troubleshoot/windows-server/identity/ismserv-not-start-when-domain-controller-starts
- Diagnostic Service Host service failed to start
I believe it should be set to Manual start so you could try that.
- The bigger problem is they all three complain about sysvol replication issues. The DFS Replication event logs on all three should have more details. I don't know how long this has been happening or if the tombstone has been exceeded. If so you may need to pick one and rebuild the other two. The one you keep you can try an authoritative sync to fix that before adding new ones.
https://learn.microsoft.com/en-US/troubleshoot/windows-server/group-policy/force-authoritative-non-authoritative-synchronization#how-to-perform-an-authoritative-synchronization-of-dfsr-replicated-sysvol-replication-like-d4-for-frs
Also WINS is from the days of NT and somewhat windows 2000 so I'd get rid of that confusion as it is no longer needed.
- Hi Dave,
I cannot find the CN=SYSVOL Subscription attribute using ADSIEDIT.MSC. Is there a specific location where it may be found?
Thx,
ScottMake sure you connect to the Default naming context (at top of tree right-click Connect to) then drill in as shown below. (drill into the correct domain controller)
scottstgelais just checking if there's any progress or updates? please don't forget to mark helpful replies.