* multicast ON

* listen IP 127.0.0.1 NOT good, only works with locally on same PC (socat can relay of course)

* Listen local IP tried also (eg.: 192.168.x.x), yes, that is possible to connect from LAN, usually

* serial connected to the device (VEMS ECU)

** windows firewall totally off

** or just enabled the listen via the popup, when VT first starts to "listen"

Slave VT with "multicast (server): OFF") (for logging, viewing, NOT to change values):

* Preferences/Communication: TCP IP: IP+ port of the master VT

** NOTE: multicast: OFF normally (unless setting up some special deep-tree topology, if you really know what you are doing, almost never needed: just configure OFF)

** again: the slave VT has "multicast (server): OFF", and the IP of the master VT is entered in the Preferences/Communication: (enabled), TCP IP (instead of serial), not under the multicast (server) settings (Preferences/Internet).

** This might be confusing at first, because the "Listen" (usual) and "Connect" (special, if firewall is so strict that Listen is impossible) mode of the multicast=ON are both related to the multicast Master server (they are NOT peers of each other as one might think).

The second vemstune connected for Marcell

* just tested 2017-02-05 VT (Multicast=On), worked immediately. Newer (or somewhat older) VT was tested earlier. The slave is rather traditional

* did NOT connect for Zoltan.

** VT version ?

** If it does not work, can you take screenshot of the Preferences/communication dialog (and promise that multicast=OFF ?)

** do you have some tools to sniff during test, eg. socat, hexdump, tee or similar ?

** note: multicast=ON and IP: port of the master is not a good configuration => unspecified behavior (2 servers peered to each other, both waiting for query commands from a normal VT, they may do nothing, or even get confused: "unspecified")