Eset NOD32 rule for Presonus Studio One and Remote

[David Barrow 0]

I am having a problem with Presonus Studio One Remote (exe) communicating with a running copy of Studio One on another computer. When I turn the firewall off it works just fine. When I turn it back on again I lose the connection. How do I make a firewall rule to all Studio One Remote.exe to communicate with the other computer? I thought I understood how this all works, but nothing I have tried works, other than disabling the firewall in NOD32.

 

 

 

[Marcos 5,462]

You can allow the desired communication via this option:

[David Barrow 0]

I did the "Resolve blocked communication" wizard, but the next time I started Presonus Studio One Remote, the remote computer did not show up. It was blocked by the firewall. As soon as I disabled the firewall, the remote computer showed up again. I could just disable the firewall every time I wanted to use Studio One Remote, but I would rather have a rule in place that actually works. I am not sure what to do differently.

[Marcos 5,462]

Please carry on as follows:

1. Enable advanced logging under Help and support -> Technical support
2. Reproduce the issue
3. Stop logging
4. Collect logs with ESET Log Collector and upload the generated archive here (only the ESET staff can access attachments).

 

[David Barrow 0]

I have attached the log collector results.

eis_logs.zip

[David Barrow 0]

Screen shot of Studio One Remote.

[David Barrow 0]

It shows "Unblocked", but remote instances of running Studio One won't show up until I disable the Eset firewall.

[Marcos 5,462]

You have 106 networks besides the default 2  private and public while every other is marked as trusted. I'd recommend to reduce the networks to the bare minimum and make sure that the two machines that are supposed to communicate are in trusted networks. The current high number of networks prevents me from checking details of each network in other to figure out the root cause.

Also make sure to enable the following settings in the real-time protection setup. The current setup allows otherwise recognized malware to be executed:

Scan on - file open
Scan on - file creation
Scan on - file execution

For maximum protection and efficiency of the Ransomware shield, Deep Behavior Monitor, etc. we strongly recommend enabling the LiveGrid Feedback system as well as detection of potentially unsafe applications to prevent vulnerable drivers from being exploited to infect the machine.

[Marcos 5,462]

I've just found out that the default firewall rules do not exist. All rules starting from nr. 1 were created by the wizard. Please make sure to reset the firewall rules and append custom rules, if needed. Do not replace default firewall rules.

[David Barrow 0]

There are only two networks I use regularly. Most of the others are repeats of the same two. I did not replace any default firewall rules. I'm not sure I even know how. Please give me a step by step recipe for how to reset/remove unwanted stuff.

[Marcos 5,462]

I'd suggest uninstalling ESET and installing Internet Security v17.0.15 from scratch using default settings. Next enable advanced logging, reproduce the issue, disable logging and collect fresh logs with ELC. Along with the logs provide also information about the IP address of the other computer that attempts to communicate with this one and the connection is blocked by the firewall.