Peter Goodall's picture


I am using the LAPP VM in VMware 7.x Workstation, on Windows Vista. I've followed the instructions in "How to allow remote access to databases" and still cannot connect to postgres from PGPAdmin. I scanned my virtual machine using Zenmap and did not find the 5432 port open.

Is there something I have to do in Linux to open the port for access from within my home network?




Peter Goodall's picture

See... No postgres port open - getting nowhere, v. frustrating

Scanning x.x.x.x [65535 ports]
Discovered open port 443/tcp on x.x.x.x
Discovered open port 22/tcp on x.x.x.x
Discovered open port 80/tcp on x.x.x.x
Discovered open port 20000/tcp on x.x.x.x
Discovered open port 12322/tcp on x.x.x.x
Discovered open port 12320/tcp on x.x.x.x
Discovered open port 12321/tcp on x.x.x.x
Completed SYN Stealth Scan at 16:02, 5.83s elapsed (65535 total ports)

Please let me know if I have missed some basic documentation...


--Peter G

Alon Swartz's picture

Make sure that postgresql.conf is configured to listen on all interfaces as described here.

Something like this:

listen_addresses = '*'

Also, don't forget to restart the postgres service for the change to take effect.

You can see what ports are "listening" locally on the LAPP appliance like this:

netstat -tan

If you are still having trouble, please post your postgresql.conf

Peter Goodall's picture

Thanks Alon,

There are none so blind...

I had left the listen_addresses line commented out. I'm newish at this *nix stuff and haven't got my inbuilt parser trained. I also got sidetracked by reading problems with MySQL root user not having permissions  for anywhere except localhost created another user etc.etc.... Apologies for wasting your time.

Also needed to change IPV4  in pg_hba.conf to accept connections on all hosts - exactly as in user documentation 'How to allow remote access to databases'.

With thanks,

--Peter G

Add new comment