This is nuts, I know. But I cannot get my new Netgear switch, to pick up the time from the time server used on the LAN. I've tried both CLI and GUI, I can't work out what it needs.
The LAN has a dedicated NTP server, which is working. I've tried every combination of settings to get the switch to pick up time from it, and followed Netgear guides as well as pages found online, but it sits at "local" and doesn't sync to the time server whatever I seem to do.
I'm not sure if that is because the local time server is NTP not SNTP, but all the examples show it syncing to a normal NTP pool, so it's probably fine. Ideally I would have thought it would autodetect the NTP settings and server from LAN DHCP params when it checks DHCP, but it isn't doing that either.
When I enter the settings, I can get a long "waiting" screen, but it always shows "local" even after waiting many minutes.
The setup I have would simply need a broadcast NTP request (the NTP server just has an IP, which could vary in future; there's no DNS on this LAN subnet). Surely it's not that complicated but I just can't find what it needs to make it work.
Rather than posting things that failed, I'd like to just ask what I have to do, to make it work.
This is the current config pages:
After @Ramhound's comment below (which was helpful, thank you!), I have come to the conclusion that the issue could be that the setting "routing mode" is incorrect. My basis for this is that although it's on the correct subnet/broadcast domain NTP broadcasts just aren't reaching the NTP server, and "ping" on the switch to the NTP server isn't getting a reply either.
(However it managed to send a DHCP request and reply without issue to the exact same server, no problem there? The switch and NTP/DHCP server are also definitely on the same subnet - I just rechecked - so broadcast should work?)
I think that might imply it doesn't know how to send packets to the server for NTP/PING purposes and so it isn't trying to send them (or is sending on the wrong ports), probably that would be a routing issue? But if so, why did DHCP work but NTP/PING not? I don't know. There's probably a good reason. I don't understand the "routing mode" setting enough to know if it should be enabled or disabled. Right now it's disabled, the switch default.