The change you described to the HBA config file is insufficient. The IP address '127.0.0.1' is for localhost; _every_ computer will typically have 127.0.0.1 set for themselves. So if your remote client tries to connect to 127.0.0.1, it would really be trying to connect to itself. As the database is not running on the client, the connection attempt will fail.
Assuming your client has an address of '1.2.3.4', add the following line to the HBA config file:
host all all 1.2.3.4/32 md5
If you want to allow access from any host on a network, modify the "32" bitmask to the appropriate setting ("24" for a Class C, for example). Also, 'md5' will require MD5-hashed passwords to be passed.
Make sure you leave the line you gave, so that you can continue to connect to the database from the server itself.
Check http://www.postgresql.org/
Main Topics
Browse All Topics
by: earthman2Posted on 2009-05-22 at 04:01:04ID: 24449492
see http://www.postgresql.org/
make sure that
listen_addresses="*"
is set in the postgresql.conf file
or specifies your ip addresses of your lan/wan adapter
if that checks out check the firewall settings and allow traffic on port 5432.