Depending on the rest of your configuration and your applicaiton time-out lengths the session you were using could have already been 'open' when you committed your test rule and it never actually checked your security policy list again for that session. It might be a good idea going forward if you haven't already when testing new policies to simply clear the session table for your specified source IP; this at least insures that your not matching a session already on the session table.
Good point but i actually tested access from different workstations with the same results.
Still puzzled with the fact that i was unable to get a clear answer from support personel about "differences" in configuration.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!