Fvx538

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.