Thread: Client Authentication problem

Client Authentication problem

From
"Vaneet Sharma"
Date:

Hello,

I am using postgreSQL 8.0.2

I configured the database, started postmaster. It is running well. I can check and see it with ps anx command.

I am running postgreSQL on centos 3.4 and Centos 4.0 machines

Well, I created a database called test as well by command line on secure CRT

Now the problem is that:
When I try to connect to my server using pgAdminIII, it is giving me the following error :

"Error connecting to the server: could not connect to the server: No route to host ( 0X00002751/10065).
Is the server running on host 212.xx.xxx.xxx and accepting TCP/IP connections on port 5432?  "

I have read pg_hba file and also included the IP entry of my machine from which I am connecting
Entry Is below:

host    all         all         192.168.50.122         255.255.255.0   trust

I have also changed postgreSQL.conf
1) I included listen_addresses = '*' on port 5432

Well, any help will be appreciated.
Also, can someone tell me where does postgreSQL put the DETAILED log on CENTOS 4.0

I opened logfile ( in home directory of postgreSQL installation , it does not give detailed log)

Well, I am a bit new to linux and also new to Administration and Installation of postgres.

Kind Regards
Vaneet

Vaneet Sharma
executive manager
iDeasTank Limited
an iwg business
dolphins' court po 388
valletta, m-malta/europe
vaneet@iwg.info
call me on www.skype.com - my ID is CALLVANEET

mobile: 

+356 9943 8263
skype:  CALLVANEET
fax:  +356 9952 8888
phone:  +356 9942 8888
Want a signature like this?

iwg is a global e-mobile company creating, building and growing new businesses.  iwg founders are pioneers in creating multi-billion dollar mobile and Internet businesses in Europe, Asia and the US.

www.iWG.info
www.countryprofiler.com/iWG
www.visitmalta.com
www.mfc.com.mt

Privileged/Confidential Information may be contained in this message.  If you are not the addressee indicated in this message (or responsible for delivery of the message to such person), you may not copy or deliver this message to anyone. In such case, you should destroy this message and kindly notify the sender by reply email.

Re: Client Authentication problem

From
Scott Marlowe
Date:
On Wed, 2005-04-27 at 11:43, Vaneet Sharma wrote:
> Hello,
>
> I am using postgreSQL 8.0.2
>
> I configured the database, started postmaster. It is running well. I
> can check and see it with ps anx command.
>
> I am running postgreSQL on centos 3.4 and Centos 4.0 machines
>
> Well, I created a database called test as well by command line on
> secure CRT
>
> Now the problem is that:
> When I try to connect to my server using pgAdminIII, it is giving me
> the following error :
>
> "Error connecting to the server: could not connect to the server: No
> route to host ( 0X00002751/10065).
> Is the server running on host 212.xx.xxx.xxx and accepting TCP/IP
> connections on port 5432?  "
>
>
> I have read pg_hba file and also included the IP entry of my machine
> from which I am connecting
> Entry Is below:
>
> host    all         all         192.168.50.122         255.255.255.0
> trust

This sounds like a networking problem right now.

I note that the IP you're trying to connect to has a 212.xxx.xxx.xxx
while the host you're connecting from needs to be 192.168.xxx.xxx.
Since 192.168 is generally not routed around a lot, I'm guessing you've
got a dns  / etc/hosts issue but can't really be sure.

what does 'traceroute dbhostname' say?

Re: Client Authentication problem

From
Michael Fuhr
Date:
On Wed, Apr 27, 2005 at 12:13:14PM -0500, Scott Marlowe wrote:
> On Wed, 2005-04-27 at 11:43, Vaneet Sharma wrote:
> >
> > "Error connecting to the server: could not connect to the server: No
> > route to host ( 0X00002751/10065).
> > Is the server running on host 212.xx.xxx.xxx and accepting TCP/IP
> > connections on port 5432?  "
> >
> > I have read pg_hba file and also included the IP entry of my machine
> > from which I am connecting
> > Entry Is below:
> >
> > host    all         all         192.168.50.122         255.255.255.0
> > trust
>
> This sounds like a networking problem right now.

Or possibly a firewall problem.  Some firewalls/packet filters
return ICMP messages instead of silently dropping packets, and some
software then displays the connection failure as "no route to host"
(EHOSTUNREACH).  But I'd check the routing first.

--
Michael Fuhr
http://www.fuhr.org/~mfuhr/