Does CIT intend to package the Cisco client with all of the available department VPN pools so that end users will not have to obtain the configuration file themselves?
This option has been discussed, and there are no plans to pursue it at this time. Although it offers some convenience for the end user, it is problematic for several other reasons. First, the list of departmental VPNs is always in flux as pools are created and retired. End-user lists would be out-of-date almost as soon as they were published. Also, as the number of departmental VPN grows, end-user lists would also grow and very possibly become unwieldy in an institution of our size. Lastly, and perhaps most importantly, most departments seek to keep their security-related information private. As a result, there’s general unease about making public to end user a list of all the departmental VPNs that exist across campus.
Related Questions
- When I attempt to connect the Cisco VPN Client on a Mac OS, I receive this error message: Error 51- Unable to communication with the VPN subsystem. How can I resolve this issue?
- Does CIT intend to package the Cisco client with all of the available department VPN pools so that end users will not have to obtain the configuration file themselves?
- How do I configure the Cisco VPN 3000 Concentrator to notify remote users for VPN Client update?
