I've been reading for a few days on the net about this, but can't seem
to find any concrete answers.

I'm running XP PRO SP2
2.00 GHZ AMD
1 GIG RAM
IE7
on a small office network using Linksys WRT54G v.8

I'm wondering if there is a way (on the network level) to block access
to IM/CHAT programs that use randomly generated ports and port
tunneling. I have a Linksys WRT54G v.5 that has been "upgraded" with
DD-WRT v.23 SP2, at my disposal as well.

This is not a dire situation, but it would be nice.

If anyone can help...thanks! If not....thanks!

Gracias in advance,

CRS

crs <claytonrstone [at] gmail.com> wrote:
> I'm wondering if there is a way (on the network level) to block access
> to IM/CHAT programs that use randomly generated ports and port
> tunneling.

Sure. Don't install/run those programs in the first place. Problem
solved.

cu
59cobalt
--
"If a software developer ever believes a rootkit is a necessary part of
their architecture they should go back and re-architect their solution."
--Mark Russinovich

On Sep 12, 11:25 am, Ansgar -59cobalt- Wiechers
<usenet-2... [at] planetcobalt.net> wrote:
> crs <claytonrst... [at] gmail.com> wrote:
> > I'm wondering if there is a way (on the network level) to block access
> > to IM/CHAT programs that use randomly generated ports and port
> > tunneling.
>
> Sure. Don't install/run those programs in the first place. Problem
> solved.
>
> cu
> 59cobalt
> --
> "If a software developer ever believes a rootkit is a necessary part of
> their architecture they should go back and re-architect their solution."
> --Mark Russinovich

I'll just stick with using Software Restriction Policies

crs <claytonrstone [at] gmail.com> wrote:
> On Sep 12, 11:25 am, Ansgar -59cobalt- Wiechers wrote:
>> crs <claytonrst... [at] gmail.com> wrote:
>>> I'm wondering if there is a way (on the network level) to block
>>> access to IM/CHAT programs that use randomly generated ports and
>>> port tunneling.
>>
>> Sure. Don't install/run those programs in the first place. Problem
>> solved.
>
> I'll just stick with using Software Restriction Policies

SRP are a way to achieve what I wrote.

cu
59cobalt
--
"If a software developer ever believes a rootkit is a necessary part of
their architecture they should go back and re-architect their solution."
--Mark Russinovich