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.
Since you have Server 2016 (oldest) and windows 10 desktops you should be using SMBv3
Overview of file sharing using the SMB 3 protocol in Windows Server | Microsoft Learn
How to detect, enable and disable SMBv1, SMBv2, and SMBv3 in Windows | Microsoft Learn
- Both SMBv2 & SMBv3 are enabled on this 2016 server. This server also has an issue with Windows Backup using a network share. I have run the Network Troubleshooter, but it found nothing wrong.
Please run;
Dcdiag /v /c /d /e /s:%computername% >C:\dcdiag.log (run on PDC emulator)
repadmin /showrepl >C:\repl.txt (run on **any** domain controller)
ipconfig /all > C:\%computername%.txt (run on **EVERY** domain controller)
ipconfig /all > C:\problemworkstation.txt (run on problem pc)
Also check the domain controller System and Replication (DFS or FRS) event logs for errors since last boot. Post the Event Source and Event IDs of any found. (no evtx files)
then put unzipped text files up on OneDrive and share a link.- Hi Dave,
Here's the link to the files.
https://1drv.ms/f/s!AgsdgwkJ9Sjnm3nCfGbceDOHaoUm?e=exle29
Thanks for the assistance.
