> Thanks for your answer. This does indeed raise more questions.
> I tried this without zebedee, and used ethereal on my client to
> trace network activity. What I noticed was that "normal" traffic
> via port 3050 showed IP addreses = the client and the public ip
> address of the server's router. (Fine).
>
> As soon as an event occurred, I saw in the ethereal log on the
> server entries with the IP address of the server machine, not the
> router. i.e. 192.168.0.101.
>
> So the question is:
> Suppose that the server RemoteAuxPort = 4321, how does the client
> know, when something arrives on port 4321, that it is firebird-
> related?
>
> regards, Colin
>

when the client registers interest in an event, then server responds by
telling the client what port it will use - I suspect. If you get zebedee to
handle your events too (not really necessary) then you would need to
intercept that port as well, but you also need to dig into the event
component source to see what's going on there. The registration occurs on
the normal port and the answer from the server is on the normal port but
event notification will happen on the separate port.
Alan