On Tue, Dec 17, 2002 at 12:23:32AM +0100, jochen wrote:
> 00:13:09 client_GetVenusId: got new host 192.168.0.2:32780
> 00:13:09 Building callback conn.
> 00:13:09 Callback message to 192.168.0.2 port 32780 failed
> RPC2_NOTCLIENT (F)
> 00:13:09 Worker1: Unbinding RPC connection 330829604
> 
> what could be a possible error? While writing this I realized that the
> client is v5.3.19 while the server is 5.3.20, could this cause the
> error?

Basically your client connects to the server and says 'hey I'm a new
client'. Then the server tries to set up the callback connection but
fails to connect to the ip/port number of the sender of the incoming
RPC2 requests.

Typically this is caused by a bad firewall setup or incorrect routing.
I don't know how your setup is, but 192.168.0.2 is an address in a
private range, so it is typically not routable across the internet.

Perhaps you have a firewall that is passing packets through, but doesn't
do any ip header rewriting (NAT/masquerading), and as a result the
server cannot send any responses back to the client, it simply doesn't
know the right address to get back to the client.

Jan