ICQ 2000b and MS Proxy 2.0

The simplest answer is to allow everyone to use ICQ. I'd bet you'll find that morale increases, and people actually become more productive.

If there's some reason you can't do that, you can always log accesses on the ICQ port. Make sure all employees know whether or not they're allowed to use ICQ. Then it's just a matter of how you handle employees who violate company policy. Of course, you'll also have to worry about employees who deliberately run ICQ on port 25 or 80.

If perceived productivity is an issue, tell employees that they're required to spend 8 hours a day *not* using ICQ. You'll probably find that some employees start spending 10 and 12 hour days at the office, which means that you're getting 8 hours of work, but 10-12 hours of availability. Very convenient when you're working late and need to ask someone a question.

The simple answer is no, you can't use MS Proxy Server v2.0 to do this. ICQ uses TCP/UDP port 4000 and as far as I know ICQ2000 uses the TCP/UDP ports 5190, 5191, 5192 and 5193. MS Proxy Server 2.0 does not allow port filtering unless you use dual NICs and you don't use an upstream proxy. If you do use two NICs and don't have an upstream proxy then you can filter it out by blocking those four TCP and UDP ports.

So what can you do if you are like most of my clients and only have one NIC or have to use an upstream proxy service? You could either upgrade your proxy server to MS ISA and use ISA's superior filtering and Firewall features. ISA is also a more efficient cache. Downside is that ISA requires continual, and I mean continual fine tuning.
Or consider a packet filter like the Packeteer PacketShaper or NetReality WiseWan.
Unless you have VLANs in place and can easily migrate all godlike users onto a "trusted" VLAN and the plebs onto an "untrusted" VLAN, setting up outbound Firewall rules is pretty well useless. If you do have VLANs in place or have physical separation between LANs, then outbound firewall rules become a viable alternative.
For my clients that have a need to control both costs and access, I often put in place a dedicated packet filter and a dedicated cache device. That way we not only are able to block applications either globally or discretely, but improve cache hits (and therfor internet performance and drop costs) as well as prioritise core application by applying Quality of Service rules.

I hope that this helps or at least gives you some options to pursue

The simple answer is no, you can't use MS Proxy Server v2.0 to do this. ICQ uses TCP/UDP port 4000 and as far as I know ICQ2000 uses the TCP/UDP ports 5190, 5191, 5192 and 5193. MS Proxy Server 2.0 does not allow port filtering unless you use dual NICs and you don't use an upstream proxy. If you do use two NICs and don't have an upstream proxy then you can filter it out by blocking those four TCP and UDP ports.

So what can you do if you are like most of my clients and only have one NIC or have to use an upstream proxy service? You could either upgrade your proxy server to MS ISA and use ISA's superior filtering and Firewall features. ISA is also a more efficient cache. Downside is that ISA requires continual, and I mean continual fine tuning.
Or consider a packet filter like the Packeteer PacketShaper or NetReality WiseWan.
Unless you have VLANs in place and can easily migrate all godlike users onto a "trusted" VLAN and the plebs onto an "untrusted" VLAN, setting up outbound Firewall rules is pretty well useless. If you do have VLANs in place or have physical separation between LANs, then outbound firewall rules become a viable alternative.
For my clients that have a need to control both costs and access, I often put in place a dedicated packet filter and a dedicated cache device. That way we not only are able to block applications either globally or discretely, but improve cache hits (and therfor internet performance and drop costs) as well as prioritise core application by applying Quality of Service rules.

I hope that this helps or at least gives you some options to pursue.

This question was auto closed due to inactivity