Do you have a firewall blocking access to ****t 523? It looks like Control
Center first tries to connect to this ****t, and only later goes to the
****t
the instance is listening on. So if ****t 523 is blocked you have a delay
(though not 4 or 5 minutes, in my experience.)
Based on your comment that you have the same issue with a Linux DB2 Client
other than CC makes me think this is *not* the issue, but I just thought
I'd
put it out there.
Frank
n 4/29/2008 at 7:48 AM, in message <VGFRj.6709$R_4.5308@[EMAIL PROTECTED]
>,
Dan van Ginhoven<danfan46@[EMAIL PROTECTED]
> wrote:
> Hi!
>
> I have installed a new Db2 V9.5 fp1 Linux 64 bit with a partioned
> database.
>
> When I connect to the database using DB2Visualizer on Windows, that
> uses db2jcc, it works OK.
>
> Connecting from DB2 Control Center takes 4-5 minutes, but it connects.
> Opening a table can take 4-5 minutes too.
> Connecting thru a Linux DB2 Client also takes 4-5 minutes, but after
that
> table access seems OK.
> I compared dbm cfg with a working db2 server but did'nt find any
> significant differences.
>
> Where do I start looking? Tried to Google, but did'nt find any obvious
> answers.
> Something with the authentication process?
>
> Mvh
> /dg
|
