search

microsoft / W32Time

This repo provides resources for high accuracy time on Windows
MIT License
71 stars 23 forks source link

Must be able to configure/specify interface for multicast join #9

Open mwtrigg opened 3 years ago

mwtrigg commented 3 years ago

On machines with multiple interfaces, we lack the ability to control on which interface the time service joins the multicast group. This occasionally leads to occasions where the time service joining the appropriate multicast group on the wrong interface (or on one physical interface of a teamed adapter), which inevitably cause the service to fall back to local CMOS clock.

izmmisha commented 3 years ago

https://github.com/Microsoft/SDN/issues/292#issuecomment-772502451

To anyone struggling with getting multicast working, you might need to add the following reg key ChosenMcastIfIpAddr:IP_OF_YOUR_INTERFACE.

mwtrigg commented 3 years ago

Thanks for the tip!

We've already had the last straw and moved to a paid solution which allows this, documents this, and allows fallback to ntp.

I am very grateful you shared this and hope it helps somebody who found their way to this issue!

izmmisha commented 3 years ago

probably way of this discovery described at https://github.com/microsoft/SDN/issues/471

Now for some reason this reg key is not mentioned on MSDN ptp article, i was only able to find it by looking at w32time logs

izmmisha commented 3 years ago

BTW windows server 2019 have no such parameter :(

sunlock21 commented 2 years ago

Server2019's ptpprov.dll meybe some bugs, you can copy from win10 the same name dll,and in reg set its path name will ok.