hi,
I am facing an issue regading comminication from db2-client

here is the db client iam using
Instance "DB2" uses "32" bits and DB2 v9.1.700.855", "s090308", "WR21434", and Fix Pack"7".

on client

i wanted to catalog the database from server and connect to it but when i cataloged the database on to the client i can see the node and database with correct port number and nodenames but facing the following problem


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


i used the option $connect to <dbname> user <userID> using <password>
but it did not work

i can connect to that server through secure CRT but i wanted to catalog some databases from that server to access in quest central/toad

any help will be greately appreciated

Thank you in advance

RAVI
06/17/2009 15:57:47.93

This is just the standard error when IP connectivity cannot be made. The error code says the problem is at URL 10.172.138.2.

This error can be caused by anything that prevents connection: wrong URL, wrong port, port secured, IP stack down, network down, etc.. First see if you can ping the server from the client.

hi,
i tried to ping server from the client no reply from the server (request timed out)
i tried like 4 to 5 IP's for all of them no reply

i was able to catalog one database from one of the server and connect to and even for that IP when i tried to ping i got the same (request timed out)

URL is correct ,port number is also correct,network is up

How to go about to resolve this error ?

any reply will be greately appreciated

Thank you

If you can't ping the server the problem is not connected to DB2. You need to talk to your network people about why you can't talk to the server.