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

    LAN client cannot connect

    Scheduled Pinned Locked Moved General pfSense Questions
    101 Posts 2 Posters 17.9k 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.
    • S
      Spectrum @stephenw10
      last edited by

      @stephenw10 said in Hardware driver:

      What IP address is your Windows client using?

      Did you set that statically?

      goodmorning. how i see this? windows - cmd - ipconfig?

      1 Reply Last reply Reply Quote 0
      • stephenw10S
        stephenw10 Netgate Administrator
        last edited by

        Yes ipconfig /allshould show it. Though it's been years since I ran Windows!

        S 1 Reply Last reply Reply Quote 0
        • S
          Spectrum @stephenw10
          last edited by Spectrum

          @stephenw10 ok,
          connection-specific dns suffix: brokenboy.local
          dhcp enabled: yes
          automatic configuration enabled: yes
          ipv5 address local to the link: xxxxxx (preferred)
          ipv4 address: 192.168.100.xx(preferred)
          lease obtained at 10 am
          lease scanned at 5pm
          default gateway, dhcp server, dns server are the same 192.168.100.x

          lan cards, local network connection are disconnected (obviously, because the pc is not connected to the switch)

          1 Reply Last reply Reply Quote 0
          • stephenw10S
            stephenw10 Netgate Administrator
            last edited by

            Ok that's good.

            I assume the client still cannot resolve wikipedia.org?

            Go to Diag > DNS Lookup in pfSense and check wikipedia.org there. Make sure all defined DNS servers are able to resolve it.

            Steve

            S 1 Reply Last reply Reply Quote 0
            • S
              Spectrum @stephenw10
              last edited by

              @stephenw10 DNS Lookup
              Hostname
              wikipedia.org
              Results
              Results Record type
              185.15.58.224 A
              2a02:ec80:600:ed1a::1 AAAA
              Timing
              Name server Time of request
              127.0.0.x 45 msec
              192.168.1.xxx 15 msec
              1.1.1.1 2 msec
              8.8.8.8 2 msec
              More information
              Ping
              Traceroute

              1 Reply Last reply Reply Quote 0
              • stephenw10S
                stephenw10 Netgate Administrator
                last edited by

                Hmm, that all looks good then. Is the client still unable to resolve it?

                S 1 Reply Last reply Reply Quote 0
                • S
                  Spectrum @stephenw10
                  last edited by

                  @stephenw10 Is not yet able.

                  1 Reply Last reply Reply Quote 0
                  • stephenw10S
                    stephenw10 Netgate Administrator
                    last edited by

                    pfSense is showing that localhost (127.0.0.1) can resolve it. That's the local DNS resolver, Unbound.

                    LAN side clients should be using that to resolve against. The fact your client cannot implies it isn't using pfSense.

                    Can you test with a different client?

                    S 1 Reply Last reply Reply Quote 0
                    • S
                      Spectrum @stephenw10
                      last edited by Spectrum

                      @stephenw10 how? can you explain in less technical words please? imagine that i am 12 years old, please

                      1 Reply Last reply Reply Quote 0
                      • stephenw10S stephenw10 moved this topic from Hardware on
                      • stephenw10S
                        stephenw10 Netgate Administrator
                        last edited by

                        I forked this topic since this is not an issue with the driver.

                        Either test using a different client if you can.

                        Or test from Windows using the IP address of the LAN IP directly like: nslookup wikipedia.org 192.168.100.1

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