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

    Windows Share problem

    Scheduled Pinned Locked Moved Firewalling
    15 Posts 3 Posters 4.3k 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.
    • K Offline
      krisken
      last edited by

      Dear Metu69salemi,

      i've made some screenshots for you so you can get a clear view of the setup.
      There can be some mistakes because i've tried to fix it using trial and error :)

      Dashboard : http://kris.derocker.name/pfsense/windowsshare/dashboard.jpg
      Outboud NAT : http://kris.derocker.name/pfsense/windowsshare/firewall-nat-outbound.jpg
      Firewall rules LAN : http://kris.derocker.name/pfsense/windowsshare/firewall-rules-lan.jpg
      Firewall rules WIFIPRIVATE : http://kris.derocker.name/pfsense/windowsshare/firewall-rules-wifiprivate.jpg

      1 Reply Last reply Reply Quote 0
      • M Offline
        Metu69salemi
        last edited by

        You may need new rule on manual outbound nat as:
        from privatewifi to lan check the box DO NOT NAT

        1 Reply Last reply Reply Quote 0
        • K Offline
          krisken
          last edited by

          I've tried these settings without effect…

          WIFIPRIVATE  10.0.0.0/24 * * * * * NO
          LAN  10.101.0.0/24 * * * * * NO
          WIFIPRIVATE  10.101.0.0/24 * 10.0.0.0/24 * * * NO
          LAN  10.0.0.0/24 * 10.101.0.0/24 * * * NO

          Lan = 10.0.0.1/24 range
          WIFIPRIVATE = 10.101.0.1/24 range

          1 Reply Last reply Reply Quote 0
          • M Offline
            Metu69salemi
            last edited by

            did you change the order that more specific is uppermost?

            1 Reply Last reply Reply Quote 0
            • C Offline
              cmb
              last edited by

              I don't see any reason you need manual outbound NAT, better to use automatic, it won't NAT between internal subnets which is what is breaking your Windows share.

              1 Reply Last reply Reply Quote 0
              • M Offline
                Metu69salemi
                last edited by

                ok, thanks for the info, it was new to me also.

                1 Reply Last reply Reply Quote 0
                • K Offline
                  krisken
                  last edited by

                  I use manual NAT because i also route some IP blocks (external IP's)

                  1 Reply Last reply Reply Quote 0
                  • C Offline
                    cmb
                    last edited by

                    @krisken:

                    I use manual NAT because i also route some IP blocks (external IP's)

                    Ok, in that case just make sure you don't have outbound NAT rules matching traffic between internal networks.

                    1 Reply Last reply Reply Quote 0
                    • K Offline
                      krisken
                      last edited by

                      Dear,

                      I don't think i have…do i?

                      1 Reply Last reply Reply Quote 0
                      • C Offline
                        cmb
                        last edited by

                        Too many interfaces there in outbound NAT and not enough context to tell. Run a constant ping to the NAS, and check Diagnostics>States. Should just show two IPs there, not a third in the middle where it's translating it. If that's good, then your problem is almost certainly the NAS is setup to not serve Windows shares to off-subnet hosts. For instance Samba has a config option that lets you restrict what IP subnets it will serve, if it's a Windows host, the default Windows firewall settings commonly block all off-subnet file access.

                        1 Reply Last reply Reply Quote 0
                        • K Offline
                          krisken
                          last edited by

                          This is what i get with ping :

                          icmp 10.0.0.31:768 <- 10.101.0.2 0:0
                          icmp 10.101.0.2:768 -> 10.0.0.31 0:0

                          10.0.0.31 = NAQ
                          10.101.0.2 = laptop using wireless

                          1 Reply Last reply Reply Quote 0
                          • C Offline
                            cmb
                            last edited by

                            Then you aren't NATing, so that much is good. Problem is on the server then, what I noted in my last post.

                            1 Reply Last reply Reply Quote 0
                            • K Offline
                              krisken
                              last edited by

                              cmb,

                              Thanks for your support, time and answers!

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