Quote:
Originally Posted by CSING Checked the notes and I was incorrect. The correction for the Cisco VPN was made in the client and not the server. A bug was introduced in HFA05 whereby if you connect a second time to the Cisco concentrator, the client sends a heartbeat with a session ID from the first connection, so the Integrity server never authorizes the session to the VPN concentrator. This has been fixed in HFA6. |
Hi Csing,
I have been inundated with problems where the disconnected policy was still active after VPN connection. I guess this answers that problem. This has had us stumped as we coud not establish a pattern.
Thanks
Unc