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

    (SOLVED) Unable to connect to public SAMBA server

    Scheduled Pinned Locked Moved General pfSense Questions
    3 Posts 2 Posters 382 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.
    • N
      netnewb2
      last edited by netnewb2

      I'm trying to connect to a public Windows file share on AWS. I'm able to connect from other networks, even from a wireless hotspot conenction, but I'm unable to connect to the instance from behind pfsense.

      I've tried this from 2 pfsense networks, different machines, OSs, nothing seems to work behind pfsense. I don't see anything suspicious in the firewall logs and RDP to the same machine works.

      EDIT: SOLVED. the port was blocked by the ISP

      1 Reply Last reply Reply Quote 0
      • johnpozJ
        johnpoz LAYER 8 Global Moderator
        last edited by

        You understand that many isp block these ports right.. And that even docsis modems can block this..

        https://www.cox.com/residential/support/internet-ports-blocked-or-restricted-by-cox.html

        https://www.docsis.org/node/673

        If your rules are any any, pfsense is not going to block anything outbound.. Sniff on pfsense when you send the traffic do you see pfsense sending outbound on the port you want to send it on? If so - not pfsense.. Pfsense can not do anything about not getting a response or something upstream blocking it.

        An intelligent man is sometimes forced to be drunk to spend time with his fools
        If you get confused: Listen to the Music Play
        Please don't Chat/PM me for help, unless mod related
        SG-4860 24.11 | Lab VMs 2.8, 24.11

        N 1 Reply Last reply Reply Quote 0
        • N
          netnewb2 @johnpoz
          last edited by

          @johnpoz Thanks for answering. Just a couple of minutes ago I checked with my ISP and it seems they have an option to request unlocking this port. I didn't expect this, as in the past they blocked only port 25. I expect it was this after all.

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