With the fact that it slowly 'catches up' last night I adjusted the time to be within 2 minutes of current time hoping that it would 'catch up' more quickly. As of this morning it's still at 2 minutes behind, so no joy....

I'm reading that if it is off only by a few minutes it slowly changes the clock to run faster until it 'catches up'.

Check again in the AM and report back.

Goodnight all.

Just using pool.ntp.org now.

Getting this:
The system time has changed to ‎2017‎-‎07‎-‎26T03:59:47.234000000Z from ‎2017‎-‎07‎-‎26T03:59:47.247242200Z.

But it's still 7 minutes behind...

Interesting... this just popped up in the log as well:

Time Provider NtpClient: No valid response has been received from manually configured peer 3.pool.ntp.org,0x8 after 8 attempts to contact it. This peer will be discarded as a time source and NtpClient will attempt to discover a new peer with this DNS name. The error was: The peer is unreachable.

The time provider NtpClient is currently receiving valid time data from 3.pool.ntp.org,0x8 (ntp.m|0x8|0.0.0.0:123->69.50.219.51:123).
The time service is now synchronizing the system time with the time source 3.pool.ntp.org,0x8 (ntp.m|0x8|0.0.0.0:123->69.50.219.51:123).

Result of /sync command.

I can't get into the BIOS right this minute. I am currently remoting into the server and would have to schedule downtime to check. Shouldn't Windows time and BIOS time be the same? (Sync with each other)

UT has the correct time. I am able to Telnet to pool.ntp.org port 123 (I don't get anything on the screen, but it connects via Putty)

From what I have read UT is open from LAN to WAN by default. So I believe so.

Physical box (no VM).

I looked at the link you referenced but not sure that is 100% applicable as it's talking about /etc folders.

I have a DC running Windows Server 2012 R2. It's behind a Untangle firewall.

I can't get it to maintain time for some reason. My understanding is that outbound traffic isn't blocked with Untangle.

I have set up several servers for NTP sync and not run into this many issues. It says it's successful but is 7 minutes off.

Any ideas?

[Configuration]

EventLogFlags: 2 (Local)
AnnounceFlags: 5 (Local)
TimeJumpAuditOffset: 28800 (Local)
MinPollInterval: 6 (Local)
MaxPollInterval: 10 (Local)
MaxNegPhaseCorrection: 172800 (Local)
MaxPosPhaseCorrection: 172800 (Local)
MaxAllowedPhaseOffset: 300 (Local)

FrequencyCorrectRate: 4 (Local)
PollAdjustFactor: 5 (Local)
LargePhaseOffset: 50000000 (Local)
SpikeWatchPeriod: 900 (Local)
LocalClockDispersion: 10 (Local)
HoldPeriod: 5 (Local)
PhaseCorrectRate: 7 (Local)
UpdateInterval: 100 (Local)

[TimeProviders]

NtpClient (Local)
DllName: C:\Windows\system32\w32time.DLL (Local)
Enabled: 1 (Local)
InputProvider: 1 (Local)
AllowNonstandardModeCombinations: 1 (Local)
ResolvePeerBackoffMinutes: 15 (Local)
ResolvePeerBackoffMaxTimes: 7 (Local)
CompatibilityFlags: 2147483648 (Local)
EventLogFlags: 1 (Local)
LargeSampleSkew: 3 (Local)
SpecialPollInterval: 3600 (Local)
Type: NTP (Local)
NtpServer: 0.pool.ntp.org,0x8 1.pool.ntp.org,0x8 2.pool.ntp.org,0x8 3.pool.ntp.org,0x8 (Local)

NtpServer (Local)
DllName: C:\Windows\system32\w32time.DLL (Local)
Enabled: 1 (Local)
InputProvider: 0 (Local)
AllowNonstandardModeCombinations: 1 (Local)

Windows Time Agent (Local)
DllName: w32tmdt.cpl (Local)
Enabled: 1 (Local)
InputProvider: 0 (Local)
VMICTimeProvider (Local)
DllName: C:\Windows\System32\vmictimeprovider.dll (Local)
Enabled: 0 (Local)
InputProvider: 1 (Local)

Leap Indicator: 0(no warning)
Stratum: 2 (secondary reference - syncd by (S)NTP)
Precision: -6 (15.625ms per tick)
Root Delay: 0.0312500s
Root Dispersion: 16.0100000s
ReferenceId: 0xCC093677 (source IP: 204.9.54.119)
Last Successful Sync Time: 7/25/2017 4:59:17 PM
Source: 1.pool.ntp.org,0x8
Poll Interval: 6 (64s)

For a server

How often should you replace your UPS units (the unit itself not the batteries)? Is there a 'best practice'?

That sounds familiar! Would be a great feature.

Thanks!

@scottalanmiller LOL... Yeah I was getting that you are a huge VM fan from the other posts. Just curious, are you a Hyper-V or a VMware fan?

@scottalanmiller Yeah, I do VM on almost all new servers I set up.

@scottalanmiller Ok, I'll try a different GPU and see what happens.

@scottalanmiller Legacy is right. This is an DB application that still uses delphi and is a flat file database.

@scottalanmiller said in Blue Screen (not BSOD) when using mouse in Windows Server 2012:

@CCWTech said in Blue Screen (not BSOD) when using mouse in Windows Server 2012:

Could be the GPU, but it's only certain things that trigger the problem. Almost all right clicks (if not all) don't work and most left clicks work but not all.

That actually suggests GPU. GPUs failing like this will often fail on certain system calls, which would only happen from certain applications or actions.

It's going to take some convincing to get DELL to replace the system board. Would a different video card be a good test or if the onboard GPU is a problem would it most likely still have an issue because it's still a device on the server?

It's their only server (very small business) so it's the DC/DNS/DHCP and application/file server. It's a pretty basic box but this is happening even when the place is closed so I don't think it's a performance issue. The box wouldn't likely be hearty enough to go VM and isn't very up-gradable.

Unfortunately because it's their applications server, their main app they use requires a right click to get into the settings to interact with several of it's features, so this is causing a significant impact. PS won't work with that app.

Could be the GPU, but it's only certain things that trigger the problem. Almost all right clicks (if not all) don't work and most left clicks work but not all.