Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1533
  • Last Modified:

W32Time time provider, wrong 'manually configured peer'?

I keep getting the following error message in my application event log on all machines in our domain. What is causing this and how can I fix it? Specific steps please, I've whacked my head against this for a long time now.

Event Type:      Error
Event Source:      W32Time
Event Category:      None
Event ID:      17
Date:            22.12.2009
Time:            9:55:06
User:            N/A
Computer:      SYN077
Description:
Time Provider NtpClient: An error occurred during DNS lookup of the manually configured peer ',0x1'. NtpClient will try the DNS lookup again in 960 minutes. The error was: The system detected an invalid pointer address in attempting to use a pointer argument in a call. (0x8007271E)

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
0
Synocus
Asked:
Synocus
  • 3
  • 3
  • 2
  • +1
1 Solution
 
g000seCommented:
Hi,

Check your server's DHCP settings to include the NTP to point to your Windows DC.
0
 
AwinishCommented:
Set NTP server as time.windows.com,0x1 into the registry of FSMO role holder domain controller i.ed PDC server & the Type has to be NTP
For client machine the time server has to be name of your FSMO role holder dc & type has to be NT5DS into registry.
Please take a below link to configure & also the registry parameter accordingly.
References:
http://support.microsoft.com/kb/816042
http://www.abcarticledirectory.com/Article/How-To-Set-Up-An-Authoritative-Time-Server-In-A-Windows-2003-Server-based-Active-Directory-Network/82029 
http://www.spectracomcorp.com/Support/Library/IntegrationGuides/SynchwithW32Time/Win2003domaincontroller/tabid/178/Default.aspx 
0
 
abhijitwaikarCommented:
You stated that the getting the following error message in my application event log on all machines in your domain.

Please check NTP server and NTP client configuration as per KB816042 suggested by Awinish.

If  NTP server and NTP client configuration is fine check UDP port 123 and make an exception for it.

You can made an exception using Group policy. This is located under Administrative Templates -> Network -> Network Connections -> Windows Firewall -> Domain Profile -> Windows Firewall -> Define Port Exceptions. Use the Show button and then add 123:UDP:xxx.xxx.xxx.xxx/xx, xxx.xxx.xxx.xxx/xx:enabled:W32TM. Where the x's are your IP range, i.e.: 10.10.1.0/24, 10.10.10.0/24.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
SynocusAuthor Commented:
Alright, that certainly has lead me onto the right track. I noticed that the DHCP service did not specify any NTP server at all. One question about the registry changes:

In step 6 of the registry changes in the Microsoft KB article, it specifies that MaxNegPhaseCorrection and MaxPosPhaseCorrection should be set to a reasonable value, such as 3600 or 1800.

I've checked in our FSMO role holders registry, and the value for those two are maximum possible (4294967295, i.e. 0xffffffff). Is this normal? I also suspect that some previous IT administrator may have set it to this value, as we sometimes experience anomalies in our network traffic.

What value would you recommend me to put the MaxPhaseCorrection values to?
0
 
g000seCommented:
The DC that holds the PDC emulator role holds the time on the network.   I would definitely revisit the DHCP settings for NTP to point to the DC (PDC emulator role).
0
 
g000seCommented:
Check out this link for MaxPhaseCorrection- http://support.microsoft.com/kb/884776
0
 
abhijitwaikarCommented:
Hello Synocus,

The default value of MaxNegPhaseCorrection and MaxPosPhaseCorrection is 4294967295, i.e. 0xffffffff).

As per KB and my experience please use value 3600 or 1800, and it will depend upon the poll interval value.

Thanks.
0
 
AwinishCommented:
Yes,abhijit is correct & settings given in KB is standard & should be present in authoritative time server DC..
0
 
SynocusAuthor Commented:
Hi again, now after Christmas. Hope it was merry for you guys!

I've configured the NTP setting in DHCP to point to our PDC.

I've set the PDC per the registry settings to obtain time from time.windows.com, and set the MaxNegPhaseCorrection and MaxPosPhaseCorrection to 2a300 (48 hours), per the kb 884776 article,,as well as the other registry changes that need to be made to the PDC.

However, I just noticed some odd things in one of our group policies being administered to all domain computers. Please, bear with me and explain how this would impact the time administration scenario I'm trying to implement here. Please also note that we've had some odd trouble with a new laptop sometimes completely losing accurate time; this might be related. I'm appending an screenshot of the policy entry.

Another thing: On each domain computer I've tested (my own and the problematic laptop), I've noticed that running 'net time /querysntp' returns the value mentioned in the local computers registry, i.e. time.windows.com,0x1. Is this normal in the scenario we're trying to implement?
w32time-settings.jpg
0
 
SynocusAuthor Commented:
FYI I noticed that the GPO had a space in the NTPServer name and fixed it. It was time1.mikes.fi ,0x1 when it should have been time1.mikes.fi,0x1
0

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 3
  • 3
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now