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?
.NET Remoting is not really firewall friendly, so I believe it might be difficult what you are trying to achieve here. .NET Remoting is also deprecated, and therefore we have a replacement, namely gRPC. This new communication channel only requires 443 and therefore it's going to be a lot easier for firewall configurations...
gRPC is currently available in preview in the latest release (10.3.2) and will be supported in production in one of the upcoming releases. So, it might be worth looking at that as a more decent solution instead of losing time on this .NET Remoting which is EOL anyhow...
Could not agree more, Bert – indeed it is quite a large range of ports that Microsoft designed in .NetRemoting for eventing to work, but once that is allowed, I’ve always been able to get it to work – we are using DM 10.2.10.0 now, but can surely check a newer version of DM if this set-up becomes redundant once https comms are in place.
As for more recent versions of CUBE & DataMiner, are there any additional restrictions added on a client Windows Firewall when CUBE is installed?
Sharing a screenshot in a new reply
(cannot upload images in comments – https://community.dataminer.services/new-feature-suggestions/add-image-in-comments/ )
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.