Windows seems particularly prone to NTP errors, because the default server is MicroSoft's and apparently sucks.
Try:
pool.ntp.org
time.google.com
The first is an internet community alias which will get time from a reasonably near public server. It does add load to servers which may not be amply funded.
See also: http://support.ntp.org/bin/view/Servers/NTPPoolServers
The second is offered by Google which can certainly afford (won't notice) the load.
There are issues if you want PRECISE time. Google smeared the recent leap-second, apparently differing from other services. However until recently Windows' internal timer was not even good for a second? And if you are 7 minutes out, getting to within a few seconds is much better.
BTW, some encryption protocols expect the time to be correct within 5 minutes. This is to deter "replay attack". Your 7 minute drift may have been causing oddness. (Or not.)