470,636 Members | 1,597 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 470,636 developers. It's quick & easy.

unable to connect to db from client machine

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.

Nov 29 '06 #1
4 3111
Need specific error messages at each step ...

Larry Edelstein

shsandeep wrote:
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.
Nov 29 '06 #2
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.

Nov 29 '06 #3
Ian
shsandeep wrote:
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
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.
Nov 29 '06 #4
Finally sorted.... it was the firewall which was blocking the port!!
Phew!! N&S - Buggers!! ;-)

Cheers,
San.

Nov 29 '06 #5

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

2 posts views Thread by schnarff | last post: by
16 posts views Thread by Serdar Kalaycý | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.