cisco secure desktop

ChadDavis chadmichaeldavis at gmail.com
Wed Jul 17 10:48:09 EDT 2013


I'm trying to connect to my companies vpn with open connect.  I'm
running Debian linux.  I'm having trouble, obviously ;)  So, normally
my company has users install the cisco vpn client via an applet that
automagically sets everything up for you.  This applet hangs
indefinitely in my browsers.  I can't quite sort out yet what the
problem is.

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
SSL negotiation with scl02-01i11-vn04.emc.com
Connected to HTTPS on scl02-01i11-vn04.emc.com
GET https://scl02-01i11-vn04.emc.com/
Got HTTP response: HTTP/1.0 302 Object Moved
SSL negotiation with scl02-01i11-vn04.emc.com
Connected to HTTPS on scl02-01i11-vn04.emc.com
GET https://scl02-01i11-vn04.emc.com/+webvpn+/index.html
GET https://scl02-01i11-vn04.emc.com/CACHE/sdesktop/install/binaries/sfinst
GET https://scl02-01i11-vn04.emc.com/+CSCOE+/sdesktop/wait.html
Refreshing +CSCOE+/sdesktop/wait.html after 1 second...
SSL negotiation with scl02-01i11-vn04.emc.com
Connected to HTTPS on scl02-01i11-vn04.emc.com
GET https://scl02-01i11-vn04.emc.com/+CSCOE+/sdesktop/wait.html
Refreshing +CSCOE+/sdesktop/wait.html after 1 second...
SSL negotiation with scl02-01i11-vn04.emc.com
Connected to HTTPS on scl02-01i11-vn04.emc.com
GET https://scl02-01i11-vn04.emc.com/+CSCOE+/sdesktop/wait.html
Refreshing +CSCOE+/sdesktop/wait.html after 1 second...
<snip>

Then if I hit the "connect" icon again while this is happening . . .

It then asks for credentials, accepts them ( why didn't it ask for
credentials the first time? ), and then it craps out, reporting this
error message:

"Unable to complete connection: Cisco Secure Desktop not installed on
the client."



More information about the openconnect-devel mailing list