Per suggestion from mcatanzaro I’m starting another after posting in another thread this response:
I was wondering if the OP (pblmx) found a solution. I am also using Cisco Anyconnect for my companies VPN and once I connect to the VPN, I am unable to connect to any company servers. The DNS part of systemd-resolved is working because the correct IP addresses are found I just unable to connect to any servers. I have been fighting this for two weeks since I updated to F33. Strange thing about this is I know it worked for one day (the first day using company VPN after upgrading to F33) and then …
The problem was that every time when I tried to connect via Cisco AnyConnect Client it kept looping through the connection and never made it connect. The fix is quite simple actually, go to Network Connections from Control Panel, right-click Cisco AnyConnect Security Mobility Client Connection, and choose Properties. Hi, Its been a while since I first wrote the article. I’m currently using Windows 10 Pro, 64-bit on a Microsoft Surface Pro 3. The version of the Cisco AnyConnect Secure Mobility Client is 3.1.12020.
The summary of the above is that I cannot connect to any servers at my company when I am logged into the VPN. I do believe that DNS queries are working since the correct IPs are returned. But if I try to ping any thing in my work domain it doesn’t work. Same for ssh to a work domain server. Even mail and chat servers which are available outside the VPN are not accessible once I log into the Anyconnect VPN.
I’m using Cisco Anyconnect (not by choice) and I am wondering if there is an incompatibility between Anyconnect and systemd-resolved. I would like to know if anyone has been successful using Anyconnect with F33.
mcatanzaro suggested using resolv.conf mode: foreign. I’m not sure how to do this is this setting
dns=default in NetworkManager.conf? Or something else? I did try this and it didn’t make any difference in results. Is there a systemd configuration that I need to change as well?
Mike
Cannot Connect To This Gateway Anyconnect Windows 10
- What should be done when an attempt to connect to VPN using Cisco AnyConnect generates this message: AnyConnect was not able to establish a connection to the specified secure gateway. Please try connecting again. In the Windows Control Panel navigate to Internet options (Network and Internet Connections, and then Internet Options).
- Cisco Bug: CSCvs64221 - VPN tunnel cannot connect on Windows10 build 1909 with ECDH group 21 and TLS 1.0 disabled on gateway.
- When Connectivity to the Gateway is Lost When OGS is used, if connectivity to the gateway to which the users are connected is lost, then AnyConnect connects to the servers in the backup server listandnot to the next OGS host. The order of operations is as follows: OGS contacts only the primary servers in order to determine the optimal one.