NETDDE error from MS time server

[- Bobb -]

Anyone else got this ?
Last night I noticed my network icon blinking while I wasn't doing any
network activity - 2 bytes at a time - on and on.
If I blocked via firewall it just stopped - no issue/popup - error
reported from Zonealarm.
Today I noticed again and checked event log - got NETDDE errors at
startup today = the default XP time servers have not responded. I
changed mine to another ( found a list at
http://tf.nist.gov/timefreq/service/time-servers.html ) and updated
fine. Might want to check yours. ( I had time.windows.com checked and
tried the other - time.nist.gov - both failed ) OK now.
I thought it was maybe due to changing the clocks ahead in March this
year, but went back and got this on April 9th as first instance ( In
the error 'time.windows.com,0x1' is being considered as MANUALLY
configured - by Microsoft - not by me)

Event Type: Error
Event Source: W32Time
Event Category: None
Event ID: 17
Date: 4/9/2007
Time: 5:14:51 PM
Description:
Time Provider NtpClient: An error occurred during DNS lookup of the
manually configured peer 'time.windows.com,0x1'. NtpClient will try the
DNS lookup again in 15 minutes. The error was: A socket operation was
attempted to an unreachable host. (0x80072751)

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

 

[Curt Christianson]

Hi Bobb,

Short answer, yes, I've had problems connecting too lately. It doesn't
bother me as I've been using nistime-32bit.exe from
http://tf.nist.gov/service/its.htm for years. You did get me thinking
though, and I found an interesting read, but the "real" info. is within the
links here:

Windows Time Service Technical Reference
http://technet2.microsoft.com/Windo...e5f7-41b3-b0e8-240f8236e2101033.mspx?mfr=true

--
HTH,
Curt

Windows Support Center
www.aumha.org
Practically Nerded,...
http://dundats.mvps.org/Index.htm

 

[- Bobb -]

I just thought it strange that the time servers - provided by Microsoft
for XP - gave errors. My Pc is up to date, yet NTP was not working: so I
gather that all XP pc's having that error also - and no one at Microsoft
noticed ?? / fixed it ?
That's why I mentioned - just to let others know that it wasn't a
problem with their pc.

Bobb