How can i tell which interface the db2 instance is listening on

[bomahony]

Ive installed db2 V8.1 FP11. when i run a local connection, it
connects correctly. However when i run a remote connect (using
squirel) it gives a connection refused error.

i ran a tcpdump on the port (60000) whicle attempting to connect and i
can see incoming traffic from the remote machine, but all traffic
going out has 0bytes.

Im not sure why the connection is being refused, as the logins ect are
the same as i use on the local machine.

If i wanted to change the port the instance is running on, is there
anywhere other than /etc/services it needs to be changed?

OS is AIX 5.3 ML4

Is there any other way to find out why the connection is being refused
on the server?

[james_dey]

On 11 Apr, 13:35, "bomahony" <[e-mail]:

Ive installed db2 V8.1 FP11. when i run a local connection, it
connects correctly. However when i run a remote connect (using
squirel) it gives a connection refused error.

i ran a tcpdump on the port (60000) whicle attempting to connect and i
can see incoming traffic from the remote machine, but all traffic
going out has 0bytes.

Im not sure why the connection is being refused, as the logins ect are
the same as i use on the local machine.

If i wanted to change the port the instance is running on, is there
anywhere other than /etc/services it needs to be changed?

OS is AIX 5.3 ML4

Is there any other way to find out why the connection is being refused
on the server?

1. Do a "netstat -an" to see if the port is listening.

If it's not, it's most likely that you've not done:-

1. "db2set DB2COMM=tcpip"
2, "db2 update dbm cfg using svcename <port>"
3. Stopped and restarted the instance.

To test your connection, you can catalog a tcpip node and your
database against that tcpip node on your server and test the
connection there. If that works, then there will be a problem between
your server and your client. This will either be that you've cataloged
the server tcpip node incorrectly on your client, or are referring to
the server by a name that isn't recognised by your DNS server. You can
try pinging the server name you've cataloged to see if this works.