Known Issues With Access Visibility
List of known Access Visibility issues.
As the Access Visibility feature is in Beta release, it is expected that there will be some known minor issues.
The list of known issues is as follows:
VPN tunnel reconnection state may cause some response packets from the prior connection to be treated as new traffic flows. This may result in Access Visibility showing Access Event counts with the reconnecting client as the Traffic Destination and high destination port numbers. If you are seeing User Groups as Traffic Destinations with destination port numbers in the 49152 - 65535 range, then it is being caused by this known issue.
The past Access Event counts for a User are not assigned to the new User Group when the User Group of a User is changed.
Access Events for a deleted User Group is shown, but there will be no Users shown in the filters because, on the deletion of the User Group, all the Users in that group were moved to another User Group.
On creating an IP Service, past Access Event counts are not associated with the new IP service and continue to be displayed associated with the Host or Network for which the IP Service was created.
CloudConnexa blocks internet traffic sent from a Connect application on Windows OS during connection and reconnections when Split-tunnel is set to ON. These blocked access events appear associated with the Traffic Destination category of Other.