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

    OpenVPN: Connected, but can't access internal network?

    Scheduled Pinned Locked Moved OpenVPN
    6 Posts 4 Posters 2.0k 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.
    • O
      oguruma
      last edited by

      I am able to connect to via OpenVPN GUI (Windows), and I verified via ipconfig that I am assigned an IP address accordingly, but I am not able to access anything on the local network. I also cannot ping devices on the local network. When I connect using the same certificate and user with my Macbook, I can access shares, view IP cameras as I would expect. The problem seems to be with this one machine. I don't have any other Windows machines to try.

      This is my first time attempting to using VPN with this machine.

      Any ideas where to start?

      1 Reply Last reply Reply Quote 0
      • V
        viragomann
        last edited by

        You have to start the OpenVPN GUI with admin privileges to get the routs pushed on your system.

        1 Reply Last reply Reply Quote 0
        • D
          divsys
          last edited by

          Also watch out for the Win Firewall blocking access to outside networks by default, easiest thing is to turn it off for testing.

          -jfp

          1 Reply Last reply Reply Quote 0
          • O
            oguruma
            last edited by

            I ran it administrator and without Windows firewall from the get-go… Issue persists...

            1 Reply Last reply Reply Quote 0
            • V
              viragomann
              last edited by

              What is your remote network and the tunnel subnet? Do your server push the routes?
              Show your server config and the client log of the connection. Run route print on the Windows command line and post the result.

              1 Reply Last reply Reply Quote 0
              • M
                marvosa
                last edited by

                There wasn't much detail in the OP, which makes it difficult to help troubleshoot.  Post your config (server1.conf).  Check the routing table on the client, is there a route to your LAN?  Are there any blocks in the logs?

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