Thanks June and Phil.
I figured out the problem I did "db2 list node directory" and the host name was hostname.domailname. So, I made an entry in to hosts file with IP address and full name. Then is started working. Kish >From: Juan Lanus <[EMAIL PROTECTED]> >Reply-To: [EMAIL PROTECTED] >To: [EMAIL PROTECTED] >Subject: Re: DB2EUG: Windows 2000 UDB 7.1 FP3 client connection to NT UDB >7.1 FP3 >Date: Wed, 14 Nov 2001 19:37:41 -0300 > >Hi, Kish >I had the same problem in my thinkpad. In my case the error was: > >SQL30081N A communication error has been detected. >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: >"socket". Protocol specific error code(s): "10044", "*", "*". >SQLSTATE=08001 > >The protocol specifics are different. >I "workarounded" the problem using the control center. >In the "Add system" dialog, in Protocol parameters / Host name the >program insisted in puting host.DOMAIN and I erased the ".DOMAIN" part >of the name. >This has also to be done in the cataog instance dialog. >After that I was able to connect. > >Good luck >Juan Lanus >TECNOSOL > > > >kishore lingamallu wrote: > >> >> >>Hi >> >>Are there any know problems with >>Windows 2000 UDB 7.2 (7.1 FP3 ) server user as client connecting to >>database on Windows NT 4.0 UDB 7.2 (UDB 7.1 FP3) server . >> >>I am getting SQL30081N error when I am trying to connect to the database. >> >>I tried to catalog the database from db2cca and it could able to >>search the database successfully and catalog the database successfully. >> >>But when I am trying to connect I am getting the following messages >>----------------------------------------- >>The connection test 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): "10061", "*", "*". SQLSTATE=08001 >> >>For additional information, press the help button. Correct the problem >>described in the help message and retry. >>----------------------------------------- >>I am able to ping the server successfully. >> >>I tried from command line and CCA Test connection. >> >> >>Thanks for Websphere Fix location, >> >>Kish >> >> >> >> >>_________________________________________________________________ >>Get your FREE download of MSN Explorer at >>http://explorer.msn.com/intl.asp >> >> >>===== >>To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED] >>For other info (and scripts), see >>http://people.mn.mediaone.net/scottrmcleod >> >> >> > > > >===== >To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED] >For other info (and scripts), see >http://people.mn.mediaone.net/scottrmcleod > _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp ===== To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED] For other info (and scripts), see http://people.mn.mediaone.net/scottrmcleod
