unable to connect to db from client machine

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

shsandeep - 29 Nov 2006 00:51 GMT

I am unable to connect to the database on the server from the client. It
gets connected at the server.
I tried the following options:
- export/import profile using CA
- manually add database using CA
- manually catalog node and db on the client (the catalog completed
successfully but the connect fails)

Everytime, it gives that 'TCP/IP communication protocol failure...etc
etc'

Also, the exported profile file does not include the IP address, port
number etc... am surprised to see this....

The network is working fine...client is pinging the server....

Any clues as to what is going wrong and how can it be resolved?

Cheers,
San.

Reply to this Message

Larry - 29 Nov 2006 01:43 GMT

Need specific error messages at each step ...

Larry Edelstein

> I am unable to connect to the database on the server from the client. It
> gets connected at the server.
[quoted text clipped - 16 lines]
> Cheers,
> San.

Reply to this Message

shsandeep - 29 Nov 2006 02:17 GMT

This is what I get while trying to connect to the db after cataloging the
node and db on the client:

SQL30081N A communication error has been detected. Communication protocol
being used: "TCP/IP", Communication API being used: "SOCKETS". Location
where the error was detected: "172.19.82.102". Communication function
detecting the error: "connect". Protocol specific error code(s):
"10060","*". SQLSTATE=08001

This is what I get when tryin to import the exported configuration file:

SQL0969N There is no message text corresponding to SQL error "-204583702"
in the message file on this workstations. The error was returned from
module "SQLECTDD" with original tokens "DEVTWHS"

Cheers,
San.

Reply to this Message

Ian - 29 Nov 2006 03:47 GMT

> This is what I get while trying to connect to the db after cataloging the
> node and db on the client:
[quoted text clipped - 4 lines]
> detecting the error: "connect". Protocol specific error code(s):
> "10060","*". SQLSTATE=08001

Can you connect from other clients? If so, make sure the port number
you specified is correct, and that the IP address (172.19.82.102) is
correct (if you specified a hostname when cataloging) to ensure that
there isn't a DNS issue.

Reply to this Message

shsandeep - 29 Nov 2006 04:26 GMT

Finally sorted.... it was the firewall which was blocking the port!!
Phew!! N&S - Buggers!! ;-)

Cheers,
San.

Reply to this Message