Re: time server problem
- From: freeck <freeck2@xxxxxxxxxxx>
- Date: Thu, 6 Dec 2007 13:13:27 -0800 (PST)
On 6 dec, 21:41, "Paul G. Tobey [eMVP]" <p space tobey no spam AT no
instrument no spam DOT com> wrote:
And the docs are wrong... When you do what the docs say and it doesn't
work, refer to the code itself. I believe I gave you the location of the
server code previously, no?
In the case of the multicast value, it can be a) a REG_DWORD that contains
the 32-bit IP address (IPv4, obviously), of the group to send to;
172.16.12.1 = 0x010c10ac (not that this is a valid multicast address, of
course), b) a REG_SZ that gives a single group to send to, or c) a
REG_MULTI_SZ which gives a list of groups to be sent to. The code is quite
clear that, unless 1 is a multicast group, it's not a valid value for that
registry entry. The code has a much harder time about being wrong about
what it does than the documentation does. The code might have bugs in it,
but it faithfully describes what it's doing.
The multicast period is DOCUMENTED IN THE CODE! What were you expecting me
to say? Use the Send Feedback link on the help page that documents the
registry settings to indicate to the docs team that the documentation is
wrong and incomplete.
Paul T.
"freeck" <free...@xxxxxxxxxxx> wrote in message
news:08fc8851-c49a-4f42-bf1d-d23750a6057a@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On 6 dec, 20:26, "Paul G. Tobey [eMVP]" <p space tobey no spam AT no
instrument no spam DOT com> wrote:
Well, just from a quick read of the code, which you have, too (hint,
hint),
it's clear that you have set the multicast period to an invalidly small
value. The minimum value is 5*60*1000 (five minutes).
Further, you've given it the wrong information in the multicast registry
value. That should be the list of multicast groups to send to, not "1".
All of this would have shown up in the serial debug messages, if you were
running on a debug build of the OS...
Paul T.
"freeck" <free...@xxxxxxxxxxx> wrote in message
news:e69b817a-fc2d-42a0-be3b-c63bc1c7712e@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi there,
Still having problems using the time server of CE5.0.
I have updated the latest fixes in PB5.0. I have set the following
registry settings in the CE-target:
Index 0
Prefix NTP
Keep 1
Order 153
Dll timesvc.dll
Context 0
ServerRole 1
Multicast 1
MulticastPeriod 2000
TrustLocalclock 1
The timesvc service is running. One should expect receiving multicast
messages each 2 second..not?
But the ethernetsniffer does'nt show any actvity.
Any idea why?- Tekst uit oorspronkelijk bericht niet weergeven -
- Tekst uit oorspronkelijk bericht weergeven -
Paul, Thanks for the quick response.
But this is what I read in the PB-help...
1: Multicast : REG_DWORD Specifies the IPv4 address for multicast
mode. Setting this value to 1 turns on the multicast server.
2: Multicastperiod : REG_DWORD Specifies the interval between
subsequent multicasts.
Then I do not understand why I did it wrong.... which IP- adres is
required (something like 192.168.2.255?) ,
what's the effect of setting the "value to 1"
Multicastperiod : Is the minimum period documented somewhere?- Tekst uit oorspronkelijk bericht niet weergeven -
- Tekst uit oorspronkelijk bericht weergeven -
Paul,
I did not realise that the documenation of MS is as bad as you
describe. From now on I will look into the code first.....
Thank you very much for response, your information was most
helpfull.
Freeck
.
- Follow-Ups:
- Re: time server problem
- From: Paul G. Tobey [eMVP]
- Re: time server problem
- References:
- time server problem
- From: freeck
- Re: time server problem
- From: Paul G. Tobey [eMVP]
- Re: time server problem
- From: freeck
- Re: time server problem
- From: Paul G. Tobey [eMVP]
- time server problem
- Prev by Date: Re: Saving and restoring touch screen calibration data.
- Next by Date: Re: time server problem
- Previous by thread: Re: time server problem
- Next by thread: Re: time server problem
- Index(es):
Relevant Pages
|
