I'm currently facing the below issue for a Village Island VFSMON device, which is of smart serial type.
When I point it to communicate with a DMA on a VM, it establishes the TCP connection. However, goes into timeout after 20-30 seconds. In the attached Wireshark captures, it can be seen that the TCP window became full before the connection went into timeout state.
I have tried increasing the TCPWindowSize, Keepalive values in the registry editor. Reducing the polling frequency of the parameters was attempted too.
This behavior is not observed on another DMA which is running on a physical server for the same user. I've tried matching all possible TCP related registry keys between the VM and physical server.
Please let me know if there are any configurations that I can look into.
May I also check if there were any changes in the way TCP connections are handled in DM10 as compared to DM9.5 or DM9.6.
Thank you!
There shouldn't be a difference if you run DataMiner on a VM or a physical server but of course we cannot guarantee that there aren't any issues on the VM platform.
There weren't any changes to our software that could explain the seen behavior and since it's not happening on a physical server it also doesn't initially look like a software issue. However to further debug if something would happen on our side you can enable the extra logging in the portlog.txt (more info can be found in the help)
This question might also be relevant:
https://community.dataminer.services/question/not-receiving-smart-serial-data-in-driver/
For issues with the VM platform you might want to check if there aren't any open tickets related to the VM environment