Subsonic Forum

I have Comodo Internet Security. I can connect to my server if I disable my firewall. I cannot connect in any other mode.

I have opened the port I selected. Then I used comodo to monitor my activity and found about a half dozen other ports that subsonic or subsonic agent was using, so I added them to my port set. I created an Any Port set so I presume that opens all ports. I added Subsonic Agent and Subsonic Service to my trusted apps. Still no change.

Is there any firewall how to for subsonic? Another odd thing is that my comodo doesn't even put up a notice that someone is trying to connect to my computer, then I could just allow it and hopefully that would configure my firewall for what is needed.

Thanks,

Kevin

Sounds like a Comodo Internet Security issue.
Maybe try a search at Comodo's help pages or doku...

I disabled my firewall, monitored my connections and found the IP that was communicating to Subsonic. I had to add it to my home network. I don't know why I would have to do that since all the other applications that receive internet traffic aren't that way. But it works.

Anyone using Comodo Firewall 7.x and Subsonic successfully?

I have tried . . . a great many combinations of firewall rules and a lack of them -- and tried to adjust portforward.com's instructions to the new Comodo version -- without success. That is, I can connect to Subsonic when Comodo is completely disabled, but not otherwise. And I don't have this problem with utorrent or slsk.

Thanks for yr help.

Did you define Subsonic as a trusted application?

http://personalfirewall.comodo.com/Como ... _Guide.pdf

Page 66

You could also probably add the Subsonic Port(s) as described on page 75-76.

I am assuming that you're not double firewalled and that Comodo is the only firewall on the system...

I've never used Comodo, so I don't know, but would assume that it disables any other system firewall when it's installed.

I ended up uninstalling Comodo (which wasn't easily done). It seems I wasn't the only one having issues with the 7.x version.

It's most likely not a problem as Comodo is probably overkill anyway.

One of the benefits of setting up Subsonic and getting it working is that if you haven't before, you're going to learn quite a bit about firewalls and networks in general, with a healthy dose of port forwarding thrown in.

Within a home network (unless you don't trust your own family) the primary line of defense is the router and/or gateway device that acts as the gatekeeper for communication with the outside world. As long as there are no gaping holes there, you are generally pretty well protected and dropping a firewall on a local machine inside your network usually doesn't constitute much risk.

The default firewalls that are already included on Windows and Linux are sufficient. Commercial or free firewalls like Comodo and others may sound like a big upgrade, but a properly configured firewall is a properly configured firewall. Add to the fact that the primary point of penetration attempts are at the edge device anyway, dropping Comodo shouldn't pose any significant risk.

mookieproof wrote:Anyone using Comodo Firewall 7.x and Subsonic successfully?

I have tried . . . a great many combinations of firewall rules and a lack of them -- and tried to adjust portforward.com's instructions to the new Comodo version -- without success. That is, I can connect to Subsonic when Comodo is completely disabled, but not otherwise. And I don't have this problem with utorrent or slsk.

Thanks for yr help.

Forget Firewall rules, this isn't about Subsonic making its own connections.

Actually, Comodo is very simple to use with Subsonic. I will show you the easiest way (there is more than one way using Global Rules).

I have Subsonic running on 4040 with SSL enabled on 443. Change your own rules according to your own subsonic config.

Step 1 - Open Comodo, Tasks, Advanced Tasks, Advanced Settings, Security Settings, Global Rules. Right Click anywhere in the list and Click Add:


Step 2 - Fill in each tab as follows:




Repeat this process for the SSL enabled port if required.

For the last tab, if you had added all your subsonic ports to the Global Rule for HTTP Ports, you might have this instead:


Don't forget to do your port forwarding on your router!