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

    Port forwarding for Exchange server

    Scheduled Pinned Locked Moved NAT
    4 Posts 3 Posters 1.1k 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.
    • F
      Fafa24
      last edited by

      Dear All,

      This is my first post on this forum. Today I wanted to replace my Edgerouter firewall with a pfsense box. I have behind the firewall in the LAN zone an Exchange 2016 server as a VM. For the Exchange server I forward port 25, 80 and 443 to my mailserver. I have iPad, iPhone setup with my mailbox. I even use for my computer in the LAN zone the external FQN name. It's easier for autodiscovery with a certificate. Everything works great with the Edgerouter which has port forwarding set.

      Today I set up the pfsense firewall with the same port forwarding rules. Port 80 and 443 worked fine. I could connect with Outlook or iPad to the email. However port forwarding rule for port 25 didn't work. I see in the firewall log pass entries for port 25 with the destination IP for my mailserver. However actually email were never delivered to my mailserver. I verified that with the Get-MessageTrackingslogs cmdlet. Mails stopped delivery when I took the pfsense live. I tried several things, but nothing helps.

      I set up up other port forwarding entries for my Synology and they worked fine too. Just not port 25.

      I removed the pfsense from the network and put in the Edgerouter in production again. After that the mails arrived again at my Exchange server.

      I'm just curious what is so special with port 25 than the other ports I forwarded successfully.

      Any idea?

      Thanks,

      1 Reply Last reply Reply Quote 0
      • DerelictD
        Derelict LAYER 8 Netgate
        last edited by

        Not in pfSense.

        https://doc.pfsense.org/index.php/Port_Forward_Troubleshooting

        Chattanooga, Tennessee, USA
        A comprehensive network diagram is worth 10,000 words and 15 conference calls.
        DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
        Do Not Chat For Help! NO_WAN_EGRESS(TM)

        1 Reply Last reply Reply Quote 0
        • F
          Fafa24
          last edited by

          Thanks - the problem was not a a wrong configuration of the NAT or firewall rule. I had to disable DNS resolver and afte that mails were flowing instantly.

          1 Reply Last reply Reply Quote 0
          • KOMK
            KOM
            last edited by

            How would disabling the resolver accomplish that??

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