I've been blocking things as I find them on my corporate network now that I have the sonicwall running - junk that users shouldn't really be doing during business hours. I wanted to get a baseline read of what traffic we *really* use for business and hosting purposes on our two T-1's.
But there are so many things out there that jump from port to port, that can span a range of thousands of ports if necessary, that it's impossible to individually block them. What's the general consensus out here in sonicwall listland regarding blocking unwanted protocols - how many of you block things individually, and how many of you just block everything and then open specific ports for necessary functions? I'm very close to redoing my rule set to only allow the few protocols I know we need, then after that have a few rules to block everything else. Suggestions from those in the trenches who've gone here already? I figured I'd look into this since I've had no joy with the XP VPN client. Just can't get it to connect no matter what I do.... Time for something else to occupy me for a while so I can take a VPN break. :> John --- [This E-mail scanned for viruses by Declude/F-Prot Virus] =================================================================================================== To unsubscribe, send email to [EMAIL PROTECTED] In the body of the email put the following: unsubscribe sonicwall your_name The archive of this list is at http://www.mail-archive.com/sonicwall%40peake.com/
