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

    OpenVPN point-to-point: cannot connect to server "network drive"

    Scheduled Pinned Locked Moved OpenVPN
    4 Posts 2 Posters 1.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
      orsomannaro
      last edited by

      Point-to-point OpenVPN connection with some vlan in both server and client side.

      server side windows subnet: 192.168.1.0/24 (Windows server stay here)
      client side windows subnet: 192.168.2.0/24

      All seem to work, but from the client subnet I'm not able to connect to Windows mapped "network drive" set to server subnet path (if I use IP address all work great).

      I take a notebook commonly used in server subnet:

      IP: 192.168.1.10
      GW: 192.168.1.1
      DNS: 192.168.1.100

      and I put it in the client subnet without changing the DNS address:

      IP: 192.168.2.10
      GW: 192.168.2.1
      DNS: 192.168.1.100

      I'm expecting that DNS solve the "network drive" path with the correct IP server subnet address, so the notebook can open the related server folder. But this doesn't happen.

      May be I must to use PfSense DNS features to solve the problem?

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

        May be that the reason of no answer is my bad English (so my question is not very clear)?  :-\

        1 Reply Last reply Reply Quote 0
        • ?
          Guest
          last edited by

          server side windows subnet: 192.168.1.0/24 (Windows server stay here)

          is there on the Server side a AD/DC in usage? Did you create there then User accounts then?

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

            is there on the Server side a AD/DC in usage? Did you create there then User accounts then?

            Yes, but if this is the problem I expect that Windows ask me username and password when I try to connect to the network drive (like happen when I use the IP address).

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