Check this out:
11/25/2009 12:34 AM,Info,Firewall configuration updated: 55 rules.,Detected,No Action Required,Firewall - Activities,,,,,,
11/25/2009 12:34 AM,Info,Firewall rules were automatically created for Computerized lighting controller.,Protected,No Action Required,,Computerized lighting controller,<path>C:\myDMX\esa.exe</path>,No Action Required,Automatically create rules,"10.1.42.225, 2430","Outbound UDP, Port 2430"
11/25/2009 12:34 AM,Info,Firewall configuration updated: 54 rules.,Detected,No Action Required,Firewall - Activities,,,,,,
11/25/2009 12:34 AM,Info,Firewall rules were automatically created for Computerized lighting controller.,Protected,No Action Required,,Computerized lighting controller,<path>C:\myDMX\esa.exe</path>,No Action Required,Automatically create rules,"0.0.0.0, 2430","Inbound TCP, Port 2430"
11/25/2009 12:34 AM,Info,"An instance of \"<path>C:\myDMX\esa.exe</path>\" is preparing to access the Internet.",Detected,No Action Required,Firewall - Activities,,,,,,
Well, first off, you can tell I'm up late working. But that's nt relevant.
Check out where esa.exe is attempting to access the internet. Why would it need to do that? Clearly, I've used MyDMX without any sort of network access and it works fine.
Perhaps the developers have an explanation. Personally, I'm leaning towards some sort of goofy mis-interpretted error.
Also note the eexclusion rules too, which tend to support esa.exe accessing the internet for no reasons. But again, I don't totally trust Norton 360.
Note: This won't stop me from using MyDMX unless network access becomes required, which would really hose me bad since I disable my wifi when doing shows, and don't connect via Cat5 either(no router or network used at my events currently outside of Aviom A-net and that's an input unit to an output unit only).
Original Post