NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Marksmt
Feb 28, 2017Aspirant
FVS336Gv3 Weird Problem - VPN stuck and possibly blocking DMZ + DHCP on Port 4 ?
Hi I wonder if anyone has come across this. Just replaced a UTM-25 with a FVS336G v3 with firmware version: 4.3.4-2 which has been perfectly stable for about a month or so. Came to work this morni...
- Mar 02, 2017
Hi
Thanks for the suggestion. Unfortunately, I went down this route with the UTM-25 and don't really have the luxury of continued disruption in the office doing the same with this new FWR so I've managed to get an RMA on the unit and have reverted back to the UTM-25 for the time being.
I've seen posts elsewhere on the net suggesting the clock skew issue was related to faulty PSU bricks. I guess only the tech guys who look at the returned unit will know. Hopefully there will be a new firmware release soon. It seems odd that it was perfectly stable for several weeks then seems to have thrown a complete "wobbler" in recent days. It resides on a surge protected UPS and the other equipment in the rack is fine
If the new unit fails the same way I'll have to look at an alternative product
Regards
SamirD
Mar 10, 2017Prodigy
Did you perform any type of firmware update or any other change prior to this behavior? It's odd for these units to go that far off the rails like that.
- MarksmtMar 10, 2017Aspirant
No, no updates or changes after testing and final commissioning.
if this information helps anyone else...
It was upgraded to latest firmware as a precautionary measure and tested. There was an initial hiccup on first install, whereby it wouldn't resolve DNS and first rollout was abandoned + reverted, (fixed by changing LAN DNS from our ISP's DNS to Google 8.8.8.8). As a DNS issue was acknowledged by our ISP I assumed this was down to them, but I now believe this was coincidental and that for some reason the FVS unit wouldn't resolve our original DNS. I noticed that Wireless LAN going via the DMZ would resolve ok at the time, but workstations on the LAN would not. This was because I had copied over the original config correctly and whoever set the UTM up had put the WLAN on 8.8.8.8 and the LAN used our ISP's DNS). The UTM config was input to the FVS by printing out every config page, taking the unit home and spending a Sunday afternoon laboriously typing in the config and checking for errors.
Once DNS issues were resolved, VPN was set up, configuration input checked, made live one evening, and was working perfectly for many weeks - in contrast to the UTM-25 which I had to revert to, which becomes unstable and requires a regular reboot every 3 or 4 weeks. I don't have the luxury of being able to tinker around with with a FWR once live as it is in 24/7 international use.
The fault, as highlighted above initially manifested as a failure of the Wireless LAN (DMZ port 4) but investigations showed the fault to be at the router. Checking the VPN link showed that also to be down. Then there were failures due to DHCP becoming enabled on the LAN. This was easily resolved by disabling LAN DHCP again, but this didn't resolve the VPN or WLAN issue satisfactorily. I also documented above that a kludge could be used to bring the VPN up but this always failed again soon after.
I did find post elsewhere suggesting that the clock skew VPN issue was due to a faulty power adapter but I can't put my hands on the post at the moment. I have just received an RMA replacement and this will have to wait until I can find time configure and test.
Hope this helps
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!