LimeWire is a peer-to-peer file sharing client that uses the Gnutella network to find and share files. Because LimeWire uses the Gnutella file-sharing protocol, it is blocked when you block theGnutella (Morpheus Xolox) protocol, in the P2P File Sharing protocol group.
Using MSN Messenger involves making more than one type of Internet request. To ensure thatÂ MSN Messenger is permitted, you must configure Websense Express to permit all of the following: Websense protocolÂ MSN Messenger Websense protocolÂ HTTPS Websense Master Database categoryÂ Search Engines and Portals (in addition toÂ Web Chat andÂ Internet Communication) The “MSN Messenger protocol” must be permitted for [...]
Log entries show permitted permitted protocol requests (for example, RTSP) even though all protocols are configured to be blocked. Even if all protocols are configured as blocked, Real-Time Streaming Protocol (RTSP) and Windows Media requests are occasionally permitted and logged. This also affects report output generated by Websense Explorer. This behavior has to do with [...]
TestLogServer is a command-line utility that displays log traffic sent to Websense Log Server. TestLogServer listens on port 55805, which is the same port used by Websense Log Server. Here is an example of traffic displyed by the TestLogServer: time=Fri Jul 30 09:15:41 2004 version=3 server=10.1.1.1 source=127.0.0.1 dest=188.8.131.52 protocol= “http” url= “http://espn.com/” port= “80″ category= [...]
You can switch between a Stand-Alone installation and an integrated installation or visa versa, by reinstalling the Websense Filtering Service and selecting the appropriate installation type. Before you change your integration, you may want to review the installation appropriate documentation. Make sure the document is specific to the version of Websense and desired integration. If [...]
Starting with version 5.2, Websense Enterprise supports Web filtering of end users running Macintosh computers within customer organizations. This article provides the requirements and restrictions for providing this filtering. This support includes end-user Web browsing and the use of network-based applications such as streaming media players, peer-to-peer clients, and instant messaging clients. With the exception [...]
Configure Network AgentÂ to block HTTPS traffic by configuring the HTTPS option in the Protocol set. SelectÂ EditÂ in the Protocol Set pane. In the Edit Protocol Set window, expandÂ WebÂ and selectÂ HTTPS. SelectÂ Block. ClickÂ OK. See the Websense Web Security Suite and Websense EnterpriseÂ Administrator’s GuideÂ chapter on blocking protocols. The link is provided below. Websense Documentation: Â Websense Web Security Suite [...]
There are two options for blocking HTTPS traffic with a Squid integration: Install Websense Network Agent, which performs protocol filtering, and configure it to block HTTPS traffic.Â For information about installing Network Agent, see the Websense EnterpriseÂ Installation Guide. After installation, detailed information about configuring Network Agent is provided in the Websense EnterpriseÂ Administrator’s Guide. If Squid [...]