Displaying 3 results from an estimated 3 matches for "ntpv2".
Did you mean:
ntp2
2013 Apr 09
2
NTP doesnt work for Win2000 clients + Samba 4.0.4 (see tcpdump)
...havior (type=Nt5DS) 1st run:
------------------------------------------------------------------------------------
08:46:21.067456 IP (tos 0x0, ttl 128, id 4794, offset 0, flags [none], proto UDP
(17), length 76)
smb4testw2k.dhcp.mycompany.com.1856 > r4dv3ld002.mycompany.com.ntp:
[udp sum ok] NTPv2, length 48
Client, Leap indicator: (0), Stratum 0 (unspecified), poll 11s, precision 0
Root Delay: 0.000000, Root dispersion: 0.000000, Reference-ID: (unspec)
Reference Timestamp: 0.000000000
Originator Timestamp: 0.000000000
Receive Timestamp: 0.000000000
Transmit Timestamp: 3574467978.4359...
2013 Apr 25
2
Samba4: W2k clients cannot set / sync time with samba4 AD DC
...refer a .PCAP sniff of tcpdump I could do that,
have to do some prerequisites for that network/switch to be able to
transfer these files additionally to my computer.
> Finally, I would ask that you help yourself:
>
> 08:28:00.436507 IP 172.16.200.66.3557 > samba4srv.mysite.com.ntp: NTPv2,
> Client, length 68
> 08:28:00.436576 IP samba4srv.mysite.com > 172.16.200.66: ICMP samba4srv
> .mysite.com udp port ntp unreachable, length 104
>
> Is the NTP server set up correctly? If the clients can't contact the
> NTP server, then it doesn't surprise me th...
2013 Apr 25
1
Samba4: W2k clients cannot set / sync time with samba4 AD DC
As a follow-up to this thread
(https://lists.samba.org/archive/samba/2013-April/172892.html) I have
created an extra topic, because this is related only to NTP/time sync.
I have done some more tests on this topic, as this really hurts and I
wouldn't be able to migrate to samba4 in productional environment. We
are still using lots of W2k clients which cannot be replaced or
upgraded. Well,