strangly enough a whole week now router goes fine with no probs so i didnt have to apply the 1.01.08 beta update and still keep 1.01.06 my...
yea sorry for that, router HAD "Firmware Version: 1.01.06" was just looking at an old firmware file like a good idiot i am! yea "- Fixes issue...
there is no spi to disable there is no watchdog or log functionality that can help us find whats happening there is no need to restart a router...
how about find a way to stop this Dos stuff eset does to the network when utorrent dominates the connection?
-firmware is updated as stated numerous times -cant afford new router as stated -prefer to tweak what i have instead of going back to crappy...
i am not looking for logic i am looking for a solution crystal for u?
router firmware wag200g at latest version already 1.00.09 cant stress enough that the problem lies on firewall of eset not my firmware or my...
what gurrantee can u give me and to my friend that by paying 100$ for a new router will solve our problems? if i wanted easy solutions i would...
"You have a router issue to be solved, not a NOD32 one" and that comes from what exactly?? from the fact that a friend of mine has the same issue...
" If any SW can cause the syndromes you are describing" obviusly u havent read anything before thinking to respond the only software cauzing...
oh yea sorry to forgot to mention that i am using xp sp3 not vista and no i dont find it sensible to install a beta security software into my...
both utorrent and svchost are excluded by having cross next to them still issue exists i might add that issue happens with http filter...
spend some time reading the above posts before u suggest something stupid the same problem accurs at a friend of mine reported as utp flood...
finally after a whole week problem started again fresh system unpatched tcpip 672 eset utorrent excluded from http scanning and yes every...
formatted system unpatched tcpip 672 eset not detection of unwated apps no filtering of most stuff excluded utorrent and some other stuff...
some times it takes minutes some times up to 20 hours result is always the same 192.168.1.1 is not responding problem started 1 month ago -...
connections are limited to very low values along with halfmaxopen at 4 besides this only happening with 3.0667 the moment u uninstall it problem...
so this is propably something simple and already mentioned but since i am too retarded to find here it goes eset internet security with nod32...
Separate names with a comma.