2

Windows 10 -NextDNS CLI does not work after using other VPN's with TAP

I have installed NextDNS CLI version on two Windows 10 machines that also use OpenVPN and ProtonVPN. 

These machine eventually develop connectivity issues until NextDNS is removed.

I believe both of these use as TAP client as well, like NextDNS.

Is there a way to not lose internet connectivity when using other TAP VPN's? I noticed the official Win10 App works fine, but the problem is with the CLI version which I need because the Standard User cannot disable it.

3 replies

null
    • tekfranz
    • 3 yrs ago
    • Reported - view

    Any word on why installing another VPN would render NextDNS (Windows-CLI) non-functional (no connectivity)?
    Is there a conflict with the TAP driver?
    Why does the Windows 10 full software package work better than the CLI version in this regard?

    • Technical Analyst
    • rjh0522
    • 3 yrs ago
    • Reported - view

    I also came across the same issue today while testing. We can't seem to silently deploy the official Windows application and deploying with the CLI breaks connectivity when using a VPN. I am using NordVPN in this instance, so this does not appear to be a product-specific issue.

      • tekfranz
      • 3 yrs ago
      • Reported - view

      rjh0522  Yes being able to deploy the CLI version in the background is a necessity since the Windows Application is easily disabled. In a some environments there are often other VPN products that are in use, whether a work VPN or a service like NordVPN or Proton VPN. I wish these were compatible with the CLI version.

Login to reply

Content aside

  • 2 Likes
  • 3 yrs agoLast active
  • 3Replies
  • 194Views
  • 2 Following