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

    socket error # 11001 host not found

    Scheduled Pinned Locked Moved General pfSense Questions
    16 Posts 2 Posters 2.1k 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.
    • Z
      Zs vendo @stephenw10
      last edited by

      @stephenw10 But when I close the opvn I'm on the local network, all the files open, but the app doesn't

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

        There's no way we can diagnose this without knowing what is actually failing.

        What is the application that's failing?

        What does error #11001 indicate in that application?

        @Zs-vendo said in socket error # 11001 host not found:

        when I close the opvn I'm on the local network, all the files open, but the app doesn't

        The application fails even when you're on the network directly?

        Steve

        Z 1 Reply Last reply Reply Quote 0
        • Z
          Zs vendo @stephenw10
          last edited by

          @stephenw10 a software made in delphi and firebird database

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

            @stephenw10 said in socket error # 11001 host not found:

            socket error # 11001

            Ok so that appears to be a standard Windows error and it's probably a DNS failure like I suggested:

            WSAHOST_NOT_FOUND
            11001
            Host not found.
            No such host is known. The name is not an official host name or alias, or it cannot be found in the database(s) being queried. This error may also be returned for protocol and service queries, and means that the specified name could not be found in the relevant database.
            

            So what host is it trying to connect to?

            It's probably trying to connect using a hostname that is only valid if you're on the remote network directly in the domain. You can add a domain override in pfSense so it points to the remote company DNS servers for hosts in that domain. If that is the issue.

            Steve

            Z 1 Reply Last reply Reply Quote 0
            • Z
              Zs vendo @stephenw10
              last edited by

              @stephenw10 I already did , I can even ping from my computer ping server.local or ping 192.168.1.2 this shows that the dns is resolved

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

                You shouldn't use .local as it's a specially reserved domain for mDNS. Or is that just an example here?

                If you client is able to resolve the target host using the full FQDN (server.local) perhaps the application is trying to use the hostname only (server) and failing when .local is not it's own domain.

                Z 2 Replies Last reply Reply Quote 0
                • Z
                  Zs vendo @stephenw10
                  last edited by

                  @stephenw10 Captura de tela 2023-06-06 105813.jpg

                  See full ping
                  before
                  ping server.company.local
                  after
                  ping 192.168.1.2

                  1 Reply Last reply Reply Quote 0
                  • Z
                    Zs vendo @stephenw10
                    last edited by

                    This post is deleted!
                    1 Reply Last reply Reply Quote 0
                    • stephenw10S
                      stephenw10 Netgate Administrator
                      last edited by

                      Ok, that looks good. And 53ms looks like it's not local so I assume it's going over the VPN.

                      However it will still fail if the application is trying to use just the hostname (server) instead of the full FQDN (server.company.local). Unless the local domain is company.local which it probably isn't.

                      It may not be DNS, something could be blocking the traffic. What do you have access to to solve this? Can you check the server side?

                      Otherwise try looking at the state table in pfSense and filter it by 192.168.1.2. Do you see states opening when you try to connect with the application?

                      Z 2 Replies Last reply Reply Quote 0
                      • Z
                        Zs vendo @stephenw10
                        last edited by

                        @stephenw10

                        on the server side I have access to everything, other applications, other software, all excel sheets, files...everything...

                        You speak in the certificate configuration?
                        1.jpg

                        1 Reply Last reply Reply Quote 0
                        • Z
                          Zs vendo @stephenw10
                          last edited by

                          @stephenw10 brother that's right, I certainly need to configure the open vpn client

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

                            I meant do you have access to the OpenVPN server or the application server to check for incoming connections?

                            If you don't then check at the pfSense end for the expected states when you try to connect.

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