I have a FVX538 which was shelved for many years because we had a new FW from the provider. However we switched providers and I had to pull it off the shelf to use. I updated the firmware successfully and all is working well, but I pulled out the VPN software which came with the device and it won't install on Windows 7 or higher with out errors. I downloaded the new VPN software for 30 days free but the configuration is different that the directions in the old software. I can see in the logs on the FW that I'm communicating but on the client side it only says "preparing IKE request" then "tunnel closed" in the lower right corner of the screen. Any assistance would be greatly appreciated.

@digitalbeachbum:Check these link below and this may help you as reference guides:http://kb.netgear.com/app/answers/detail/a_id/24245/related/1http://www.downloads.netgear.com/files/GDC/FVS318N/QSGVPN_4Apr2012.pdf

What FW version are you using now? If you have successfully updated the FW to the latest version, the UI of the firewall should change (should have a yellow/purple banner). When adding a new VPN connection using the wizard, you will be asked for a local and remote identifier. (ex. fvx_remote.com and fvx_local.com) you can actually change/modify the default one (take note of these identifiers). Once you applies the settings it should be good to go. Now, on the client side - the new client software is different from the old ones . Use the wizard as well. configuration>wizardchoose "A router or VPN gateway"enter the WAN IP of the FVS538enter the PSK and the local network IPthe click FinishYou will see three tabs Authentication, Advanced and Certificateclick advancedon the bottom part you will see Local and Remote IDon the type of ID select DNSon local ID: use the remote ID - fvx_remote.comone remote ID: use the local ID - fvx_local.comclick apply and save try opening the tunnel

Firmware Version (Primary): 3.0.5-28.4Yeah, those instructions are what I did - basically the wizards on both sides then added the DNS Identifier fvx_remote and fvx_localLet me try again and see if I missed any thingNhellie26 wrote:What FW version are you using now? If you have successfully updated the FW to the latest version, the UI of the firewall should change (should have a yellow/purple banner). When adding a new VPN connection using the wizard, you will be asked for a local and remote identifier. (ex. fvx_remote.com and fvx_local.com) you can actually change/modify the default one (take note of these identifiers). Once you applies the settings it should be good to go. Now, on the client side - the new client software is different from the old ones . Use the wizard as well. configuration>wizardchoose "A router or VPN gateway"enter the WAN IP of the FVS538enter the PSK and the local network IPthe click FinishYou will see three tabs Authentication, Advanced and Certificateclick advancedon the bottom part you will see Local and Remote IDon the type of ID select DNSon local ID: use the remote ID - fvx_remote.comone remote ID: use the local ID - fvx_local.comclick apply and save try opening the tunnel

I am using a pre-shared key verses the RSA signature. Does this make a difference?Nhellie26 wrote:What FW version are you using now? If you have successfully updated the FW to the latest version, the UI of the firewall should change (should have a yellow/purple banner). When adding a new VPN connection using the wizard, you will be asked for a local and remote identifier. (ex. fvx_remote.com and fvx_local.com) you can actually change/modify the default one (take note of these identifiers). Once you applies the settings it should be good to go. Now, on the client side - the new client software is different from the old ones . Use the wizard as well. configuration>wizardchoose "A router or VPN gateway"enter the WAN IP of the FVS538enter the PSK and the local network IPthe click FinishYou will see three tabs Authentication, Advanced and Certificateclick advancedon the bottom part you will see Local and Remote IDon the type of ID select DNSon local ID: use the remote ID - fvx_remote.comone remote ID: use the local ID - fvx_local.comclick apply and save try opening the tunnel

Thank you. I'm looking through the info now.Sasword wrote:@digitalbeachbum:Check these link below and this may help you as reference guides:http://kb.netgear.com/app/answers/detail/a_id/24245/related/1http://www.downloads.netgear.com/files/GDC/FVS318N/QSGVPN_4Apr2012.pdf

Fvx538 | NETGEAR Communities

41 Replies

digitalbeachbum
Aspirant
Jun 04, 2015
I found the following in my log... I watched the log live and I know this is mine because of the IP's. 2015 Jun 4 14:47:57 [FVX538] [kernel] LOG_PACKET[ACCEPT] IN=WAN OUT=SELF SRC=XX.XXX.XXX.XX DST=XX.XX.XXX.XX PROTO=TCP SPT=51440 DPT=9696 2015 Jun 4 14:47:57 [FVX538] [kernel] LOG_PACKET[ALLOW] IN=SELF OUT=WAN SRC=XX.XX.XXX.XX DST=XX.XXX.XXX.XXX PROTO=TCP SPT=9696 DPT=51440 2015 Jun 4 14:47:57 [FVX538] [kernel] LOG_PACKET[DROP] IN=LAN OUT=SELF SRC=192.168.1.6 DST=192.168.1.255 PROTO=UDP SPT=137 DPT=137 2015 Jun 4 14:47:57 [FVX538] [kernel] LOG_PACKET[ALLOW] IN=SELF OUT=WAN SRC=XX.XX.XXX.XX DST=XX.XXX.XXX.XX PROTO=TCP SPT=9696 DPT=51440
Nhellie
Virtuoso
Jun 04, 2015
Try rebooting the FVX538. Did you perform a factory reset after the FW update?
digitalbeachbum
Aspirant
Jun 04, 2015
Yes, I actually nuked the FW and started over from scratch because I had changed the password and had it saved in to my browser. Over time I forgot the password and had to change it, hence the need to do a factory reset.

Nhellie26 wrote:
Try rebooting the FVX538. Did you perform a factory reset after the FW update?
digitalbeachbum
Aspirant
Jun 04, 2015
Well I'm stumped. Is there a log locally kept on the workstation which would show why I'm getting rejected? I don't see any thing else on the FW side which would lead me to understanding the rejection.

by the way, thanks for covering my rookie move.... but could you remove the rest of the IPs from my previous post?
adit
Mentor
Jun 05, 2015
Read my LAN Subnets NOT to Use tutorial.
digitalbeachbum
Aspirant
Jun 05, 2015
If my work IP's are 192.168.1.x and my home is 192.168.0.x then should I change both of them?

adit wrote:
Read my LAN Subnets NOT to Use tutorial.
digitalbeachbum
Aspirant
Jun 05, 2015
Does it matter to the FW if it doesn't run DHCP? I don't have it running on the FW and it is handled internally by a server.
adit
Mentor
Jun 05, 2015
digitalbeachbum wrote:
If my work IP's are 192.168.1.x and my home is 192.168.0.x then should I change both of them?
I would for VPN Client reasons but I don't know your work network and how complicated it is. The point in the tutorial is that using those common private IP ranges is that you may run into the situation where both the local and remote subnets are the same, and you won't be able to successfully connect and access devices across the VPN tunnel. You should be on firmware 3.0.7-24 (fairly stable version) or newer on the FVX538. Does the 538 have a public IP on it's WAN? Are you testing this outside of the 538 LAN? It doesn't matter what runs DHCP as long as there is only 1 DHCP server enabled on the LAN.

Nhellie26 wrote:
Try rebooting the FVX538. Did you perform a factory reset after the FW update?

adit wrote:
Read my LAN Subnets NOT to Use tutorial.

digitalbeachbum wrote:
If my work IP's are 192.168.1.x and my home is 192.168.0.x then should I change both of them?

digitalbeachbum

Aspirant

Jun 05, 2015

I'll change the so I can finally move forward. I don't ever recall having problems previously I've always used the 192.168.1.x for workplace and at home I've used either 192.168.x.x (but always kept it different from each other as I knew about the conflict)

I'll upgrade the firmware tonight.

The 538 has a public IP.

I've been testing the 538 remotely. It is possible I could do testing internally. I have a completely different subnet with another FW and public IP available.

Yep. One DHCP on this subnet.

I've been burning the candle at both ends on this project and I want it to be over with. As soon as I get this 538 up and running I can transfer every thing over from the other subnet to this new network.

Thanks for the info.

adit wrote:
I would for VPN Client reasons but I don't know your work network and how complicated it is.

The point in the tutorial is that using those common private IP ranges is that you may run into the situation where both the local and remote subnets are the same, and you won't be able to successfully connect and access devices across the VPN tunnel.

You should be on firmware 3.0.7-24 (fairly stable version) or newer on the FVX538.

Does the 538 have a public IP on it's WAN?

Are you testing this outside of the 538 LAN?

It doesn't matter what runs DHCP as long as there is only 1 DHCP server enabled on the LAN.

digitalbeachbum
Aspirant
Jun 06, 2015
The version of firmware I have is up to date. v3.0.7.-24 isn't online.
The version I have is v3.0.5-28.4

adit wrote:
.

You should be on firmware 3.0.7-24 (fairly stable version) or newer on the FVX538.

Forum Discussion

Fvx538

41 Replies

Related Content

FVX538 SFTP

FVX538 Firewall Bandwidth Management

FVX538 v2 - Looking for new replacement

reset FVX538

FVX538 - Problems

NETGEAR Academy

ProSupport for Business