I'm experiencing a major head-ache at the moment with our company firewall, we're currently changing ISPs (new lease line and new block of static IPs) and I'm setting up firewall rules (we're using a NETGEAR ProSafe VPN Firewall FVX538).
The firewall is visible internally on
18.104.22.168 (all IPs for example only) and we can configure it through the web admin on ports 80 and 443. All traffic from our building goes out on
22.214.171.124, but when you go to the
126.96.36.199 IP (from within or outside the network), the firewall admin page is shown. This isn't really what we want!
I've tried adding firewall rules for HTTP traffic on
188.8.131.52 to be routed to one of our web servers at
184.108.40.206, but when I add this rule, requests to
220.127.116.11 just hang. If I change my rule to
18.104.22.168, it works fine but the NETGEAR admin's still visible on
22.214.171.124 - problem not solved.
The real problem is that this means we can't point our domain
126.96.36.199, because the NETGEAR admin would show rather than our site, but we need this domain to resolve to
188.8.131.52 because all mail out of our building will come from this IP (our client's spam filters won't let our mail through - reverse DNS problems).
I'm banging my head against my desk: this MUST be possible, or how would a company that has a single IP address be able to resolve web traffic? Can anyone help? Sorry if the questions doesn't make a lot of sense - I always find questions like this difficult to express!
Update / Things I've tried
- Ensure remote management is disabled (it's never been enabled anyway) screen
- Rebooted firewall
- Checked for firmware updates
- Tried adding DMZ WAN rule in place of a LAN WAN rule