Could also be the firewall blocking it. Since it takes a lot of whining to get access to the internet for each port here, and you don't know when the network guy will forget why the port was open and block it, I tend to just use our internal Windows servers as our NTP servers.
Here is one way of determining what NTP servers your windows client is using at work:
https://winaero.com/configure-internet-time-ntp-options-in-windows-10/
If you're like me you will not see the tab Internet Time. I assume this is locked down by some Windows policy. I talked to our network people. All of our DNS servers are also NTP servers.
So, what are your company DNS servers? They should appear here:
CFGTCP
12. Change TCP/IP domain information
Page down
Domain name server:
Hopefully you have multiple listed. This way when they are performing maintenance on one you'll still be working. Or if they phase one out and fail to notify you in advance you'll be ok also.
Oh, and to test if those DNS servers are still serving dns you can do the following at your windows command prompt
Nslookup someserver ipaddressofdnsserver
IBM i has a nslookup command IF you have the following loaded
5770SS1 31 5050 Domain Name System
We only have a few internal lpars with that loaded. We used to use it in our DMZ but if failed every audit because IBM was always way behind on the dns bind levels. It couldn't pass an IBM audit.
Rob Berendt
midrange.com
