RE: ESL 2-port DB9 - activation issue
LavaSupport > 07-29-2015, 04:48 PM
There are several possibilities as to why the ESL isn't being found by the Manager.
Certain firewall or antivirus applications prevent the Manager from sending a broadcast packet out on the network, which is how the Lava Ether Link Manager discovers any Ether-Serial Links present on the LAN. The best way to verify this is by disabling the firewall, or anti-virus, completely and checking to see if that resolves your issue. If that does then I'd re-enable the application and tweak the access rules to allow the Lava Ether Link Manger to send and receive broadcast packets.
Alternatively, that same broadcast packet could be blocked by a router on your network, this is less likely but still could be a possibility. I would just make sure the network path between the ESL and PC is as simple as possible, ideally using a hub or something like that.
I would suggest exploring the above options and refreshing the Lava Manager every step of the way to see if anything changes within the Lava Manager, or if the ESL is eventually detected.
If neither of the two routes pans out then we can always manually create the COM Port, which appears to be what you attempted with Com 3, but we'll leave that as a last ditch effort.
- LAVA Support