Ditto on Mitch. You need root access to get at the file that needs to be edited. Here's an excerpt from a recent email discussion. Avaya fixed it for me in minutes, no charge.
~~~~~~~~~~~~~
To fix the problem you have to modify the ntp configuration file.
When the user configures an Network Time Protocol (NTP) server on the web interface and submits the changes, the following line appears in the /etc/ntp.conf file:
"restrict default kod nomodify notrap nopear noquery"
After that, command /usr/sbin/ntpq -p fails with the following output:
"localhost.localdomain: timed out, nothing received ***Request timed out".
The problem goes away and ntpq -p command is successful when the above line is commented out or deleted from the configuration file and then NTP service is restarted.
es:
[ ]# ntpq -p
localhost.localdomain: timed out, nothing received
***Request timed out
*********************************************
[ ]# cat /etc/ntp.conf
restrict default kod nomodify notrap nopeer noquery
server 161.181.9.7
server 10.4.164.67
driftfile /etc/ntp/drift
1. Delete or commet out the restriction line in the ntp.conf file
2. Restart the NTPD service: with entering "service ntpd stop" and then "service ntpd start
~~~~~~~~~~~~~~~~~~~
Copy and paste this information into an email and send it to the technician that answers the phone. This is so new, they didn't know about it when they took my call last week. If you offer this info to them you'll do them a favor and get your problem fixed quickly.
