cisco secure desktop

Kevin Cernekee cernekee at gmail.com
Wed Jul 17 16:04:16 EDT 2013


On Wed, Jul 17, 2013 at 7:48 AM, ChadDavis <chadmichaeldavis at gmail.com> wrote:
> However, I found openconnect in the debian repos and went with it.
> Wonderful integration with the network manager; impressive improvement
> over recent years.  However, when I actually try to connect to the
> vpn, it complains about a lack of Cisco Secure Desktop.
>
> I need troubleshooting advice.
>
> Here's the actual error.  See below for MORE INFO.
>
> Attempting to connect to 137.69.122.5:443
> SSL negotiation with vpn-usa-west.emc.com
> Connected to HTTPS on vpn-usa-west.emc.com
> GET https://vpn-usa-west.emc.com/
> Got HTTP response: HTTP/1.0 302 Temporary moved
> Attempting to connect to 137.69.122.7:443

Possibly related:

http://lists.infradead.org/pipermail/openconnect-devel/2013-May/001050.html
http://lists.infradead.org/pipermail/openconnect-devel/2013-May/001035.html

You might also want to try "--csd-user=<whatever> --no-xmlpost".  In
XML POST mode, the CSD/Hostscan feature works very differently from
legacy mode, and currently requires a wrapper script.  However, some
VPNs will refuse all logins in legacy mode.



More information about the openconnect-devel mailing list