Hello, I have been using some of my spare time trying to understand this behaviour.
I was not sure, but the testing I've made pointed in the direction of the ETh2 module. So, since I was looking to upgrade it anyway, I ordered an Eth3 that arrived today.
Immediately I went to the UCM and replaced the old module with the new one.
Frustration hits. It was not working even with the new Module. Checked everything possible with no success until a fortunate event pointed me in the right direction.
I was disabling DHCP and setting a Fixed IP on 192.168.1.5 (the same IP I had for years and since I have some custom processes looking at Comfort at that address I wanted to keep it like it was). On one of the tests I left the DHCP on.
Collected the IP that was assigned to Comfort and try it. It worked !!!Now back to testing a fixed IP. This time tried a different one 192.168.1.10. And it worked !!!
So, without too much science I now know that I can't use the old IP in order for it to work.
Not sure what is causing the problem with that specific IP, maybe some conflict ... will have to investigate further, but I'm now back to having IP connection to my system.
From my knowledge Eth2 supports only one connection, right?
I forgot I had a running script on an old machine connecting to the Comfort System. That connection take over the available connection.
With Eth3 I configured teh script to connect to port 1001 and Comfigurator to connect to 1002.
Everything is ok now. I can even use the old IP.
So if you are experiencing this issue consider the number of connections.
(meanwhile, why is the number of connection limited? RAM?)
The number of connections to a port is limited to 1, even for ETH03. This limitation is normal for such connections. There is a secuerity issue, because a connection eeds to log in to connect. If another conection is allowed, it may be able to send commands without log in.