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

    Apple Remote Desktop (ARD)

    Scheduled Pinned Locked Moved
    Firewalling
    3
    10
    1.1k
    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
      newUser2pfSense
      last edited by

      Hello…

      I'm currently running pfSense 2.4.2-RELEASE-p1 (amd64).  I've been attempting to connect to a relatives MacBook Pro from my Mac using Apple Remote Desktop with no luck.  I've always been able to connect in the past.  There are only two things that have changed since that time; my relative got a new router from her ISP which they stated they put it in bridged mode and I began to use pfSense.  Each of our Macs are up to date as well.  I don't know that pfSense is blocking the connection but am wondering if anyone has any experience with pfSense and Apple Remote Desktop that may be able to provide some guidance?

      Thank you.

      1 Reply Last reply Reply Quote 0
      • G
        GoldFish
        last edited by

        By Default, pfSense will pass all traffic originating from LAN unless the user changes it. Now how are you accessing ARD. Is it open access to the remote desktop or you connect to VPN and then remote in. If its open access, you may have to check if the port is open on the appliance although this is not recommended.

        • pfSense Enthusiast *
        1 Reply Last reply Reply Quote 0
        • N
          newUser2pfSense
          last edited by

          I use ARD with my relatives IPv4 address; my Mac to their Mac.  Nothing in between.  It is interesting to see when my relative begins to read the result from whatismyip.com vs the DynDNSs IP check.  It sounds like whatismyip provides an IPv6 address and DynDNS provides and IPv4 address.

          I've locked down my LAN pretty tight.  In an effort to test if pfSense was blocking the connection, I created a port alias with 3283 and 5900.  I then crafted a rule on my LAN to pass traffic from my LAN to any using the port alias and still couldn't get through.  Maybe I'm crafting the rules incorrectly.

          1 Reply Last reply Reply Quote 0
          • G
            GoldFish
            last edited by

            I would disable the existing rules temporarily. Then start with Any Any rule at the very top and take it from there.

            • pfSense Enthusiast *
            1 Reply Last reply Reply Quote 0
            • N
              newUser2pfSense
              last edited by

              Ok, I placed an Any Any LAN rule at the top and did a packet capture on my LAN.  My relatives internet IPv4 address responded back to my LAN IPv4 address several times with a "udp port 3283 unreachable".  Port 3283 is Apple's Remote Management port.  My relative of course has always had remote management enabled on their Mac so I could remote.  Hmm.  Seems something is blocking the port.  Maybe their ISP doesn't have their router in bridge mode maybe?

              1 Reply Last reply Reply Quote 0
              • G
                GoldFish
                last edited by

                Yeah. Looks like the router doesnt have the port open

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

                  When I have to help a relative regularly I set up an OpenVPN server on their end and VPN in. From there you can ARD straight to the inside address.

                  If that is not possible I use the screen sharing in Messages so no ports have to be forwarded.

                  I like ARD too but it's not worth forwarding in ports for.

                  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
                  • N
                    newUser2pfSense
                    last edited by

                    Derelict…I wouldn't be able to setup and OpenVPN server on their end.  I know where the Screen Sharing is in System Preferences -> Sharing and they have Remote Management checked in Sharing as well but I'm not sure what you are referencing in "Messages".  Can you point me to that so I can try that?

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

                      In Messages right-click on a user and see the screen sharing options.

                      For that everyone has to be using iMessages.

                      ![Screen Shot 2018-01-22 at 12.44.18 PM.png](/public/imported_attachments/1/Screen Shot 2018-01-22 at 12.44.18 PM.png)
                      ![Screen Shot 2018-01-22 at 12.44.18 PM.png_thumb](/public/imported_attachments/1/Screen Shot 2018-01-22 at 12.44.18 PM.png_thumb)

                      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
                      • N
                        newUser2pfSense
                        last edited by

                        Thanks Derelict.  I'll give Messages a try.

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