This is a very strange one, but I wanted to let everyone know they need to double check that all features work.
We have a webserver that is used for webtrends data collection and isn't really reviewed that often. I got an email today that the site wasn't working for the past 13 days (exactly when I upgraded to 7.5). So I:
1. Checked that the Additional Address existed (it did)
2. Checked that the Internal Host object existed (it did)
3. Checked that the Internal Host had the same IP (it did)
4. Checked the Packet Filter to make sure a rule existed (it did)
5. Checked the Live Packet Log to see if traffic came in for the site (it didn't)
6. Checked the site to be sure it worked internally (it did)
I had an extra IP for a server that was currently being rebuilt, so I changed its DNAT rule to point to the internal host of the missing server. The site was now accessible through the extra IP. Now this is where it gets whacky, I change the definition of that DNAT to handle traffic from the original IP (the DNAT rule is now a carbon copy of the one below it), it fails. So, I change it back, and delete the DNAT rule that doesn't work. I delete the Additional Address on the Interface and recreate it. I then create a new DNAT rule. It works right away.
Very strange, but the moral of the story, double check that all your IPs are accessible from the outside after you upgrade.
This thread was automatically locked due to age.