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

    Captive portal + windows 2012 r2 radius server. wont show up

    Scheduled Pinned Locked Moved Captive Portal
    3 Posts 2 Posters 1.8k 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
      kensh21
      last edited by

      Hi Guys,

      its my first time posting here. i hope someone can shed some light on my situation.

      this is my setup:

      vm1: windows server 2012 r2 with AD,DHCP, DNS and NPS
      vm2:pFsense disabled dhcp and uses the windows server DNS.

      now i setup a radius in win 2012r2 i pretty much followed the guides available. but whenever i enable the captive portal it just wont show up and the web pages wont load. what could be the reason?

      TIA

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

        Your clients have to be able to resolve DNS correctly before the CP page will load. So your Windows DNS server should have an external forwarder set and your DHCP settings should have the Windows server set as your clients' primary name server.

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

          @muswellhillbilly:

          Your clients have to be able to resolve DNS correctly before the CP page will load. So your Windows DNS server should have an external forwarder set and your DHCP settings should have the Windows server set as your clients' primary name server.

          Hi the dns server external forwarder where should i point it? should i just point it to 8.8.8.8?

          i can confirm that the dhcp and dns is being used in the clients pc is coming from the windows server though. i use a VM for client pc.

          EDIT: adding the FQDN and ip on the DNS of windows server did the trick.

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