using netstat -tlpn:
tcp 0 0 127.0.0.1:5432 0.0.0.0:* LISTEN 1142/postmaster
tcp 0 0 192.168.56.101:5432 0.0.0.0:* LISTEN 1142/postmaster
tcp 0 0 192.168.56.101:5432 0.0.0.0:* LISTEN 1142/postmaster
tcp6 0 0 ::1:5432 :::* LISTEN 1142/postmaster
telnettting to 5432 fails.
Ports 22 and 9090 are open/listening and telnetting just fine. The problem must be on the Win 10 side.
Thanks. Kevin
On Tuesday, July 20, 2021, 5:49:59 PM PDT, Ron <ronljohnsonjr@xxxxxxxxx> wrote:
- run netcat to ee if postgres is listening on port 5432.
- then telnet to port 5432 to see if it's open.
- then telnet to port 5432 to see if it's open.
On 7/20/21 6:05 PM, Kevin Struckhoff
wrote:
I'm running Oracle VBox
6.1. What doesn't make sense is that I can connect via
putty, WinSCP and even at port 9090 for the CentOS web
client (cockpit) using the static IP address.
I suspect there's a bug in
VBox, because my other VM uses just a single network adaptor
set to Bridged mode and it connects just fine. However, it
only works at home and not on the road. Hence the need for a
static IP.
Thanks. Kevin
On Tuesday, July 20, 2021, 11:02:31 AM PDT, Jeff Janes
<jeff.janes@xxxxxxxxx> wrote:
On Mon, Jul 19, 2021 at 6:48 PM Kevin
Struckhoff <kevinstruckhoff@xxxxxxxxx>
wrote:
Hi,
Just installed 13.3 on CentOS 8 runnning on a VM on my win 10 laptop.
What is your VM software?
I am getting an error while running the odbc connection test:
could not connect to server: connection timed out.
Connection timeouts are almost always caused by
firewalls or gateways. It can't be due to pg_hba,
as you are not getting far enough for that to kick
in yet.
Cheers,
Jeff
--
Angular momentum makes the world go 'round.
Angular momentum makes the world go 'round.
