Forum Discussion

Aspirant

Feb 12, 2019

Solved

FVS318N Wireless network error While loading the page critical error encountered.

This is a screenshot of the error I receive on the Radio Configuration screen on my FVS318N Router. When this error occurs, I am unable to connect new devices to the wireless network. All currently connected devices stay connected. I have to reboot the router to resolve the issue. Within an hour after reboot, the error again appears and the issue reoccurs. I tried to fix by upgrading the firmware to ver 4.3.5-3. Is anyone aware of a fix for this issue even though this model is discontinued?

Troubleshooting

ehirsch
Feb 19, 2019
Thanks. I just gave up on it and set up an Aruba device so we could get the wireless network accessible again. Right now this will work for what we need.

7 Replies

JohnC_V
NETGEAR Employee Retired
Feb 14, 2019
Hi ehirsch,

Welcome to our community! :)

It seems that you are having issues with your FVS318N. May I know what you did to show this error message? Did you just go to the Radio Settings and it did show this error? You may try to reset the firewall to factory default setting and check if it will show the same issue.

Regards,
- ehirsch
  Aspirant
  Feb 14, 2019
  I noticed the problem when I had trouble connecting devices to the wireless network. The network was visible but it kept rejecting the network password. I first saw the error when I went to the web client to investigate. As I wrote, rebooting the router temporarily resolved the problem and then the error reoccurred. I will try to reset the firewall back the factory settings and respond with the result.
  - ehirsch
    Aspirant
    Feb 14, 2019
    We use this router for the wireless networking function only. It doesn't use DHCP to generate IP Addresses. I did set the router back to factory settings and reconfigured the wireless networks. after about 15 minutes, the error came back. Then I just reloaded the backed up settings that I saved before I started. as of now 11:38 AM EST have no error but I will look at it in a few minutes. As off 11:49 AM still no error.An Hour later at 12:48 PM Still no error.