- App Store
Can't connect to xtuple database on local area network
I am trying a new connection to a new database in my office. I have the database setup on a windows 2003 server and can locally connect via pgadmin just fine to the database. But when I try to connect my workstation to it I get the following error:
"Sorry cant connect to the specified xTuple ERP server.
This may be due to a problem with your user name, password, or server connection info.
FATAL: password authentication failed for user "admin" QPSQL: Unable to connect"
The server's IP is 192.168.1.2
Database name: Trufab Stainless
Port : 5432
I do not have postgres installed on the workstation (I figured I only needed it on the server). I tested the user name and password with the pgadmin on the server and it connected fine so I know that info is correct. I am assuming it is a hba.conf setting. I already added " host all all 192.168.1.0/24 md5" and still that error.
thanks again guys!
Mon, 07/22/2013 - 14:32#1
Assuming that you have restarted the postgresql service after making the pg_hba.conf change, the next thing I would do is check to make sure the windows firewall is disabled (or configured to allow tcp port 5432 through it).
If you still can't connect, from a command line on the server run "netstat -a" and look for an entry that says 0.0.0.0:5432 and LISTENING -- if you see that it at least means postgresql is listening for connections from "any" and that the problem is in between you and postgresql. Beyond that you would need to make sure some other application isn't blocking ports.
Mon, 07/22/2013 - 15:04#2
Thanks for the reply David.
Thanks for the reply David. I verified that the TCP 5432 port is added in my firewall and still no luck. I ran netstat -a on the server and it does not show 0.0.0.0:5432 and LISTENING instead it shows" TheBeast:5432 ESTABLISHED" TheBeast is my server's name. Is that the same thing?
Mon, 07/22/2013 - 15:29#3
That means that there is an
That means that there is an open connection to the port, probably pgAdmin or the xtuple client if you have it connected from the server itself. If you don't see the listening line it means PostgreSQL is not listening on the any interface, check your postgresql.conf to make sure listen_address is set to * and not 127.0.0.1.
Tue, 07/23/2013 - 09:06#4
It was already set to *.
It was already set to *. Also made sure postgres service was running. Any other possiblities?
Thu, 08/01/2013 - 13:51#5
Hi David, i need your help too, i am having same problem, even if i turnoff my firewall on my server. server side i can acess the database but can't' from other laptop or desktop.