Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    PfSense open VPN works on Mac clients but not on Windows 10 clients.

    Scheduled Pinned Locked Moved OpenVPN
    4 Posts 3 Posters 613 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Z
      zo718
      last edited by

      Hello,

      I have open VPN Set up on my PFsense Firewall and used client export to download the Viscosity inline config.
      Everything works great in all the Mac clients running Viscosity VPN. authentication against the LDAP, ping, DNS resolution etc. They can access the internal network, work on our SMB shares with no issues.

      Our Windows 10 clients using Viscosity VPN are able to authenticate. But when connected, they can't access our SMB shares and ping (to an internal IP address) or DNS resolution doesn't work as well.

      Any ideas??

      1 Reply Last reply Reply Quote 0
      • C
        cradulescu
        last edited by

        Provide the output of ROUTE PRINT after you are connected to VPN. Also provide the logs of the client VPN regarding the initialization of the connection.

        1 Reply Last reply Reply Quote 0
        • Z
          zo718
          last edited by

          Hi,

          I resolved the issue.
          typo on my push route 172.16.1.0/24 instead of a 172.16.0.0/24

          thanks!

          1 Reply Last reply Reply Quote 0
          • DerelictD
            Derelict LAYER 8 Netgate
            last edited by

            There is usually no reason to use push route commands any more.

            Put the network in the Local Networks field instead.

            Chattanooga, Tennessee, USA
            A comprehensive network diagram is worth 10,000 words and 15 conference calls.
            DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
            Do Not Chat For Help! NO_WAN_EGRESS(TM)

            1 Reply Last reply Reply Quote 0
            • First post
              Last post
            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.