patternsqlMinor
Problems connecting to Windows-based Postgresql
Viewed 0 times
postgresqlconnectingbasedwindowsproblems
Problem
Other computers are having trouble even finding the running Postgresql 9.1 on my Windows 7 machine. Local connections work just fine of course.
In my pg_hba.conf I have:
In postgresql.conf I have (Yes, port 5433 is intentional):
Upon running
Heck, I even made a firewall exception:
The typical response from pgAdmin is always the dreaded:
Any ideas?
In my pg_hba.conf I have:
#office subnets
host all all 192.168.##.0/24 md5
host all all 192.168.##.0/24 md5In postgresql.conf I have (Yes, port 5433 is intentional):
listen_addresses = '*' # what IP address(es) to listen on;
# comma-separated list of addresses;
# defaults to 'localhost', '*' = all
# (change requires restart)
port = 5433 # (change requires restart)Upon running
netstat -a -b in the cmd I find:Can not obtain ownership information
TCP 0.0.0.0:5433 XXXXX-PC:0 LISTENINGHeck, I even made a firewall exception:
Protocols and Ports:
Local port: Specific Ports, 5433
Remote port: All Ports
Scope: Any IP Address
Advanced: Profiles: Private, Public
Programs and Services: Apply to this service: postgresql-x64-9.1The typical response from pgAdmin is always the dreaded:
Server doesn't listen
could not connect to server: Connection timed out (0x0000274C/10060) Is the server running on host "...." and accepting TCP/IP connections on port 5433?Any ideas?
Solution
Here are the steps of troubleshooting I would recommend:
-
From the local machine try the following. If they work you know the issue is not PostgreSQL. If they don't work then you know your issue is local to the machine.
-
Now if that works the next step is to troubleshoot the network. Traceroute may be helpful here. Also try connecting to any other open ports using other software and make sure that works. From there, you may be able to figure out exactly where the packets are being dropped.
-
From the local machine try the following. If they work you know the issue is not PostgreSQL. If they don't work then you know your issue is local to the machine.
- psql -h localhost -p 5433
- psql -h [external ip] -p 5433
- If the latter fails, try temporarily disabling all firewalls and trying again
-
Now if that works the next step is to troubleshoot the network. Traceroute may be helpful here. Also try connecting to any other open ports using other software and make sure that works. From there, you may be able to figure out exactly where the packets are being dropped.
Context
StackExchange Database Administrators Q#30818, answer score: 5
Revisions (0)
No revisions yet.