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

    Problem accessing mail * RESOLVED *

    Scheduled Pinned Locked Moved Firewalling
    5 Posts 3 Posters 1.6k 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
      kelsen
      last edited by

      Hi,

      I'm having a problem with the network of a customer, they use Outlook and are not able to connect to the server that sits outside the network, made ​​it a rule allowing access ports 110, 25, 587, 995 but still did not work. Doing a telnet through firewall in mail server ip works, from a host on the network does not work.
          Even using the default rule "allow" still doesn't work.
          On "States" output looks like the traffic is still been filtered.
      state.png
      state.png_thumb

      1 Reply Last reply Reply Quote 0
      • jimpJ Offline
        jimp Rebel Alliance Developer Netgate
        last edited by

        The output there means that the outlook server never responded to the syn (connection attempt)

        If it were being filtered by the firewall, one or both of those states would not have existed.

        Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

        Need help fast? Netgate Global Support!

        Do not Chat/PM for help!

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

          well, the Nat was not working, dont know why, perhaps because the lan net is 115.0.0.0/8? when I did a manual nat all worked well. Someone have a logic explanation?

          1 Reply Last reply Reply Quote 0
          • chpalmerC Offline
            chpalmer
            last edited by

            115.0.0.0/8 is not reserved for private addresses and should not be used in a LAN.

            If a particular piece of software or firmware sticks to the RFC you might have an issue or two…

            Triggering snowflakes one by one..
            Intel(R) Core(TM) i5-4590T CPU @ 2.00GHz on an M400 WG box.

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

              I know that, i'm just replacing a linux firewall and cant touch in this address. I would like to know why the pfsense didn't made the automatic nat rules, if it's because the network address or a bug in my installation.

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