Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
Database Servers
DB2InformixIngresMS SQLOraclePervasive.SQLPostgreSQLProgressSybase
Desktop Databases
FileMakerFoxProMS AccessParadox
General
General DB TopicsDatabase Theory
Related Topics
Java Development.NET DevelopmentVB DevelopmentMore Topics ...

Database Forum / DB2 Topics / June 2006

Tip: Looking for answers? Try searching our database.

Can connect to one DB but not another on same server??

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
jd_12345@yahoo.com - 28 Jun 2006 18:20 GMT
Windows XP connected via DSL over a VPN to an AIX server
DB2/6000 8.2.3
Using IBM DB2 ODBC Driver

I can connect fine to a specific DB via an AIX box and a person in the
next cubicle connected the same way as I am can access the database.
Last week I connected fine but some network issues occurred since.  I
now can connect to one DB but not another on the same server using the
the same user ID/password.  I've had no issues connecting to either DB
for months.

I'm getting the error below:
SQL30081N  A communication error has been detected.  Communication
protocol
being used: "TCP/IP".  Communication API being used: "SOCKETS".
Location
where the error was detected: "nnn.nnn.n.nn".  Communication function
detecting the error: "connect".  Protocol specific error code(s):
"10061", "*",
"*".  SQLSTATE=08001

The IP address, nnn.nnn.n.nn, is my local laptop.

Obviously, the problem is local to my Windows client.  Does anyone have
any ideas on what I might check?

Thanks, Jim D.
jd_12345@yahoo.com - 28 Jun 2006 18:46 GMT
I deleted and re-created the ODBC driver entry without any change in
result.  I also get the same error when testing the connection via ODBC
or CLI in the Configuration Assistant.

Jim D.
jd_12345@yahoo.com - 28 Jun 2006 19:49 GMT
I found my problem by comparing the working connection with the problem
DB using the Configuration Assistant.  Curiously, the host name was my
local workstation.  I changed this to the proper host name and
everything is  fine.  I have no idea how the host name got changed and,
as the incorect host name was a meaningless collection of letters that
came from the manufacturer, there's no way I could have made the change
manually.

Jim D.
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.