NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Netgear FVS336Gv2 IPSec VPN with Shrew Soft client
I recently upgraded our FVS336Gv2 to firmware 4.3.3-6 from an older v3.x.x. I have reconfigured the firewall and it has internet connection and all is fine for that part of the equation. My issue lie...
Hi StrikedOut,
Let me share this link and it might help. Also, to isolate the problem, kindly try other PC/laptop (with Windows 10 or previous Windows OS) with Shrew Soft Client software installed.
Regards,
DaneA
NETGEAR Community Team
Hi DaneA, thanks for the reply.
That was the walkthrough I used to get as far as I did and I just tried using my laptop which is Win8.1 and get the same error.
Hi StrikedOut,
Let us isolate the problem. Here are my questions below:
a. Were you able to connect just fine using your Windows 10 PC with Shrew Soft Client software before you have upgraded the firmware of the FVS336Gv2?
b. Did you perform a factory reset on the FVS336Gv2 after successfully upgrading its firmware? It is recommended to reset the FVS336Gv2 to factory default settings after doing a firmware upgrade.
c. Is the LAN subnet set on your FVS336Gv2 differ from the LAN subnet of you existing local network where your Windows 10 PC with Shrew Soft Client software is connected to? For example, the FVS336Gv2 has a LAN subnet of 192.168.9.x while your existing local network where your Windows 10 PC belongs has a LAN subnet of 172.16.3.x. The LAN subnet should be different.
d. Is the WAN IP Address registered on the FVS336Gv2 a Public IP Address?
I look forward to your response.
Regards,
DaneA
NETGEAR Community Team
Regarding you questions;
a. Yes, we used to connect using all versions of Windows from Windows 7 to Win 10, all x64.
b. The router was reset to factory after the upgrade.
c. Yes. The LAN subnet of the firewall is 192.168.75.x, My pc and laptop is 192.168.11.x and the VPN connection once established should give a subnet of 192.168.50.x.
d. No but the router between the firewall and the public domain has all ports forwarded and I can see the connection hitting the firewall in the VPN logs although I was expecting the port to be 500.
The layout of the network where the firewall resides is as follows.
Customer LAN -- Firewall LAN (192.168.75.254 -- Firewall WAN (192.168.175.253 -- Router LAN (192.168.175.254) -- Router WAN (78.x.x.x) -- Public domain.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
