Please, Dojo - I'm trying to detail the exact behaviour of a CUBE client connecting to a DMA via
.NET-Remoting>Eventing (this to facilitate FW configs).
On connection to a DMA, I seem to get at least one connection established, however the client switches to polling mode.
The output of a netstat on the client would show something like this:
It seems the ports in the "high port range" (49152 through 65535) are allowed on the client - the connection is actually "ESTABLISHED" to port 8004 of the server - via client port 51134, but then why the client has a second connection open in "TIME WAIT" and eventually switches to polling?
Is more than one port required on the client for eventing?
Or could the server be configured to use polling regardless of the connection successfully established between client port 51134 and server port 8004?
Cube settings for the above test were like this:
Any steer will be helpful
Need to resume testing on this – I seem to have different numbers of connections depending on the environment – I will update the thread as soon as I gather some more data
Hi Alberto,
I see that this question has been inactive for a long time. Do you still need more information about this? If not, could you select the best answer to indicate that no further action is needed here?
As this question has now been inactive for a very long time, I will close it. If you still want more information about this, could you post a new question?
Based on testing, I believe 9 ports are open on the client side in the attempt to establish the communication for Eventing - sadly, none of them is working for me, but based on testing with DM 10.2.10.0-12242, I can see 9 ports towards 2 different DMAs:
1) .7 is my client IP, .11 is the DMA where connection with port 8004 is expected;
I can see 9 ports, seven are in Time_Wait while two ports show an established connection - nevertheless, Cube switches to polling
2) same here, .7 is my client, .213 is the DMA, where 8004 seems to be in communication with 9 ports open on the client side - still no joy, Cube fails eventing and switches to "polling" again 
Hi Alberto,
I see that this question has been inactive for some time. Have you found a solution for this yet? If yes, could you share some more information about this, and select the best answer (using the ✓ icon)? If not, you can also contact techsupport@skyline.be for assistance.