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

    Config pfSense to works as DHCP for Windows 22 Domain Network

    Scheduled Pinned Locked Moved DHCP and DNS
    3 Posts 2 Posters 281 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.
    • PitohuiCHP
      PitohuiCH
      last edited by PitohuiCH

      Hi all :)

      I'm kinda new to pfSense but i already managed to create a failover wan and 4 vlans for dedicated use. 3 of the 4 seperated lans can communicate with each other (DMZ for sure excluded) but what ever i do, i don't get the domain able to be found.

      Can anyone assist me?

      some quick informations

      Servernetwork 10.0.0.0/27

      • 10.0.0.1 Gateway
      • 10.0.0.4/27 Windows Server 2022 Standard "Active Directory" is configured as W22-DC01.lorem.local
      • 10.0.0.11/27 Windows 10 Client can access the files shared on W22-DC01.lorem.local but can't connect to domain

      Streaming 10.10.10.8/

      • 10.10.10.9 Gateway
      • 10.10.10.11/29 Windows 10 Client can access the files shared on W22-DC01.lorem.local but can't connect to domain

      DMZ 172.16.0.0/27

      • 172.16.0.1 Gateway
      • 172.16.0.11/27 Windows 10 Client can't access other land (as intended)

      Default 192.168.0.0/24

      • 192.168.0.1 Gateway
      • 192.168.0.11/24 Windows 10 Client can access the files shared on W22-DC01.lorem.local but can't connect to domain

      To be honest i don't know if it is a DNS issue or a DHCP issue.

      Any help would be much appreciated :)

      Greetings from Switzerland

      S 1 Reply Last reply Reply Quote 0
      • S
        SteveITS Galactic Empire @PitohuiCH
        last edited by

        @PitohuiCH You need to use Windows DNS at some level. You can either create a domain override in pfSense, to point your AD domain to your Windows Server(s) 10.0.0.4. Or else set PCs to use Windows Server for DNS and have Server forward to pfSense if you need to.

        Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
        When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
        Upvote ๐Ÿ‘ helpful posts!

        PitohuiCHP 1 Reply Last reply Reply Quote 1
        • PitohuiCHP
          PitohuiCH @SteveITS
          last edited by

          @SteveITS

          Oh My..... you just solved 20hrs plus of thinking trining and restoring withing 10 seconds. the domain override was exactly what i was looking for.

          Thank you so much for the help ๐Ÿ˜ƒ

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