4.0.467.0 Blocking

[robis]

Hi i tested 4.0.467.0 and I have firewall log full of strange blocking ... how do i correct or what cause this?

every 1 second i have 2 or 3 blocked connection
screen:
http://img62.imageshack.us/img62/5003/blocking.jpg

[Marcos]

Maybe an attack from a 192.168.1.1 had been detected before and all subsequent communication attempts were blocked. Does this somehow affect network communication? (browsing, sharing, network-aware applications, etc.) Does disabling the "Blokovat nebezpečnou adresu po detekovaném útoku" option make a difference?

[robis]

-{ Quote: "Maybe an attack from a 192.168.1.1 had been detected before and all subsequent communication attempts were blocked. Does this somehow affect network communication? (browsing, sharing, network-aware applications, etc.) Does disabling the "Blokovat nebezpečnou adresu po detekovaném útoku" option make a difference?" }-

slowing my download only ... pings are ok, upload ok too only download gets from 700KB/s to 200-300KB/s.

on second PC where is Windows XP 32bit, connected to same router is all ok but on this PC there is a only few blocking meybe 1 per munute

my pc has windows vista 64b

all PC has got latest windows updates and latest version of eset ss 4 means 467 build

By disabling this option as you describe

firewall is still logging but speed is getting better it is from 200-700
I am not sure but it is look like that somebody or some program scanning my port.

[robis]

Maybe I found problem:

in network connection (thanks for that utility :) ) i see that one program caled Flashget still comunicating even it is not used. Here is this ports witch ESSET blocking.

I dont understant 2 things why ESET blocking when Flashget is allow by rule?

Second is why Flashget is trying comunicate even is not used?

(Flashget is download manager)

after uninstaling Flashget all is ok with ticked BLOCKING (I am sorry for disturbing :) )

Could somebody answer to my questions?

[ccomputertek]

This can also happen if you use a torrent program.Eset allows it while the program is running, but after you close the program people are still trying to connect to that port for awile and Eset no longer allows it because it sees that program has closed.

seems like something similiar is happening here.also 192.168.1.1 is your default gateway router addy.