|
Prev: Microsoft Firewall vs ????
Next: ICT firewall Security
From: fred fleagle on 31 Mar 2008 19:28 Comodo blocks port forwarding from router, programs can't receive incoming connections. Can someone suggest a way to allow port forwarding? Thanks from fred fleagle -- Posted via a free Usenet account from http://www.teranews.com
From: Volker Birk on 1 Apr 2008 00:37 fred fleagle <fgh(a)dot.net> wrote: > Comodo blocks port forwarding from router, programs can't receive > incoming connections. > Can someone suggest a way to allow port forwarding? Yes. Drop Comodo. Yours, VB. -- The file name of an indirect node file is the string "iNode" immediately followed by the link reference converted to decimal text, with no leading zeroes. For example, an indirect node file with link reference 123 would have the name "iNode123". - HFS Plus Volume Format, MacOS X
From: "Mr. Arnold" MR. on 1 Apr 2008 16:14 "fred fleagle" <fgh(a)dot.net> wrote in message news:47f15c4c$0$30486$88260bb3(a)free.teranews.com... > Comodo blocks port forwarding from router, programs can't receive > incoming connections. > Can someone suggest a way to allow port forwarding? > You go to the personal packet filter/personal firewall and you open the same ports on it as you did on the router.
From: Poutnik on 5 Apr 2008 03:50 Dne Tue, 01 Apr 2008 01:28:11 +0200 fred fleagle <fgh(a)dot.net> napsal/-a: > Comodo blocks port forwarding from router, programs can't receive > incoming connections. > Can someone suggest a way to allow port forwarding? > I have no problems with forwarded ports with Comodo. Especially at firewalls, all FW is as good as its configuration. Well, it can be worse, but never better. check proper forwarding at router, and incoming connections in comodo in both Application and Network monitor. Remember if there is not allowed incoming traffic in network layer, it does not matter what is allowed at application layer. First step in blaming is always my own hands, blaming product is next step.
From: Sebastian G. on 5 Apr 2008 04:34
Poutnik wrote: > I have no problems with forwarded ports with Comodo. > > Especially at firewalls, all FW is as good as its configuration. > Well, it can be worse, but never better. And Comodo is worse, since it doesn't even allow proper configuration even in the most simple scenarios. > Remember if there is not allowed incoming traffic in network layer, > it does not matter what is allowed at application layer. There is no matter to the latter anyway. > First step in blaming is always my own hands, > blaming product is next step. Unless you know what you're doing. |