We have several end-users that go into one of our service centers, and connect to the corporate network, then launch pulse secure. They do not need pulse secure, since they are now on the corporate network, but they don't listen. We want to block them from logging in to the SA-2500 , and thought that blocking the User Role, at the Source Restriction was a good start. This does not seem to work. They are still able to log in to the SA-2500. So the end user is on 192.168.201.0/24 segment. When we use the public IP, it definately blocks, but should also block on the private IP. This is the table, I am using.
... View more