NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
RAX200 1.0.2.98 Firmware
Did anyone update their RAX200 to 1.0.2.98 firmware? If so, is everything working as it should? Thanks
- I still have IPV6 issues. Reloaded firmware 1.0.2.8. This was the last update that work for IPV6. The latest updates have IPV6 issues.
Has anyone had any issues with the router’s Real-Time clock since upgrading to v98
The router clock no longer updates with the result scheduling does not take place at the appropriate time.
I have completely reset the router to default parameters after the update, but the clock is set to some random time and stuck even when the NTP server is changed and/or the time zone is reset. I suspect it is something to do with NETGEAR’s automatic time zone detection algorithm. Is there any way to switch that off?
I have had issues with Attached Devices page no updating properly. Indicating devices are attached when they have been off for hours.
You're right. It's 1100 am local here on the 4th and the NTP set at Netgear shows 0930 on the 3rd. I always set the correct time zone but never paid attention to the time. more than a day off.
I updated the firmware over the weekend. Yesterday I noticed that the date on the router was wrong. I had the NTP server set to Netgear's default. I switched to another one, but it made no difference. I rebooted the router and saw that the date got corrected. But some time later I saw the time was frozen to the time I rebooted the router. This morning when I logged into the router again, I saw the date was still set to yesterday and the time was still set to the time of the router reboot. All entries in the log were set to the same date/time. I strongly suspect the updated firmware caused the problem.
- How do you Check and set the time? Where can I find it on the menus?
ThanksLog into the administrator interface, then Advanced => Administration => NTP Settings.
You can't set the time directly, but you can specify the time zone and NTP server, as well as seeing what date/time the router thinks it is.
Loaded V1.0.2.102_1.0.56 today, it appears to have fixed the time issue. I haven't noticed any problems in the hour or so since I installed it, bt of course it's early days
- Thanks,
Installed early AM, did a restore to default afterwards. Set it up, did some checks, we’ll see.........
- Yep along with IPV6 issues
Yeah, I just saw your posts on them. I'm preparing to do a factory reset, then restoral of my settings, to see if this fixes the date/time issue, since I can't see how to reach Netgear to get them to fix their faulty update (my ISP hasn't gone to IPV6 yet). But it's too hot for me to fool around with this now.
Yes the dates are wrong. Also I am not sure if the IPV6 issues is connected to that or it is the same ongoing issue from firmware 1.0.2.88 on. I the clock was OK until the 1.0.2.98 update which killed the clock. It all worked up to and including firmware update 1.0.2.8. So as Netgear pushes out updates they are adding more and more problems without fixing existing issues. Bad Software/Hardware Quality Control. No more Netgear for me. I just went and brought an ASUS GT-AX11000 gaming router. No problems at all. So easy to set up and IPV6 runs without a hitch. Now using the RAX200 as an Access Point which IPV6 setting are not used only the main router setting connected to the access point need it. An expensive access point at that. But I am stuck with it. The product return period has came and gone. Netgear support kept telling me they will resolve the issue. Well it is 4 months and 3 firmware updates later still bad IPV6 including a bad clock. I need and use IPV6 . Your provider will be going to it soon. They might already have it but you will never know if you are trying to connect with the RAX200 or any RAX routers with the same firmware update. If you have an older Netgear router like the 8000 or 8000P they still work on IPV6. Maybe your provider might have it IPV6. Supposedly all the providers now support it in one form or another.
John
