A long time ago we had an issue where a banking website wouldn't function for a specific customer on dual-NAT, but it functioned when they were put on a public IP. I believe that it was a combination of a too-strict / over-bureaucratic firewall at the bank's end and the NAT affecting path MTU discovery somehow. It was too much work to troubleshoot for one residential customer so I just put them on a public IP.
On Mon, Jan 27, 2020 at 9:46 AM Steve Jones <[email protected]> wrote: > We have been having issues where customers that are NAT (double NAT) are > unable to connect to the Illinois mytax website. I assume its got to do > with security of the site and the double NAT. Changing to a public IP > resolves it, so its not a huge issue. We see that it appends a _/ to the > end of it so its https://mytax.illinois.gov/_/ I dont know what that is > about. > > Is there anything else a guy can do aside from going to all publics? We > dont do CG NAT because our ratio isnt all that high and we just got more > ARIN space that we need to clean up and provision > -- > AF mailing list > [email protected] > http://af.afmug.com/mailman/listinfo/af_af.afmug.com >
-- AF mailing list [email protected] http://af.afmug.com/mailman/listinfo/af_af.afmug.com
