If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Please bear with me if it seems like a silly question since I am new to DB2 LUW.

I can connect to the above db2 server using Putty where I supply the linux machine's ip and SSH port. Basically it connects to the server as a linux user and then I invoke DB2 from there.

But I want to register the remote database at my client windows machine using Configuration Assistant so I can access it locally from my client machine.

So I have given the linux server's ip as hostname and port as db2 service port 50005 for tcp which I have checked its listening on. Database name given is the instance name of db2 server. But when I do a Test Connection using one of the linux system userid and password, it doesn't work.

I know tcp service at port 50005 is working since netstat -an | grep 50005 shows it with LISTEN.

Any idea what could be going wrong. I suspect I am using an operating system userid and password but at DB2 level. Not sure how authentication should happen.

Can you ping the Suse Server from your windows client?
Is the IP of the Suse server = 192.168.1.459 ?
From the Windows client, in a cmd.exe window, what is the result of:
telnet 192.168.1.459 50005
If you do not see "Connected to..." then you might have firewall issues.
If Windows-Firewall (or any software firewall) is active on your Windows client, configure a rule to allow TCP traffic inbound and outbound for port 50005.

Please bear with me if it seems like a silly question since I am new to DB2 LUW.

I can connect to the above db2 server using Putty where I supply the linux machine's ip and SSH port. Basically it connects to the server as a linux user and then I invoke DB2 from there.

But I want to register the remote database at my client windows machine using Configuration Assistant so I can access it locally from my client machine.

So I have given the linux server's ip as hostname and port as db2 service port 50005 for tcp which I have checked its listening on. Database name given is the instance name of db2 server. But when I do a Test Connection using one of the linux system userid and password, it doesn't work.

I know tcp service at port 50005 is working since netstat -an | grep 50005 shows it with LISTEN.

Any idea what could be going wrong. I suspect I am using an operating system userid and password but at DB2 level. Not sure how authentication should happen.

telnet 192.168.1.459 50005 however waits forever and doesn't work. But I see in linux that its listening on port 50005.

If the telnet command to that ip and port does not work (it may not be clear when it is working and when it is not working), then you have a firewall problem. It doesn't matter whether Linux is listening on that port or not.

Looks like something is blocking port 50005 either on Windows, or on Linux or at some point between the workstation and the server. Use tracerte to see the path between your workstation and the Linux server.

So the easiest thing to do is to open the port 50005 on the end-points and on any intervening firewalls.

If it takes too long to get that done (e.g. firewalls are out of your control, or have beurocratic procedures for getting ports opened) then a practical option is to tunnel your DB2 connection via the SSH port which you know is opened. Read about ssh-tunnelling in any good SSH book or google is your friend here...

If the telnet command to that ip and port does not work (it may not be clear when it is working and when it is not working), then you have a firewall problem. It doesn't matter whether Linux is listening on that port or not.

Thanks Marcus, db2mor and n_i. Turning off firewall did help with telnet. I also started xinetd. Not sure if that helped too.

Anyway, now I have added the connection setup to firewall custom rules and can connect with firewall up.