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

How to: Bypass Captive Portal for RDP connection

Scheduled Pinned Locked Moved Captive Portal
4 Posts 2 Posters 1.5k 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.
  • C
    cyberjox
    last edited by Mar 15, 2015, 7:03 AM

    We have 2 additional networks through data lines 192.168.1.0 and 192.168.2.0, pfsense is in 192.168.0.0 network. The terminal server is on the psfense network, users from the other network can only connect to the terminal server if we add the users IP to the allowed IP addresses tab in captive portal. But by doing this, users can surf the internet without being prompted to login. Is there a solution to bypass captive portal for remote desktop connection only?

    Same thing happens when users from outside network using VPN connection cannot connect to the terminal server unless the terminal server is added to the allowed IP addresses tab in captive portal.

    Appreciate if anyone can guide me through a possible solution.

    Thanks!

    1 Reply Last reply Reply Quote 0
    • D
      Derelict LAYER 8 Netgate
      last edited by Mar 15, 2015, 7:47 AM

      Instead of adding the clients to Allowed IP addresses why don't you add the server they need to RDP to.  You should be able to further restrict what ports on that host they can access with normal firewall rules.

      Adding allowed IP addresses will allow IP access to/from these addresses through the captive portal without being taken to the portal page. This can be used for a web server serving images for the portal page or a DNS server on another network, for example.

      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
      • C
        cyberjox
        last edited by Mar 16, 2015, 11:37 AM

        Thanks for your reply Derelict…

        Did what you said, but the terminal server is still able to access the internet even when rules are added to block port 80.

        1 Reply Last reply Reply Quote 0
        • D
          Derelict LAYER 8 Netgate
          last edited by Mar 16, 2015, 3:23 PM

          Instead of saying what you think you've done, post what you;ve done.

          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
          1 out of 4
          • First post
            1/4
            Last post
          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
            This community forum collects and processes your personal information.
            consent.not_received