Checked and unchecked various Docker settings under the General tab in Docker Desktop settings (` Expose daemon on tcp://localhost:2375 without TLS`).

Checked and uncheck various options in the Cisco An圜onnect settings (including ` Allow local (LAN) access when using VPN`).

Switched ISOLATION mode from isolation to hyperv.

Some of the troubleshooting attempts included:

Complete loss of internet access from the running containers.īecause a VPN connection is required for several API-based components, it was essential to solve this.

Inability to use the localhost:portnumber hostname to access the site.

Inability to use custom hostnames to access the site (pings from the host to the CM and Solr hostnames failed with an ` Unreachable` or ` Request Timeout` code).

🤮Īt a high level, any time we connect to the VPN using Cisco An圜onnect, the running containers would begin to misbehave - and symptoms disappeared after VPN was de-activated. The blocker stemmed from this particular client's VPN: Cisco An圜onnect Mobility Client. After prepping and polishing a custom legacy Sitecore 8.2 Docker environment for our developers, we ran into a significant blocker that had us questioning whether we needed to backtrack and use locally installed Sitecore instances instead.

Cisco anyconnect mobility client use