 




<?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; Net Stumbler</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/it-rant/tag/net-stumbler/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>Troubleshooting wireless networks</title>
		<link>http://itknowledgeexchange.techtarget.com/it-rant/troubleshooting-wireless-networks/</link>
		<comments>http://itknowledgeexchange.techtarget.com/it-rant/troubleshooting-wireless-networks/#comments</comments>
		<pubDate>Thu, 14 Aug 2008 19:42:28 +0000</pubDate>
		<dc:creator>Jason Tramer</dc:creator>
				<category><![CDATA[IT professional]]></category>
		<category><![CDATA[Net Stumbler]]></category>
		<category><![CDATA[Wireless]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/it-rant/troubleshooting-wireless-networks/</guid>
		<description><![CDATA[Wireless networks are getting more and more common and with good reason, they are damn useful, particularly when you get a lot of guests or vendors who visit your office. However they can be an absolute pain in the butt to troubleshoot. Part of this is because in a 9 times of 10 the person [...]]]></description>
				<content:encoded><![CDATA[<p>Wireless networks are getting more and more common and with good reason, they are damn useful, particularly when you get a lot of guests or vendors who visit your office. However they can be an absolute pain in the butt to troubleshoot. Part of this is because in a 9 times of 10 the person installing it buys the cheapest linksys or d-link wireless router they can find and installs it with the standard settings so you end up have 15 networks in proximity all with the same name and all on the same channel. It also  seems that some people  don&#8217;t see the correlation between the 2.4 ghz router they bought and all those cordless phones in their office that say 2.4 ghz on them. Plus why don&#8217;t some people realize that security could be important. To quote one of my co-workers &#8220;God bless the people who don&#8217;t realize they should put some form of security on their wireless networks because otherwise I would have to pay for internet at home&#8221;, great for your neighbours, bad for your network.</p>
<p>So there is a bunch of stuff that can go wrong but how do you make it right? Well I like to use a little tool called Net Stumbler. A great tool which shows you all the networks in proximity, their names, which channel they are on, their signal strength, whether or not they are secure and what type encryption they are using. Take it from me, it is a god send when troubleshooting wireless network issues.</p>
<p>http://www.softpedia.com/get/Network-Tools/Network-Monitoring/NetStumbler.shtml</p>
<!-- wpms-network-global-inserts -->]]></content:encoded>
			<wfw:commentRss>http://itknowledgeexchange.techtarget.com/it-rant/troubleshooting-wireless-networks/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
