From: https://social.technet.microsoft.com/Forums/windowsserver/en-US/9a5a0536-80fe-40c8-93f2-fcd12607bb83/domain-pcs-syncing-incorrect-time?forum=winserverNIS

Hi Steve,
Thank you for the post.
The time Infrastructure are 
.Domain clients/server sync time from DC servers
.DC servers sync time from PDC server
.PDC server sync time from external time source
To show the local computer time source, run command 
"w32tm /query /source".
To configure PDC external time source , run command 
"w32tm /config /manualpeerlist:time.windows.com,0x01 /syncfromflags:manual /reliable:yes /update".
You could find other time server from http://www.pool.ntp.org/ to replace time.windows.com.
If there are more inquiries on this issue, please feel free to let us know.
Regards
Rick Tan
TechNet Community Support

From: https://social.technet.microsoft.com/wiki/contents/articles/1374.event-id-129-microsoft-windows-time-service.aspx

To verify that the Windows Time service is synchronizing correctly:

Open a command prompt as an administrator. To open a command prompt as an administrator, 
click Start. In Start Search, type Command Prompt. At the top of the Start menu, right-click 
Command Prompt, and then click Run as administrator. If the User Account Control dialog box 
appears, confirm that the action it displays is what you want, and then click Continue.
At the command prompt, type 
W32TM /resync, and then press ENTER.
At the command prompt, type 
W32TM /query /status, and then press ENTER.
This command displays the status of the Windows Time service synchronization. The Last Successful 
Sync Time line of the output displays the date and time that you ran the W32TM /resync command in 
the previous step. Also, check the computer name that is shown as the Source. This should be the 
name of a domain controller (or an administrator-configured time server) in the same Active Directory 
domain as the local computer.

From: https://social.technet.microsoft.com/Forums/windows/en-US/fd63a802-2168-4c6c-955a-f8311cac4330/windows-7-not-respond-to-ping?forum=w7itpronetworking

When you only stop the firewall service, it will cause the boot-time filters to load. 
The proper way to completely stop the firewall is by **setting the service to disabled** 
in Services Manager then stopping the service through one of the GUIs or Netsh. This 
behavior is by design. 
In Windows 7, you need to disable and stop the **"Base Filtering Engine" service** firstly.
Only stop the firewall service will put you in block mode. It could be the resean why 
you cannot ping the PC.
Microsoft doesn not recommend you stop the firewall service, only if you need to troubleshoot 
some issue. This behavior will increase the security risks. 
In addition, this blog would help you:
Stopping the Windows Authenticating Firewall Service and the boot time policy
http://blogs.technet.com/b/networking/archive/2009/03/24/stopping-the-windows-authenticating-firewall-service-and-the-boot-time-policy.aspx
Regards,
Miya

From: https://blogs.technet.microsoft.com/networking/2009/03/24/stopping-the-windows-authenticating-firewall-service-and-the-boot-time-policy/

Windows 7 and Windows Server 2008 R2
In Windows 7 and Windows Server 2008 R2, you first need to disable and stop the 
“Base Filtering Engine” service. Only stopping the Firewall service as described 
above will put you in block mode.