<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>The ranting of an IT Professional &#187; known issue</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/it-rant/tag/known-issue/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/it-rant</link>
	<description></description>
	<lastBuildDate>Mon, 19 Sep 2011 18:30:04 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>Websense Web Filter 7.01 &#8211; Unable to download filtering database</title>
		<link>http://itknowledgeexchange.techtarget.com/it-rant/websense-web-filter-701-unable-to-download-filtering-database/</link>
		<comments>http://itknowledgeexchange.techtarget.com/it-rant/websense-web-filter-701-unable-to-download-filtering-database/#comments</comments>
		<pubDate>Wed, 26 Aug 2009 13:20:19 +0000</pubDate>
		<dc:creator>Jason Tramer</dc:creator>
				<category><![CDATA[7.01]]></category>
		<category><![CDATA[hot fix]]></category>
		<category><![CDATA[known issue]]></category>
		<category><![CDATA[unable to download filtering database]]></category>
		<category><![CDATA[web filter]]></category>
		<category><![CDATA[websense]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/it-rant/websense-web-filter-701-unable-to-download-filtering-database/</guid>
		<description><![CDATA[I have been working with Websense to get a fix for an issue i have been having in Web filter 7.01 where I was unable to download the filtering database. This is apparently a known issue which has a hotfix. Here are the details of downloading and installing the hotfix. Go to http://eval.websense.com/download/patches/WWF_7.0.1_Hotfix_26_WISP_Trace_Issue_binaries.zip 1. Stop [...]]]></description>
				<content:encoded><![CDATA[<p>I have been working with Websense to get a fix for an issue i have been having in Web filter 7.01 where I was unable to download the filtering database. This is apparently a known issue which has a hotfix. Here are the details of downloading and installing the hotfix.</p>
<p><!--[if gte mso 9]&gt;  Normal 0     false false false  EN-US X-NONE X-NONE                            &lt;![endif]--><!--[if gte mso 9]&gt;                                                                                                                                            &lt;![endif]--></p>
<p class="MsoPlainText">Go to</p>
<p class="MsoPlainText"><a href="http://eval.websense.com/download/patches/WWF_7.0.1_Hotfix_26_WISP_Trace_Issue_binaries.zip">http://eval.websense.com/download/patches/WWF_7.0.1_Hotfix_26_WISP_Trace_Issue_binaries.zip</a></p>
<p class="MsoPlainText">
<p class="MsoPlainText">
<p class="MsoPlainText">1. Stop all Websense services.</p>
<p class="MsoPlainText">
<p class="MsoPlainText">When you stop all Websense services, the sequence of stopping them is important for the final three services only. Always end with the following services, in the order shown:</p>
<p class="MsoPlainText">1. Stop Websense Policy Server.</p>
<p class="MsoPlainText">2. Then, stop Websense Policy Broker.</p>
<p class="MsoPlainText">3. Finally, stop Websense Policy Database.</p>
<p class="MsoPlainText">
<p class="MsoPlainText">Linux: Use the command ./WebsenseAdmin stop (Run the command from the /opt/Websense/ directory). This stops them in the correct sequence.</p>
<p class="MsoPlainText">
<p class="MsoPlainText">2. Back up the files listed below into a separate folder:</p>
<p class="MsoPlainText">
<p class="MsoPlainText">Windows:</p>
<p class="MsoPlainText">The default location for Windows is: C:\Program Files\Websense\bin\</p>
<p class="MsoPlainText">EIMServer.exe</p>
<p class="MsoPlainText">EIMService.dll</p>
<p class="MsoPlainText">NetworkAgent.exe</p>
<p class="MsoPlainText">WsEventLog.dll</p>
<p class="MsoPlainText">natuning.ini (if present)</p>
<p class="MsoPlainText">
<p class="MsoPlainText">Linux:</p>
<p class="MsoPlainText">The default location for Linux is: /opt/Websense/bin/</p>
<p class="MsoPlainText">EIMServer</p>
<p class="MsoPlainText">NetworkAgent</p>
<p class="MsoPlainText">libWsEventLog.so</p>
<p class="MsoPlainText">natuning.ini (if present)</p>
<p class="MsoPlainText">
<p class="MsoPlainText">3. Extract the Hotfix zip file and locate the following files:</p>
<p class="MsoPlainText">
<p class="MsoPlainText">Windows:</p>
<p class="MsoPlainText">EIMServer.exe</p>
<p class="MsoPlainText">EIMService.dll</p>
<p class="MsoPlainText">NetworkAgent.exe</p>
<p class="MsoPlainText">WsEventLog.dll</p>
<p class="MsoPlainText">natuning.ini</p>
<p class="MsoPlainText">
<p class="MsoPlainText">Linux:</p>
<p class="MsoPlainText">EIMServer</p>
<p class="MsoPlainText">NetworkAgent</p>
<p class="MsoPlainText">libWsEventLog.so</p>
<p class="MsoPlainText">natuning.ini</p>
<p class="MsoPlainText">
<p class="MsoPlainText">4. Replace the files listed above with the corresponding files included in the Hotfix zip file:</p>
<p class="MsoPlainText">
<p class="MsoPlainText">Default location in Windows: C:\Program Files\Websense\bin\</p>
<p class="MsoPlainText">Default location in Linux: /opt/Websense/bin/</p>
<p class="MsoPlainText">
<p class="MsoPlainText">5. Make any needed configuration changes to natuning.ini.</p>
<p class="MsoPlainText">
<p class="MsoPlainText">If you have customized this file previously, start with your copy of the customized file, and then change or add settings that are provided by this Hotfix.</p>
<p class="MsoPlainText">
<p class="MsoPlainText">(a) To configure Network Agent to ignore HTTPS traffic:</p>
<p class="MsoPlainText">
<p class="MsoPlainText">Change the configuration variable &#8216;IgnorePort80&#8242; to &#8216;IgnorePorts&#8217; in the natuning.ini file. This parameter tells Network Agent to ignore traffic on any ports at the driver level.</p>
<p class="MsoPlainText">
<p class="MsoPlainText">For example:</p>
<p class="MsoPlainText">IgnorePorts = 80, 443</p>
<p class="MsoPlainText">
<p class="MsoPlainText">(b) To prevent the IP addresses of the Network Agent interfaces from being displayed in Websense Manager:</p>
<p class="MsoPlainText">
<p class="MsoPlainText">Add the configuration variable &#8216;ShowNICsIP&#8217; to the natuning.ini file and set it to false.</p>
<p class="MsoPlainText">ShowNICsIP = false</p>
<p class="MsoPlainText">
<p class="MsoPlainText">In the natuning.ini file supplied with this hotfix both of these settings have been commented out. To enable one of the settings, simply remove the &#8216;#&#8217; character from the beginning of the line.</p>
<p class="MsoPlainText">
<p class="MsoPlainText">6. Restart Websense services.</p>
<p class="MsoPlainText">
<p class="MsoPlainText">Windows: Use the Windows Services dialog box.</p>
<p class="MsoPlainText">
<p class="MsoPlainText">When you start all Websense services, always begin with the following services, in the order shown:</p>
<p class="MsoPlainText">1. Websense Policy Database</p>
<p class="MsoPlainText">2. Websense Policy Broker</p>
<p class="MsoPlainText">3. Websense Policy Server (all copies)</p>
<p class="MsoPlainText">
<p class="MsoPlainText">Then, remaining services can be started in any order.</p>
<p class="MsoPlainText">
<p class="MsoPlainText">
<p class="MsoPlainText">Linux: Use the command ./WebsenseAdmin start. This command starts the services in the proper sequence.</p>
<!-- wpms-network-global-inserts -->]]></content:encoded>
			<wfw:commentRss>http://itknowledgeexchange.techtarget.com/it-rant/websense-web-filter-701-unable-to-download-filtering-database/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Fireware 11 has been released!</title>
		<link>http://itknowledgeexchange.techtarget.com/it-rant/fireware-11-has-been-released/</link>
		<comments>http://itknowledgeexchange.techtarget.com/it-rant/fireware-11-has-been-released/#comments</comments>
		<pubDate>Thu, 20 Aug 2009 13:33:18 +0000</pubDate>
		<dc:creator>Jason Tramer</dc:creator>
				<category><![CDATA[11]]></category>
		<category><![CDATA[12]]></category>
		<category><![CDATA[bugs]]></category>
		<category><![CDATA[Fireware]]></category>
		<category><![CDATA[known issue]]></category>
		<category><![CDATA[WatchGuard]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/it-rant/fireware-11-has-been-released/</guid>
		<description><![CDATA[So in the past I have criticized Watchguard a tad when they constantly give me the answer that my issue is a known bug and will be fixed in the next version &#8230; Well the next version is here! Fireware 11 has been released to the general public. I will get trying it out in [...]]]></description>
				<content:encoded><![CDATA[<p>So in the past I have criticized Watchguard a tad when they constantly give me the answer that my issue is a known bug and will be fixed in the next version &#8230;</p>
<p>Well the next version is here! Fireware 11 has been released to the general public. I will get trying it out in the coming days and reporting back here but a quick look in my IT crystal ball tells me that Watchguard will have indeed fixed all those little bugs which plagued my existence for so many months. Before Watchguard draws too much succor from my words I should also point out that my IT crystal ball tells me that I will be soon plagued with a ton of new bugs which won&#8217;t be fixed till version 12 comes out.</p>
<!-- wpms-network-global-inserts -->]]></content:encoded>
			<wfw:commentRss>http://itknowledgeexchange.techtarget.com/it-rant/fireware-11-has-been-released/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
