Choose from several options for complete web, email and data security.
Learn more
Evaluate Websense products by watching demos and installing evaluation software.
Learn how Websense solutions help keep our customer safe, secure and productive
Get information on product updates, support resources and more.
Get the most out of support in five simple steps.
Find tools and assets to help sell Websense solutions.
Come work for the global leader in unified information security. Go
Running Websense Enterprise 6.3 is it possible to block or allow single Windows Media addresses? I can allow or block single HTTP addresses through the Recategorized and Not Filtered sections. I am allowing Windows Media streaming for training resources but need to block Internet Radio streaming. I already have the 'Internet Radio and TV' category blocked in the Bandwidth group. Certain users are crafty enough to connect to the stream directly without using the launcher site that I have blocked. The RTA shows "Windows Media://96.17.8.151".
Thanks in advance,
Jim
Hi there,
Are the training recource and the radio stuff in the same site? If not, you may block streaming media category and the windows media protocol, create a custom protocol whose port is "all ports" and ip address is that of the training recource site, then permit this protocol in the protocol set being used.
Cheers
This solution does not work, at least not with WebSense 7.6
For instance, there is a Cal/EPA Webcast site that my users need to get to. There is a Test URL at this page:
http://www.calepa.ca.gov/broadcast/
We have a bandwidth cap for all non-business essential categories and protocols, including Windows Media during high-bandwidth times. This was blocking their access to this site during a high-bandwidth time.
I see that this site has the media hosted at media.ciwmb.ca.gov. This resolves to the California Teale Data address space. As we already allow all .gov sites, I figured there would be no problem following the suggestion in this thread of adding a custom protocol.
I created the custom protocol with all ports, IP Address Range 205.225.128.0 - 205.225.255.255, transport method TCP. To test to see that it worked, I set the override action to Block. I tested the URL again, still allowed. Real-time show it is allowed. I restricted it to only port 80, but it still doesn't block.
For now I have no choice but to remove my bandwidth filter for Windows Media.
