Has anybody experience with situations that can cause a Cube to switch to polling for other reasons than ports being blocked (i.e. allegedly all proper ports are open, and Cube keeps falling back to polling)?
When Cube connects to the DMA, Cube will open a random port to which the DMA has to connect to send eventing notification messages. If only Cube is able to connect to the DMA, and the DMA not to Cube, then Cube switches to polling. This happens when ports towards the client are blocked, or when the client is behind NAT, which makes that the DMA isn’t able to connect to Cube on the client machine.
I got a similar issue when running our automated tests in Ranorex. Cube is also switching to polling. When you start Cube manually on that client there’s no switching back to polling. For the moment I haven’t found the root cause why the firewall rule isn’t applied.
Hi Maarten,
Normally when you start Cube for the first time, you get a popup from the firewall to add it to the allowed apps. Maybe your automated run is launching the app from a different path, and therefore not allowed anymore since the allowed apps are added based on their path. You can try adding it to the allowed apps manually with the correct path in Control PanelAll Control Panel ItemsWindows Defender FirewallAllowed apps.