On 8/7/2010 12:22 PM, Steve Kostecke wrote: > On 2010-08-07, Cindy Huyser <[email protected]> wrote: > >> [---=| Quote block shrinked by t-prot: 32 lines snipped |=---] >>> My configuration file is very simple: >>> >>> driftfile "C:\Windows\Temp\ntp.drift" >>> broadcastdelay 0.008 > > This has nothing to do with your IPv6 issue ... but: > > The broadcastdelay line is only necessary for configurations where a > broadcast client is not able to calculate the delay during the temporary > unicast phase of a broadcast association (e.g. over one way links). > > In your case this ntpd is not even configured as a broadcastclient, so > that line has no effect. > >>> logfile "C:\Windows\Temp\ntp.log" >>> >>> server -6 fe80::290:fbff:fe80:6aff%4 minpoll 4 maxpoll 5 iburst prefer > > Why the "%4" at the end of the address? Can you retry your configuration > without it? >
Yes, you shouldn't be using the scopeid with the IPv6 address, just the address. I already checked that on Windows XP and it is not causing the problem, though it doesn't help. >> After all this, with all due respect I wonder how much testing of this >> functionality has gone on with Windows XP? > > Such testing would require developer access to a Windows XP machine. Which Dave Hart and I have. We did most of the work here but I seem to remember someone else did some too and it may not have been tested properly at least on Windows. Steve, does it work for you on Debian Linux? Danny _______________________________________________ questions mailing list [email protected] http://lists.ntp.org/listinfo/questions
