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

    Can't connect to Devices on the WAN on Port 445

    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.
    • H Offline
      hijacker
      last edited by

      Hello

      I have several old IPCop Installations out there and want to connect to them via Remote-Admin. The Port is 445, https. With pfsense 2.0, I can't connect to the Remote Host. With 1.2.3, everything worked fine.

      Which things do I have to do?

      Kind regards, dave

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

        What does your rules say

        1 Reply Last reply Reply Quote 0
        • H Offline
          hijacker
          last edited by

          LAN -to- WAN is everything open!

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

            for a start https is on port 443 and not in 445, so you've either changed original port or have portforwards on that?
            If you have anything open from pfsense, and i assume you're not having any proxies, the possibility to say that problem is in pfsense is quote minimal.

            If your firewall allowes anything then you have problems with another end of the line or something is not correctly set.
            Like what is your wan ip, i don't want to know your public ip, but is it an internal ip? are behind another firewall?

            1 Reply Last reply Reply Quote 0
            • B Offline
              Bai Shen
              last edited by

              @Metu69salemi:

              for a start https is on port 443 and not in 445, so you've either changed original port or have portforwards on that?
              If you have anything open from pfsense, and i assume you're not having any proxies, the possibility to say that problem is in pfsense is quote minimal.

              If your firewall allowes anything then you have problems with another end of the line or something is not correctly set.
              Like what is your wan ip, i don't want to know your public ip, but is it an internal ip? are behind another firewall?

              IIRC, IPCop's web gui defaults to 81 and 445 to allow you to run any normal web servers on your network.

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