Well, it seems that your server on 192.168.1.2 is not configure to talk
TCP/IP.

To check this, you can log in on the server, and execute a db2set.
if there's no line saying: DB2_COMM=TCPIP then you should probably add
this by using db2set.

Furthermore, if you do so, check in your /etc/services that there's an
entry like 'db2 50000/tcp'.
if not, add it. DB2 needs to know on what port to run its service.
And finally, check your DBM settings by executing a 'db2 get dbm cfg'
there should be a 'SVCENAME' please set this one to the corrosponding
setting in your services.

You can do this by, for example, executing:
'db2 UPDATE DBM CFG USING SVCENAME db2'

Now restart your instance (db2stop/db2start)

Good luck.

Steve Rainbird wrote:
>
> Then I tried to connect and got the following.
>
> $ db2 connect to pear
> SQL30081N A communication error has been detected. Communication protocol
> being used: "TCP/IP". Communication API being used: "SOCKETS". Location
> where the error was detected: "192.168.1.2". Communication function
> detecting
> the error: "connect". Protocol specific error code(s): "111", "*", "*".
> SQLSTATE=08001
> $
>
>
> Any ideas?