Ok, then the taget database is not cataloged correctly on this server or the userid and password you are using is not correct. Uncatalog the database and node and recatalog. Take a look at another server and record how it is cataloged there then use that same info on this server. HTH Phil
-----Original Message-----
From: kishore lingamallu
To: [EMAIL PROTECTED]
Sent: 11/14/01 9:50 AM
Subject: RE: DB2EUG: Windows 2000 UDB 7.1 FP3 client connection to NT UDB 7.1 FP3
HI
The target datbaase is started,
I could able to connection from the other servers.
db2comm is set on the NT4 box.
Kish
>From: Philip Gunning <[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: Tue, 13 Nov 2001 10:21:44 -0800
>
>Check the DB2COMM registry variable has TCPIP enabled. HTH Phil
>
>-----Original Message-----
>From: Sinha, Abhijit
>To: [EMAIL PROTECTED]
>Sent: 11/13/01 8:49 AM
>Subject: RE: DB2EUG: Windows 2000 UDB 7.1 FP3 client connection to NT
UDB
>7.1 FP3
>
>ONE of the reasons why this could happen is if the target database you
>are
>trying to connect to has not been started. Check that please.
>
>Abhijit
>
>-----Original Message-----
>From: kishore lingamallu [mailto:[EMAIL PROTECTED]]
>Sent: Tuesday, November 13, 2001 10:26 AM
>To: [EMAIL PROTECTED]
>Subject: RE: DB2EUG: Windows 2000 UDB 7.1 FP3 client connection to NT
>UDB 7.1 FP3
>
>
>
>
>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
