Besfort wrote:
May be you have solved your issue, if not try to disable non-syn reject because that did the trick for me.
You can disable it by creating a new Zone Protection profile (in Network -> Network Profiles).
In the new profile set the "Reject Non-SYN TCP" to no.
Apply this zone profile to your internal zone.
Don't be quick to turn off non-syn tcp checks. This is an important basic firewall check to insure the only valid tcp sessions are transiting the firewall. If you need this turned off for legitimate traffic to work, you probably have asymmetrical routing on your network. You should hunt down this routing issue and resolve the problem so that non-syn tcp checks can remain in place. To check for asymmetrical routing perform the following steps on the two hosts of the legitimate traffic that is being blocked by the non-syn tcp check. host A: run a trace route to host B Host B: run a trace route to host A These should show the same number of hops and use the same routers. There may be different ip interfaces on the same router but the number of hops and the router hosts should all be the same. Common causes of asymmetrical routing include: placing two layer 3 routers with interfaces into the same vlan Routing protocols that provide different metric paths between multi-hops between the hosts due to link cost settings in OSPF or local preference modifications in BGP
... View more