Forum Discussion
Server 2016 Std DNS BPA Errors
There is only one ethernet adaptor:
If this were the PDC emulator then time would / should be sync'd to either a hardware clock or possibly an external known source.
w32tm /unregister
net stop w32time
w32tm /register
net start w32time
w32tm /config /manualpeerlist:xxx.xxx.xxx.xxx /syncfromflags:manual /reliable:yes /update
net stop w32time
net start w32time
then check
w32tm /query /source
w32tm /query /configuration
(replace xxx.xxx.xxx.xxx with desired source)
https://tf.nist.gov/tf-cgi/servers.cgi
If you're using integration services Time synchronization box checked then this overrides NT5DS and makes the source come from the hypervisor host only.
All domain members should use NT5DS domain time. Desktops and member servers will sync with any domain controller. Domain controllers sync with PDC emulator, PDCe syncs with either a hardware clock or possibly an external source.
Thanks very much Dave Patrick for your reply. Unfortunately the time sync didn't work. I think there is a slight sequence error in the commands. So I have changed the unregister command to be after the net stop command. I have changed the time server IP to 3.uk.pool.ntp.org which pings successfully.
The serious issue as I see it are the DNS errors. I suppose I can always set the CMOS clock accurately occasionally but any further assistance in resolving the NTP issue gratefully received..
Results below:
C:\Users\XXX-Admin>net stop w32time
The Windows Time service is stopping.
The Windows Time service was stopped successfully.
C:\Users\XXX-Admin>w32tm /unregister
W32Time successfully unregistered.
W32Time successfully registered.
The Windows Time service is starting.
The Windows Time service was started successfully.
C:\Users\XXX-Admin>w32tm /config /manualpeerlist:85.199.214.100 /syncfromflags:manual /reliable:yes /update
The command completed successfully.
The Windows Time service is stopping.
The Windows Time service was stopped successfully.
C:\Users\XXX-Admin>net start w32time
The Windows Time service is starting.
The Windows Time service was started successfully.
C:\Users\XXX-Admin>w32tm /query /source
Local CMOS Clock
C:\Users\XXX-Admin>w32tm /query /configuration
[Configuration]
AnnounceFlags: 5 (Policy)
TimeJumpAuditOffset: 28800 (Local)
MinPollInterval: 6 (Policy)
MaxPollInterval: 10 (Policy)
MaxNegPhaseCorrection: 172800 (Policy)
MaxPosPhaseCorrection: 172800 (Policy)
MaxAllowedPhaseOffset: 300 (Policy)
PollAdjustFactor: 5 (Policy)
LargePhaseOffset: 50000000 (Policy)
SpikeWatchPeriod: 900 (Policy)
LocalClockDispersion: 2 (Policy)
HoldPeriod: 5 (Policy)
PhaseCorrectRate: 1 (Policy)
UpdateInterval: 100 (Policy)
[TimeProviders]
DllName: C:\Windows\SYSTEM32\w32time.DLL (Local)
Enabled: 1 (Local)
InputProvider: 1 (Local)
CrossSiteSyncFlags: 2 (Policy)
AllowNonstandardModeCombinations: 1 (Local)
ResolvePeerBackoffMinutes: 15 (Policy)
ResolvePeerBackoffMaxTimes: 7 (Policy)
CompatibilityFlags: 2147483648 (Local)
EventLogFlags: 0 (Policy)
LargeSampleSkew: 3 (Local)
SpecialPollInterval: 3600 (Policy)
Type: NT5DS (Policy)
DllName: C:\Windows\SYSTEM32\w32time.DLL (Local)
Enabled: 1 (Local)
InputProvider: 0 (Local)
AllowNonstandardModeCombinations: 1 (Local)
No, the sequence is correct. You can ignore errors depending on the state of service. From the results above the time configuration is being overridden by a policy. However if you're moving on to other issues then please run;
- Dcdiag /v /c /d /e /s:%computername% >c:\dcdiag.log
- repadmin /showrepl >C:\repl.txt
- ipconfig /all > C:\dc1.txt
- ipconfig /all > C:\dc2.txt
- ipconfig /all > C:\dc3.txt
then put unzipped text files up on OneDrive and share a link.Hi Dave Patrick
Content not anonymised. Link herewith:
https://1drv.ms/u/s!AmMne01oSBYoixayALNeAxb9e8Dt?e=izuUW9
Thanks again.
Looks Ok to me. I'd suggest removing the router address as forwarder. There are quite a number of DCOM errors in system event log that may need attention. As to anything DNS I'd check the system event log for related errors since last boot.