The Site > Old Forums > Cayman > 3220-H not getting time from time-a.nist.gov

3220-H not getting time from time-a.nist.gov

I can't even get to the site.

reply to Dunsel
I am experiencing the same problem. The router now shows elapsed time instead of UTC. I contacted Netopia, but have no answer so far.

reply to Dunsel
How 'bout trying just time.nist.gov
That's what I'm using.

reply to Dunsel

How 'bout trying just time.nist.gov

reply to Dunsel
I got a reply about this from the people at NIST today and thought that I'd share it here:

Subject: Re: Is time-a.nist.gov (129.6.15.28) not working anymore?
From: Judah Levine
Date: Mon, 26 Apr 2004 15:13:33 -0600 (MDT)

Hello,

> My network's router cannot obtain the time from the time-a.nist.gov
> (129.6.15.28) internet time server anymore, since about a week ago.

This system is up and running, but it is very busy and is dropping
some requests.

> My equipment (Netopia Cayman 3220-H DSL Router) seems hard-wired to
> regularly contact the 129.6.15.28 IP address for its UTC time
> synchonization.

This is most unfortunate. Apart from failures, ip addresses change
from time to time, and having a hard-wired ip address is very definitely
not an optimum strategy.
I hope to be able to upgrade this system in the next few weeks,
and that will solve the problem -- at least for now.

> Do you think I should encourage my router's manufacturer
> to impliment a time checking routine which would be more tolerant...

Absolutely. It would also be a friendly act if they distributed the
requests among all of our servers instead of pointing all of the
hardware devices to the same one.
There are a "best practices" documents that address this issue.
You could encourage them to look at the material published by David
Mills of the University of Delaware (www.eecis.udel.edu/~mills/reports.html.

Judah Levine
Time and Frequency Division
NIST Boulder

Netopia does not seem too interested in patching the firmware. This is Netopia email response:

Thanks for your email. I'm sorry to say that you cannot change any of the NTP settings on a 3220. Best wishes.

Netopia products and services include DSL, T1, Frame Relay, VPN, and Analog Equipment, as well as service delivery software such as parental control, eSite and eStore hosting, Timbuktu remote control, eCare virtual support, and the netOctopus software suite for remote gateways and PC
administration.

Netopia, Broadband Without Boundaries
DSL, Frame Relay, and Analog Equipment Technical Support
E-MAIL: techsports@netopia.com
WWW: »www.netopia.com/en-us/support
FTP: »ftp://ftp.netopia.com/pub
PHONE: 510-597-5400 Mon. - Fri. 6AM-5:30PM Pacific Time

yeah, i don't think they wil have another firmware for the 3220 as it is pretty much a dead line. damn good unit, piss poor firmware support!

reply to public

said by public:

---

Netopia, Broadband Without Boundaries

---

reply to Dunsel

said by Dunsel:

---

Recently, my 3220-H doesn't seem to be able to get the UTC time setting from time-a.nist.gov anymore when the modem restarts. I was wondering if it is just my modem or ISP having this problem, or if I could just configure the 3220-H to use a different time server than time-a.nist.gov (129.6.15.28) if it is the time server that's down. (Or should I just wait for US Gov to fix that time server?)

I've rebooted and unplugged the Cayman, and in every other way it is seems to be working normally. I couldn't see a setting for the time server in the web interface. I can see the 129.6.15.28 (time-a.nist.gov) address in the IP route cache after the modem restarts so it looks like the Cayman is at least trying to get the UTC time when it restarts.

(You know, it is nice that this is the ONLY problem I've had with the 3220-H in 2 years. And it really isn't even a very significant problem.)

---

reply to Dunsel
Mine started working again at last reboot - ?

said by jwalker019:

---

Mine started working again at last reboot - ?

---

I'm running a 3386-ENT witn f/w 8.3.3R0 and noticed in the log that it isn't connecting to the NTP server. I don't know if it is related to my enabling the basic firewall and restarting it or not.

reply to Dunsel
I was having the same problem with my 3546, but it is working again.:)
--
»www.mozilla.org/products/firefox/

reply to Dunsel
When all else fails, read the firmware manual, f/w 8.3.3R0:

Note: NTP can be blocked by some firewall configurations. To ensure that this feature works, create a filterset
rule to allow UDP port 123 to be open.

reply to Dunsel
»nist.time.gov/timezone.cgi?Pacific/d/-8/java

reply to public

said by public:

---

Maybe there is hope after all. If only everybody requested a patch....

---