@belrpr
Couldn't find NTPtool but found this :
bd6bf5d1-dda7-4a58-9221-49065644bd7c-image.png
Ok, I insisted. Found it .... ( normally, I wouldn't even consider installing this kind of pre Windows 7 software on a Windows 11 device ... ) but ok, and sure enough :
a79816b0-c76b-437d-984c-353cc1a09f17-image.png
Port already in use ?????
WTF : this is - is it ? a client - not a server app ? A client doesn't 'bind to a port like that ..... Ditched NTP tool ....
VLANs : never used them. if set up correctly, VLANs can't be an issue ;)
Btw : what about :
34f16d7e-cfae-41a4-9ec9-df5cba7fe267-image.png
Hit start and now you see all incoming and outcoming LAN traffic using UDP on port 123 :
Client (my PC, 192.168.1.6) asking and pfSense (192.168.1.1) replying :
13:02:14.933372 IP (tos 0x0, ttl 128, id 25871, offset 0, flags [none], proto UDP (17), length 76)
192.168.1.6.52162 > 192.168.1.1.123: [udp sum ok] NTPv3, Client, length 48
Leap indicator: (0), Stratum 0 (unspecified), poll 0 (1s), 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: 3922434134.684999999 (2024-04-18T13:02:14Z)
Originator - Receive Timestamp: 0.000000000
Originator - Transmit Timestamp: 3922434134.684999999 (2024-04-18T13:02:14Z)
13:02:14.933472 IP (tos 0xb8, ttl 64, id 29204, offset 0, flags [none], proto UDP (17), length 76)
192.168.1.1.123 > 192.168.1.6.52162: [udp sum ok] NTPv3, Server, length 48
Leap indicator: (0), Stratum 3 (secondary reference), poll 3 (8s), precision -23
Root Delay: 0.026702, Root dispersion: 0.019515, Reference-ID: 0xac099600
Reference Timestamp: 3922426453.956603380 (2024-04-18T10:54:13Z)
Originator Timestamp: 3922434134.684999999 (2024-04-18T13:02:14Z)
Receive Timestamp: 3922426934.933415658 (2024-04-18T11:02:14Z)
Transmit Timestamp: 3922426934.933454875 (2024-04-18T11:02:14Z)
Originator - Receive Timestamp: -7199.751584341
Originator - Transmit Timestamp: -7199.751545124