This is a targeted approach, and it takes a little more work, but you can combine it with other methods to make...
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
it extremely effective. Combine this with preventing software installations (see step four), and you can keep the vast majority of messenger clients off your network.
Messenger clients usually have to log on to a central server to work properly. Ergo, the best way to block messenger clients is not to block the ports they use, but the central servers they use. For instance, AOL Instant Messenger's logon server is login.oscar.aol.com, which resolves to four IP addresses: 126.96.36.199, 188.8.131.52, 184.108.40.206, and 220.127.116.11. Block both the domain name and the IP addresses, and AIM should no longer work. (Blocking all of aol.com is probably impractical, but blocking just AIM's logon server should not pose any other problems.) For Yahoo! Messenger, the most commonly used logon addresses are msg.edit.yahoo.com, edit.messenger.yahoo.com, csa.yahoo.com, csb.yahoo.com, and csc.yahoo.com. (The IPs for these may vary, so be sure to check them.)
If you come across other clients you want to block, it should be easy enough to run them on a computer in a DMZ, analyze the connections they attempt to make with the command-line netstat tool, and then block all the sites they try to use. Note that static IPs for servers might change over time, so you may want to periodically re-check the IP addresses for any given logon server and make sure it's still being blocked.
Blocking IM and P2P
Step 1: The "easy, but stupid" approach
Step 2: The "block the nexus" approach: IM
Step 3: The "block the nexus" approach: P2P
Step 4: The "block the application" approach
More information from SearchWindowsSecurity.com
|ABOUT THE AUTHOR:|
|Serdar Yegulalp is editor of the Windows Power Users Newsletter. Check it out for the latest advice and musings on the world of Windows network administrators -- and please share your thoughts as well! Copyright 2005 TechTarget|