Spare my port 1433/4, would you?
Since the SQL Slammer runs rampant on the net, I received so many request on those ports from unknown servers that I have never visited; I am in acknowledge of such because I haev blocked the captioned ports in my firewall, but request still comes in and stolen my bandwidth; seems no fix for these culprits?
Since the SQL Slammer runs rampant on the net, I received so many request on those ports from unknown servers that I have never visited; I am in acknowledge of such because I haev blocked the captioned ports in my firewall, but request still comes in and stolen my bandwidth; seems no fix for these culprits?
Participate on our website and join the conversation
This topic is archived. New comments cannot be posted and votes cannot be cast.
Responses to this topic
Well, having read through your APK.html article, uit surely is fun and informative, albeit in a minimalist approach
I have one point to add is that I have never bind the TCP/IP stack to my homeLAN NIC, since I dont use any ICS on my LAN; I have this for some additional fail-safe precation cheers.
I have one point to add is that I have never bind the TCP/IP stack to my homeLAN NIC, since I dont use any ICS on my LAN; I have this for some additional fail-safe precation cheers.
I am in fact not using a router-hub, just two NIC with dual box; I found this to be effective and apparently no side effect for many OSes and apps. in time span of about a decade!
On a side note, I also never bind microsoft networks client and IPX/netbios protocol to my cable NIC. My network is imcomplete acoording to Microshaft, lol
Your work is valuable anyway, as it encompasses all possible measures to it.
On a side note, I also never bind microsoft networks client and IPX/netbios protocol to my cable NIC. My network is imcomplete acoording to Microshaft, lol
Your work is valuable anyway, as it encompasses all possible measures to it.