Thank you both for your replies. Here's the result with just using the hostname: $ openconnect -C "DSID=aLongStringOfChars" --protocol=pulse myWorkplace.server.serv -v --os=win Attempting to connect to server 123.123.123.233:443 Connected to 123.123.123.233:443 SSL negotiation with myWorkplace.server.serv Connected to HTTPS on myWorkplace.server.serv Got HTTP response: HTTP/1.1 404 Not Found Transfer-Encoding: chunked Strict-Transport-Security: max-age=31536000 HTTP body chunked (-2) Unexpected 404 result from server Creating SSL connection failed ..so it looks like I get the same result doing it that way. Daniel, I don't have much hope that the network admins will enable legacy mode, but sometimes they surprise me. So if I continue to be roadblocked with pulse, I'll try to reach out to them. Tim On Sun, Mar 29, 2020 at 12:47 PM David Woodhouse <dwmw2@xxxxxxxxxxxxx> wrote: > > On Sun, 2020-03-29 at 08:32 -0400, Tim Howard wrote: > > D. My connection attempts (url and IP addresses obscured): > > $ openconnect -C "DSID=aLongStringOfChars" --protocol=pulse > > myWorkplace.server.serv/dana/home/index.cgi# -v --os=win > > Attempting to connect to server 123.123.123.233:443 > > Connected to 123.123.123.233:443 > > SSL negotiation with myWorkplace.server.serv > > Connected to HTTPS on myWorkplace.server.serv > > Got HTTP response: HTTP/1.1 404 Not Found > > Try that without the path; just the server hostname. > _______________________________________________ openconnect-devel mailing list openconnect-devel@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/openconnect-devel
