w32tm DC error
Franz
I am a newbie in NTP, yet have to use NTP on Windows XP. But when I try
to run "w32tm /monitor /domain:time.windows.com" there is always
the error message:
GetDcList failed with error code: 0x80070057.
Exiting with error 0x80070057
If I start monitoring "w32tm /monitor /domain:192.36.133.66" the
error is 0x800717E6, however. What does the error code mean? Is there
any description for that?
I have set the registry entries exactly like described in
http://support.microsoft.com/kb/314054/ (external time source).
But why is my local clock NOT synchronizing with the (S)NTP server?
Thank you for your help!
Regards, Franz
Ry
so I'm not sure why you want to change anything.
If you want to check how close it is, you've got your syntax messed up.
You need this
w32tm /monitor /computers:time.windows.com
But that only shows you the difference between your clock. To force it
to actually change your clock, do
w32tm /resync /rediscover
Obviously your time zone has to be set correctly, and the computer
clock needs to be within 1000 seconds of the "real" time to begin with
or Windows won't set it. And the Windows time service must be running
and set to "automatic" startup.
Also, Windows doesn't just set the time, it "slews" your clock so it
runs faster or slower until it matches the real time. So you might not
see the effects right away.
Finally, the windows time service in XP will only keep your clock to
within about 1 second of the real time. If you need better time than
that, you need to install the "real" NTP on Windows XP.
Franz
I set the configuration back to default, but when I tried command
"w32tm /monitor /computers:time.windows.com", it says (even when
the firewall is off):
time.windows.com [207.46.130.100]:
ICMP: error IP_REQ_TIMED_OUT - no response in 1000ms
NTP: error ERROR_TIMEOUT - no response from server in 1000ms
In http://support.microsoft.com/?kbid=224799 it says: "All client
desktops select an authenticating domain controller (the domain
controller returned by DSGetDCName()) as their time source."
It seems that the DC is not properly set. But I have no idea how I can
find out, which DC I am currently using and how to change the DC. My
current SNTP value is: time.windows.com,0x1
Any hint why time is not synchronizing?
Thanks in advance!
Regards, Franz
Ry
Active Directory Domain at a company or other organization, it will by
default look for time.window.com instead of a windows domain
controller.
Please run these command and send the output:
w32tm /dumpreg /subkey:parameters
w32tm /dumpreg /subkey:conifg
Franz
C:\>w32tm /dumpreg /subkey:parameters
Value Name Value Type Value Data
--------------------------------------------------------------------
Type REG_SZ NTP
NtpServer REG_SZ time.windows.com,0x1
ServiceMain REG_SZ SvchostEntry_W32Time
ServiceDll REG_EXPAND_SZ C:\WINDOWS\System32\w32time.dll
C:\>w32tm /dumpreg /subkey:config
Value Name Value Type Value Data
------------------------------------------------
LastClockRate REG_DWORD 100144
MinClockRate REG_DWORD 99894
MaxClockRate REG_DWORD 100394
FrequencyCorrectRate REG_DWORD 4
PollAdjustFactor REG_DWORD 5
LargePhaseOffset REG_DWORD 1280000
SpikeWatchPeriod REG_DWORD 90
HoldPeriod REG_DWORD 5
MaxPollInterval REG_DWORD 15
LocalClockDispersion REG_DWORD 10
EventLogFlags REG_DWORD 2
PhaseCorrectRate REG_DWORD 1
MinPollInterval REG_DWORD 10
UpdateInterval REG_DWORD 360000
MaxNegPhaseCorrection REG_DWORD 54000
MaxPosPhaseCorrection REG_DWORD 54000
AnnounceFlags REG_DWORD 10
MaxAllowedPhaseOffset REG_DWORD 1
Ry
the KB article but it does not appear when I run w32tm /dumpreg on my
own systems. Try running this command:
NET TIME /SETSNTP:time.windows.com
That should reset all of the registry values you were messing with.
Then stop and restart the Windows Time Service.
Look in the event log. If there are any warnings saying that the time
server could not be contacted, then you definitely have a networking
problem. Somehow UDP port 123 is being firewalled or otherwise blocked.
Have you tried using us.pool.ntp.org instead of time.windows.com?
Martin Burnicki
> That 0x1 after the host name looks strange; I see that documented in
> the KB article but it does not appear when I run w32tm /dumpreg on my
> own systems.
As I understand the KB article below:
http://support.microsoft.com/kb/816042/EN-US/
the flag 0x1 tells w32time to use a special poll interval which must also be
configured.
> Try running this command:
>
> NET TIME /SETSNTP:time.windows.com
>
> That should reset all of the registry values you were messing with.
> Then stop and restart the Windows Time Service.
>
> Look in the event log. If there are any warnings saying that the time
> server could not be contacted, then you definitely have a networking
> problem. Somehow UDP port 123 is being firewalled or otherwise blocked.
>
> Have you tried using us.pool.ntp.org instead of time.windows.com?
If w32time queries a real NTP server then you might have to make sure it
sends "client mode" requests to the NTP server instead of "symmetric active
mode" packets since otherwise the NTP server might just discard the request
packets without sending any reply.
Flag 0x8 can be used to force "client mode" requests while flag 0x4 can be
used to force "symmetric active mode" requests, for whatever the latter
might be required. If none of these flags is specified then w32time sends
request packets with a mode which depends on whether it runs on a DC, or
not.
Martin
--
Martin Burnicki
Meinberg Funkuhren
Bad Pyrmont
Germany
Franz
Thanks for your help. I changed the sntp, like you said, but it's still
not working. I tried to connect to some other addresses, like
europe.pool.ntp.org or similar, but still it is not working.
I also though that port 123 might be blocked, but ethereal shows that
WinXP still sends and receives NTP packets (but it might be that the
NTP packets are just send inside the group?!). In the EventViewer I did
not see any bad warnings regarding time.
the command netstat -a say the following:
[...]
UDP computer:ntp *:*
[...]
So i thought the NTP port should be ok - i cannot see port 123, but
":ntp". Is there any other command with whom i can check if port 123 is
listening or active?
Regards, Franz
Hal Murray
>the command netstat -a say the following:
>[...]
>UDP computer:ntp *:*
>[...]
>
>So i thought the NTP port should be ok - i cannot see port 123, but
>":ntp". Is there any other command with whom i can check if port 123 is
>listening or active?
The "ntp" text is probably a symbolic translation of 123.
There is probably a switch that disables that translation step.
--
The suespammers.org mail server is located in California. So are all my
other mailboxes. Please do not send unsolicited bulk e-mail or unsolicited
commercial e-mail to my suespammers.org address or any of my other addresses.
These are my opinions, not necessarily my employer's. I hate spam.
Steve Kostecke
>
>>the command netstat -a say the following:
>>[...]
>>UDP computer:ntp *:*
>>[...]
>>
>>So i thought the NTP port should be ok - i cannot see port 123, but
>>":ntp". Is there any other command with whom i can check if port 123 is
>>listening or active?
>
> The "ntp" text is probably a symbolic translation of 123.
> There is probably a switch that disables that translation step.
try 'netstat -na'
--
Steve Kostecke <kost...@ntp.isc.org>
NTP Public Services Project - http://ntp.isc.org/
Danny Mayer
If you install NTP instead of using microsoft's w32time we'd really be
able to help you. Otherwise you need to take this to a Microsoft news group.
You can install Meinberg's binary NTP kit and it should be simple to
configure and use.
you can use netstat -an |grep "123" from the DOS Command line to get a
short list of ntp ports.
Danny
_______________________________________________
questions mailing list
ques...@lists.ntp.isc.org
https://lists.ntp.isc.org/mailman/listinfo/questions
Ry
Just to make sure there's no blokcing upstream from you, can you do a
traceroute to some random internet site, then try w32tm /monitor to
each of the routers found in order? This should help you determine
where NTP is being firewalled. Not all routers provide public NTP, but
many do.
If none of those routers respond with a time offset, I'm not sure where
yo go. It is beginning to sound like you need to post to one of the MS
windows support groups. There are usually very helpful folks (some from
MS itself) on those lists.
Franz
Command "netstat -na" shows [ip-address]:123
> If you install NTP instead of using microsoft's w32time we'd really be
> able to help you. Otherwise you need to take this to a Microsoft news group.
>
> You can install Meinberg's binary NTP kit and it should be simple to
> configure and use.
I had installed Meinberg NTP server binary, but it did not work
neither. Furthermore I just need an ordinary NTP client, which gets a
synchronized NTP timestamp. I have to implement NTP then in a C++
program, which should run on ordinary Windows machines.
> you can use netstat -an |grep "123" from the DOS Command line to get a
> short list of ntp ports.
The command netstat -an |grep "123" didn't work on my machine.
*TRACE & ENVIRONMENT*
My computer is directly connected to the internet and I tried to trace
time.windows.com and europe.pool.ntp.org. As you can see in
http://www.servus-web.de/sweden/thesis/tracert.txt time.microsoft.com
timed out, but for europe.pool.ntp.org can be traced, but still the
result of "w32tm /monitor /computers:europe.pool.ntp.org" is:
europe.pool.ntp.org [82.67.125.122]:
ICMP: 94ms delay.
NTP: error ERROR_TIMEOUT - no response from server in 1000ms
*EVENTVIEWER / EVENTLOG*
Unfortunately, I missed some error messages in the EventViewer, because
they have been recently in "Application" instead of "System";
however, I don't get the reason for the error:
The description for Event ID ( 17 ) in Source ( W32Time ) cannot be
found. The local computer may not have the necessary registry
information or message DLL files to display messages from a remote
computer. You may be able to use the /AUXSOURCE= flag to retrieve this
description; see Help and Support for details. The following
information is part of the event: time.microsoft.com; A socket
operation was attempted to an unreachable host. (0x80072751); 60.
*SQL SERVER*
I read in
http://www.ntp.org/ntpfaq/NTP-s-trbl-spec.htm#S-TRBL-SPEC-WINNT that MS
SQL Server might cause problems for NTP, so I stopped SQL Server (but
did not de-install it).
*ETHEREAL*
ethereal only catches outgoing NTP packets, but no incoming NTP
packets.
So it seems that NTP packets are sent to the NTP server, but the
response packet can't reach my computer. Any idea?
Thanks in advance.
Regards, Franz
Maarten Wiltink
news:1144770918....@e56g2000cwe.googlegroups.com...
> [...] I have to implement NTP then in a C++
> program, which should run on ordinary Windows machines.
Is this a good idea? The usual procedure is to assume or demand
a good clock, which is then ensured by running a normal NTP.
Undoubtedly there's more to it than that. So can you tell us?
Groetjes,
Maarten Wiltink
Steve Kostecke
> I had installed Meinberg NTP server binary, but it did not work
> neither. Furthermore I just need an ordinary NTP client,
ntpd is _both_ a "server" and a "client".
> which gets a synchronized NTP timestamp.
You also need to discipline your clock.
>I have to implement NTP then in a C++ program, which should run on
>ordinary Windows machines.
Why re-invent the wheel? You already have an excellent "NTP client".
You just need to fix the problem that is preventing ntpd from working.
Franz
> > program, which should run on ordinary Windows machines.
>
> Is this a good idea? The usual procedure is to assume or demand
> a good clock, which is then ensured by running a normal NTP.
That's exactly what I meant. Sorry for the unclear description.
I need a clock, synchronized by NTP and then get from this clock a NTP
timestamp, which I need for the program.
Therefore I thought it would be the best to use the default NTP client
of Windows and just make sure that it really synchronizes its clock.
Regards, Franz
BigHug
What kind of Internet connection do you have? Maybe you got a slow link
or your time source was too busy. Since the error shows "no repsonse in
1000ms", try a closer stratum 1 or 2 source. You said that you have
tried Meimberg's ntpd and it doesn't work. What error message do you
get? Maybe your ISP block udp 123?
Danny Mayer
> I had installed Meinberg NTP server binary, but it did not work
> neither.
What do you mean that it did not work? What were the symptoms?
Are you running XP SP2? If so did you configure your firewall to allow
packets in both directions on 123/UDP port?
Furthermore I just need an ordinary NTP client, which gets a
> synchronized NTP timestamp. I have to implement NTP then in a C++
> program, which should run on ordinary Windows machines.
>
NTPd already does that. Why reinvent the wheel?
>> you can use netstat -an |grep "123" from the DOS Command line to get a
>> short list of ntp ports.
> The command netstat -an |grep "123" didn't work on my machine.
Did you use Command or cmd? You should be using cmd. Command is garbage.
hmm, that grep is in my own private set of binaries.
>
> *TRACE & ENVIRONMENT*
> My computer is directly connected to the internet and I tried to trace
> time.windows.com and europe.pool.ntp.org. As you can see in
> http://www.servus-web.de/sweden/thesis/tracert.txt time.microsoft.com
> timed out, but for europe.pool.ntp.org can be traced, but still the
> result of "w32tm /monitor /computers:europe.pool.ntp.org" is:
> europe.pool.ntp.org [82.67.125.122]:
> ICMP: 94ms delay.
> NTP: error ERROR_TIMEOUT - no response from server in 1000ms
>
> *EVENTVIEWER / EVENTLOG*
> Unfortunately, I missed some error messages in the EventViewer, because
> they have been recently in "Application" instead of "System";
ntpd puts them in Application because that's what it is.
> however, I don't get the reason for the error:
> The description for Event ID ( 17 ) in Source ( W32Time ) cannot be
> found. The local computer may not have the necessary registry
> information or message DLL files to display messages from a remote
> computer. You may be able to use the /AUXSOURCE= flag to retrieve this
> description; see Help and Support for details. The following
> information is part of the event: time.microsoft.com; A socket
> operation was attempted to an unreachable host. (0x80072751); 60.
>
I can't help you with w32time but it is most unlikely that it doesn't
have the necessary message file.
> *SQL SERVER*
> I read in
> http://www.ntp.org/ntpfaq/NTP-s-trbl-spec.htm#S-TRBL-SPEC-WINNT that MS
> SQL Server might cause problems for NTP, so I stopped SQL Server (but
> did not de-install it).
SQL Server? How could there be any interaction with NTP? NTP uses UDP
and SQL TCP and runs on different ports. There's no reference to SQL on
that page. Did you send the wrong URL?
>
> *ETHEREAL*
> ethereal only catches outgoing NTP packets, but no incoming NTP
> packets.
>
> So it seems that NTP packets are sent to the NTP server, but the
> response packet can't reach my computer. Any idea?
>
Which means you have a firewall in the way.
Heiko Gerstung
Franz schrieb:
> Command "netstat -na" shows [ip-address]:123
>
OK, short summary:
1. You tried two different applications for time synchronization without
success
2. You found out with Ethereal that there is no NTP reply coming in
For me it is clear that, if no NTP replies are received by your host, no
service/application using NTP will ever function properly on your
system. No matter which software you will try, even if you write your
own, it will not work until you manage to see NTP packets coming in on
your ethernet interface.
My suggestions for debugging:
- install NTP on a second PC (lets call it PC B) in your local network
(using the Meinberg Installer, of course :-))
- configure PC B to use its local clock as a time reference, start the
NTP service and wait until ntpd shows the asterisk in front of LOCAL(0)
in the ntpq billboard
- start the NTP service on your PC A and see what happens (with
Ethereal, capture filter "host ip.of.pc.b and udp port 123")
In order to speed up things
If you receive packets on port 123 from PC B to PC A, you should see
that PC A will synchronize to PC B after a few minutes. If this happens,
then NTP works fine on your PC A and you should find out who is blocking
your incoming NTP packets. Suggestions: Personal Firewall on your PC,
your Internet router or your ISP..
All other approaches are unnecessary, you need to make sure that you can
receive NTP packets, period. Good luck :-)
Kind regards,
Heiko
--
Meinberg radio clocks: 25 years of accurate time worldwide
MEINBERG Radio Clocks
www.meinberg.de
Stand alone ntp time servers and radio clocks based on GPS, DCF77 and
IRIG. Rackmount and desktop versions and PCI slot cards.
Maarten Wiltink
news:443C6916...@ntp.isc.org...
> Franz wrote:
[...]
>> The command netstat -an |grep "123" didn't work on my machine.
>
> Did you use Command or cmd? You should be using cmd. Command is garbage.
> hmm, that grep is in my own private set of binaries.
It should have been 'netstat -an |find "123"'. Command.com or cmd.exe
makes little difference here; netstat is a standalone program anyway.
(Purists would argue that you should %comspec%.)
But you're right that Windows doesn't include grep as standard, it has
find. Now _that_'s garbage. (-:
Groetjes,
Maarten Wiltink
Danny Mayer
> "Danny Mayer" <ma...@ntp.isc.org> wrote in message
> news:443C6916...@ntp.isc.org...
>
> find. Now _that_'s garbage. (-:
>
> Groetjes,
> Maarten Wiltink
>
Turns out that I picked up grep years ago and I keep it in my Utils
directory along with a bunch of other stuff. Switching between O/S's all
the time makes you forget which is native and which is addon.
Franz
I tried your test and it worked, but all time servers outside of our
university network are blocked ! So on my laptop I can synchronize time
by using command "w32tm /resyc /rediscover" (the uinveristy NTP server
as default SNTP server). It is also working with Meinberg's solution.
So it seems that the UDP port 123 is open and active on my personal
computer, but is blocked from the university's network somehow.
But is there a way to find out if you are in an university network and
are allowed to use only the dedicated NTP server (which has to be found
out as well) or if you are in an open network and can use _any_ time
server?
Regards, Franz
Danny Mayer
you ask the university's network admin what ntp server to use
Ry
reason.
First, using their internal time server saves network resources. NTP is
supposed to work in a hierarchical manner, so if they're providing you
good stratum-2 or -1 time locally, you should use that.
Secondly, and this is probably the REAL reason, is that there are many
peer-to-peer applications that try to "tunnel out" using standard
application ports. I know that some will try to use the DNS port to get
around firewalls, so it makes sense that some will try to use the NTP
port as well.
Franz
I know the NTP server of the univerity now. The problem I asked for is
maybe not realizable right now and more about theoretical nature....
For background: I am writing a C++ program, which should later be
ported to Win CE and run on Pocket PCs. So if I walk around and do not
know that my university network blocks UDP port 123 and want by default
use some external NTP server. Therefore it would be nice to have a way
to check if port 123 is blocked from a network and furthermore get the
NTP server of the local network.
But this probably has be filed in "future work" ;)
Thanks for all the help!
Regards, Franz
Richard B. Gilbert
If there is a DHCP server available, you can request the address of an
NTP server. See RFC 2131 and section 8.3 of RFC 2132. There is no
guarantee that the server will have the address of a server to give you
but it is possible to ask.