FVS336G v2 Locks up with printed report

Changed 3DES to AES-128. Also changed the MTU to 1430. Had them run the report for the last several days and they all printed fine.

I am not sure which resolved the problem, but have a couple of routers (various Netgears) that absolutely will not VPN with 3DES. AES-128 is fine.

The VPN Wizard uses 3DES as the default.

I had a similar unexplained lockup occurring with the 336 at a remote office in Chesapeake, VA - about 100 miles away. It worked fine for several days at a time, then locked up. At the time, I had a FVS-338 as a spare and when I replaced the 336 with the 338, the problem went away.

A storm took out the 338 I had at the location in Richmond, VA - where I am located, and I ordered a couple more, but could only get the 336's. When I replaced the dead 338 with the 336, I had the same lockup problem, but this was the unit I pulled out of Chesapeake and was the only "working" box I had until my order arrived. When I replaced the "bad" 336 with a new one, I still had the lockup problem. As this site is local, I spent a lot of time at this site and found out that every time a certain report was printed, the 336 locked up requiring a power off reset.

I imagine a similar situation was happening in Chesapeake, but I had not connected the print job to the outage.

I also have a 336 installed in Yorktown and Williamsburg, but the reports are all most likely done by the Chesapeake office. I am going to make the MTU and AES-128 change to those as well.

Odd that 3DES and default MTU size work on the FVS-338 but not on the 336. All of them have the latest available software load.

I was beginning to think the 336's were all buggy. I have been using Netgear VPN's for nearly 9 years and have been through some really cranky and buggy software. Especially the earlier releases for the FVS-538, which is doing OK now with 3.0.6-29. I think I will leave the FVX alone.

Thanks for the help on this. I will make the AES-128 and MTU 1430 the default from now on.