Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tDAJZ-00GQxl-3U for pgsql-odbc@arkaria.postgresql.org; Mon, 18 Nov 2024 22:33:49 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1tDAJW-008LrA-IQ for pgsql-odbc@arkaria.postgresql.org; Mon, 18 Nov 2024 22:33:47 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tDAJW-008Lqt-4I for pgsql-odbc@lists.postgresql.org; Mon, 18 Nov 2024 22:33:46 +0000 Received: from pgintl.fastcrypt.com ([149.56.129.164]) by makus.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1tDAJP-002agH-QW for pgsql-odbc@lists.postgresql.org; Mon, 18 Nov 2024 22:33:45 +0000 Received: from mail-ej1-f46.google.com (mail-ej1-f46.google.com [209.85.218.46]) by pgintl.fastcrypt.com (Postfix) with ESMTPSA id 43D29207FB for ; Mon, 18 Nov 2024 17:33:37 -0500 (EST) Received: by mail-ej1-f46.google.com with SMTP id a640c23a62f3a-a99f3a5a44cso35606766b.3 for ; Mon, 18 Nov 2024 14:33:37 -0800 (PST) X-Gm-Message-State: AOJu0YzBnikgXDd9n186ov2AM3N7ulzArn3rAMGRg4e3f5M9ZSsrStng DKUnag570iOuD7TkBYc/YQcBVmhvGWqT5Dfety+ddqgZJ4om5seQ1ejBYUaTU5nbh32/a+dVwB9 BAb0stYp+O1PgRHad+NHuQXDtWn8= X-Google-Smtp-Source: AGHT+IFLlZHfYbb+XX/QGTRDYXCEg+eyV4cvkV0R3zWWiJlJ1HH73GiRIQ07dfbrLIFjOO6kZhkC6tkZBnR++WIEWYA= X-Received: by 2002:a17:907:26ca:b0:a99:eedd:6466 with SMTP id a640c23a62f3a-aa483426483mr1344428966b.19.1731969216941; Mon, 18 Nov 2024 14:33:36 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Dave Cramer Date: Mon, 18 Nov 2024 17:33:19 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: ODBC configuration problem To: Steven Adams Cc: "pgsql-odbc@lists.postgresql.org" Content-Type: multipart/alternative; boundary="000000000000f0249b062737819a" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000f0249b062737819a Content-Type: text/plain; charset="UTF-8" I'd prefer if this were on github https://github.com/postgresql-interfaces/psqlodbc/issues But my guess is that your postgresql.conf file does not have localhost enabled. https://www.postgresql.org/docs/current/runtime-config-connection.html#GUC-LISTEN-ADDRESSES Dave Cramer www.postgres.rocks On Mon, 18 Nov 2024 at 17:28, Steven Adams wrote: > Hello, > > I'm trying to use MS Access with PostgreSQL and so want to configure an > ODBC file for this. Testing it resulted in a connection timeout, so I > looked at this to troubleshoot: > https://odbc.postgresql.org/faq.html#3.3 > Adding a "tcpip=true" line to postgresql.conf and a line to permit a > connection from the computer running Access to pg_hba.conf and then > restarting PostgreSQL seemed to go without errors, but when I tried to run > the psql command afterward, I got this error: > psql: error: connection to server at "localhost" (127.0.0.1), port 5432 > failed: Connection refused > Is the server running on that host and accepting TCP/IP > connections? > > The psql command worked again after I undid these changes, so I'm trying > to figure out how they caused this error. The line I added to pg_hba.conf > was as follows. > host spiralxprime web_app 192.168.0.72 scram-sha-256 > > Any ideas as to why this is happening would be appreciated. > > Regards, > > Steven Adams > > --000000000000f0249b062737819a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

On Mon, 18 Nov 2024 at 17:28, Steven Adams <stevenadams@spiralxllc.com> wrote:
Hello,

I'm trying to use MS Access with PostgreSQL and so want to configure an= ODBC file for this.=C2=A0 Testing it resulted in a connection timeout, so = I looked at this to troubleshoot:
Adding a "tcpip=3Dtrue" line to postgresql.conf and a line to per= mit a connection from the computer running Access to pg_hba.conf and then r= estarting PostgreSQL seemed to go without errors, but when I tried to run t= he psql command afterward, I got this error:
psql: error: connection to server at "localhost" (127.0.0.1), por= t 5432 failed: Connection refused
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Is the server running on that host and acceptin= g TCP/IP connections?

The psql command worked again after I undid these changes, so I'm tryin= g to figure out how they caused this error.=C2=A0 The line I added to pg_hb= a.conf was as follows.
host=C2=A0 =C2=A0 =C2=A0 spiralxprime=C2=A0 =C2=A0 =C2=A0web_app=C2=A0 =C2= =A0 =C2=A0192.168.0.72=C2=A0 =C2=A0 =C2=A0scram-sha-256

Any ideas as to why this is happening would be appreciated.

Regards,

Steven Adams

--000000000000f0249b062737819a--