We have a problem with one of our users on the network at our remote jobsite.
He insists on using Yahoo Chat and MSN Messenger during work hours. He has been warned numerous times to stay off these applications but choses to ignore. We do not want to teminate this young lad as he has a lot of potential.
Here are some of the networking details.
We are still on a peer to peer network configuration.
This machine is setup with a static I.P. 10.116.101.27
I do not have access to the Cisco 1750 router which is in place.
We want to block the ports that these applications are using at this static I.P. 10.116.101.27
If possible I wish to block the ports during this time frame. (6a.m. to 6p.m.)
Is there software available that will help me with blocking this activity ?
Thanks for the help.
Ironbender
Nov 4 2005, 01:03 PM
Hi DS,
It's possible to manually block the ports using firewall rules, but you may take a look at this:
http://www.plevna.f9.co.uk/Hope it will help,
Chris
Thanks ... that looks like it may do the job.
We are behind a Infosat controlled Cisco hardware firewall ... I have no access rights to that as well.
I will have a good look at your link.... thank you.
rknol
Dec 5 2005, 06:03 PM
Beware that a lot of applications (Messenger, Chat etc) can proxy over port 80 (HTTP). If you block the published messenger ports the program may try and go over port 80 which you will then also have to disable, preventing that person from surfing the web.
We have the same problem at our office. Our firewall blocks all outgoing packets other than 80 (HTTP) and 443 (HTTPS). Still programs like iChat, Messenger, RealPlayer, MediaPlayer etc find their way out of the building.
Our solution was to create an "internet agreement" that all emlpoyees have to sign. It basically says that they shall not download/obtain sensitive material (read: p0rn) and use non-approved software (shareware etc). Still some employees abuse the system, but they get a warning, then a writeup in their file and at the third strike they can be fired.
You may look at taking away his administrative rights (e.g. in Windows 2000/XP ensure he's not part of the local administrators group) and remove the offending applications. But you will never get rid of the problem completely.
Ronald.