From: Tom Lane <tgl@sss.pgh.pa.us>
To: "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
cc: "CS DBA" <cs_dba@consistentstate.com>, pgsql-admin@postgresql.org
Subject: Re: Canot access PostgreSQL via psql -h (Vmware Fusion)
In-reply-to: <503744920200002500049ADE@gw.wicourts.gov>
References: <64CA6636-C7A2-4305-8A06-A133DEEFEAE7@consistentstate.com>
	<503744920200002500049ADE@gw.wicourts.gov>
Comments: In-reply-to "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
	message dated "Fri, 24 Aug 2012 09:08:34 -0500"
Date: Fri, 24 Aug 2012 10:35:54 -0400
Message-ID: <20231.1345818954@sss.pgh.pa.us>

"Kevin Grittner" <Kevin.Grittner@wicourts.gov> writes:
> CS DBA <cs_dba@consistentstate.com> wrote:
>> psql: could not connect to server: No route to host
 
> That problem has nothing to do with PostgreSQL; you might have
> better luck on a list related to the other technologies.
 
> FWIW, on Linux I would start with `netstat -plnt` to see if the
> process was listening on the expected port and host address.

"No route to host" doesn't have anything to do with whether there's
anything listening on the target port ... what's more likely is
that the OP mistyped the IP address, or else there's something
wrong with his network layout, interface netmask assignments,
that sort of thing.

			regards, tom lane