423,311 Members | 1,224 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 423,311 IT Pros & Developers. It's quick & easy.

Protocol specific error code(s): "10060", "*", "*". SQLSTATE=08001

P: 7
I tried to connect DB2 (Sitting in Unix server at my client location) using Db2 connect V8. I am getting the following error message. I tried all the possible options BUt the error is same.. See each type belpw

Standard connection failed.
SQL30081N A communication error has been detected. Communication protocol
being used: "TCP/IP". Communication API being used: "SOCKETS". Location
where the error was detected: "". Communication function detecting the error:
"connect". Protocol specific error code(s): "10060", "*", "*".
SQLSTATE=08001
CLI connection failed.
SQL30081N A communication error has been detected. Communication protocol being used: "TCP/IP". Communication API being used: "SOCKETS". Location where the error was detected: "". Communication function detecting the error: "connect". Protocol specific error code(s): "10060", "*", "*". SQLSTATE=08001
OLEDB connection failed.
SQL30081N A communication error has been detected. Communication protocol being used: "TCP/IP". Communication API being used: "SOCKETS". Location where the error was detected: "". Communication function detecting the error: "connect". Protocol specific error code(s): "10060", "*", "*". SQLSTATE=08001
JDBC connection failed.
[IBM][CLI Driver] SQL30081N A communication error has been detected. Communication protocol being used: "TCP/IP". Communication API being used: "SOCKETS". Location where the error was detected: "". Communication function detecting the error: "connect". Protocol specific error code(s): "10060", "*", "*". SQLSTATE=08001
ADO connection failed.
SQL30081N A communication error has been detected. Communication protocol being used: "TCP/IP". Communication API being used: "SOCKETS". Location where the error was detected: "". Communication function detecting the error: "connect". Protocol specific error code(s): "10060", "*", "*". SQLSTATE=08001
Jun 19 '07 #1

✓ answered by hitendrap

If u are getting: SQL30081N Protocol specific error code(s): "10065", "*", "*". SQLSTATE=08001

If you are using Linux server , turn off your firewall service & check if you can connect to database remotely through

client
to stop firewall type this command on bash : $ etc/init.d/iptables stop

If now you can connect remotely thru client then
turn OFF firewall service from all run levels
before that check

$ chkconfig --list iptables

if they are ON @ runlevels 2,3,4,5 then

$ chkconfig --levels 2345 iptables off


Regards.
Hitendra

Share this Question
Share on Google+
4 Replies


P: 2
Is this problem fixed?
I also encounter this on my platform SUSE10 .Hope someone will help
Apr 17 '09 #2

Shashank1984
P: 26
Folks,
Here is the list of some SQL30081N TCP/IP communication protocol errors and recommended action plans associated with them.
http://www-01.ibm.com/support/docvie...id=swg21164785

Cheers !
Thanks,
Shashank Kharche, IBM.
DB2 for Linux, Unix & Windows -Information Management Software
Apr 18 '09 #3

P: 2
Thanks, I will check in to it.
Apr 20 '09 #4

P: 9
If u are getting: SQL30081N Protocol specific error code(s): "10065", "*", "*". SQLSTATE=08001

If you are using Linux server , turn off your firewall service & check if you can connect to database remotely through

client
to stop firewall type this command on bash : $ etc/init.d/iptables stop

If now you can connect remotely thru client then
turn OFF firewall service from all run levels
before that check

$ chkconfig --list iptables

if they are ON @ runlevels 2,3,4,5 then

$ chkconfig --levels 2345 iptables off


Regards.
Hitendra
Sep 24 '09 #5

Post your reply

Sign in to post your reply or Sign up for a free account.