<< AIM will connect on port 80 without problems. >>
Didn't know AIM was such a pain to get rid of, go figure, its AOL. I figured that AOL didn't use HTTP, so it would be easy to block, but it sounds more like Yahoo! messanger now. Does AIM use UDP? If it used UDP, you could block that and be done with it.
<< You can setup a proxy in AIM. >>
I guess you could do that (just like any other IM), but if the users didn't have the password to use any port other than 80, then AIM wouldn't be able to connect since the proxy wouldn't let them out. Now that AIM can use port 80, its pretty annoying to stop.
<< Block the ip address of the login server at the firewall, along with doing something like this. Much easier. >>
What if someone had an external proxy forwarder setup? Someone could point their AIM to that external IP and have that external IP forward the information on. This is a common method to get net based games working through restrictive firewalls.
Win95 has ways to be restrictive (you must install admin addons), you could do:
- Don't let them run anything more than iexplore.exe.
- Disable the Start Menu for the default user.
- Don't let them Run anything.
- Don't let them shell to command prompt.
- Don't let them regedit.
- Run ZoneAlarm, put a password on it and use the strictest settings. Run iexplore.exe, let that out and tell ZoneAlarm to never let anything else out unless they know the admin password.
If you really want to lock them down, don't run Windows 95 -- run some flavor of Windows NT, or another OS that doesn't have AIM support and is more difficult to get running (FreeBSD, BeOS, but you'd have different sets of issues there).
Another thing to do is Ghost (or drive copy) the disk images on the machines, so you can just reimage the machines after each period. Sure, its a few minutes, but its less time then uninstalling all their crap
Last, but not least, tell them that any user caught will have their access removed for X amount of days. Be loud about it and you'll see less AIM users around.
vash