<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Wireless Network Hammerin&#8217;</title>
	<atom:link href="http://www.meryl.net/2004/12/15/wireless-network-hammerin/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.meryl.net/2004/12/15/wireless-network-hammerin/</link>
	<description>Content on writing, tech, business, marketing, social media</description>
	<lastBuildDate>Tue, 07 Feb 2012 21:03:01 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Eric</title>
		<link>http://www.meryl.net/2004/12/15/wireless-network-hammerin/comment-page-1/#comment-1133</link>
		<dc:creator>Eric</dc:creator>
		<pubDate>Tue, 21 Dec 2004 01:50:45 +0000</pubDate>
		<guid isPermaLink="false">http://meryl.net/new/2004/12/15/wireless-network-hammerin/#comment-1133</guid>
		<description>&lt;p&gt;If WEP or WPA is used to secure WLAN, ensure all clients have the correct authentication key.&lt;/p&gt;

&lt;p&gt;If MAC filtering is used, ensure they are correctly added to the router\AP.  This can explain why 2 WLAN clients connect but a third cant.&lt;/p&gt;

&lt;p&gt;Ensure WLAN clients have latest firmware and drivers and that both support level of WEP, WPA or other authentication measures used to secure WLAN&lt;/p&gt;

&lt;p&gt;Try removing WEP\WPA\MAC filtering..can the clients connect?  Enable ESSID (network name) broadcast...do the Windows XP clients &quot;see&quot; or discover the WLAN?&lt;/p&gt;

&lt;p&gt;Although there are 11 channels in the US, technically there are only 3 non overlapping channels - Channels 1, 6 and 11.  Setting the AP to Channel 2 or 3 is similar to setting an old rotary dial TV inbetween two TV channels... may get some reception but normally just get more noise (snow on screen).  Channel 6 is the default by most OEMs and as such the most used.  Try Channel 1 or 11 and see if the interference or connectivy improves.  Use Netstumbler v4.0 from netstumbler.org to &quot;sniff&quot; Wireless networks in the area.  The report will tell you what WLANs are nearby, their signal strength, network name and channel used.  Note you may not see all networks - some may disable ESSID Broadcast - for these a commercial application like AirSnort, AirMagnet, AirDefense, AeroPeek are needed.&lt;/p&gt;

&lt;p&gt;There are still a ton of additional steps however this is a good start.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>If WEP or WPA is used to secure WLAN, ensure all clients have the correct authentication key.</p>
<p>If MAC filtering is used, ensure they are correctly added to the router\AP.  This can explain why 2 WLAN clients connect but a third cant.</p>
<p>Ensure WLAN clients have latest firmware and drivers and that both support level of WEP, WPA or other authentication measures used to secure WLAN</p>
<p>Try removing WEP\WPA\MAC filtering..can the clients connect?  Enable ESSID (network name) broadcast&#8230;do the Windows XP clients &#8220;see&#8221; or discover the WLAN?</p>
<p>Although there are 11 channels in the US, technically there are only 3 non overlapping channels &#8211; Channels 1, 6 and 11.  Setting the AP to Channel 2 or 3 is similar to setting an old rotary dial TV inbetween two TV channels&#8230; may get some reception but normally just get more noise (snow on screen).  Channel 6 is the default by most OEMs and as such the most used.  Try Channel 1 or 11 and see if the interference or connectivy improves.  Use Netstumbler v4.0 from netstumbler.org to &#8220;sniff&#8221; Wireless networks in the area.  The report will tell you what WLANs are nearby, their signal strength, network name and channel used.  Note you may not see all networks &#8211; some may disable ESSID Broadcast &#8211; for these a commercial application like AirSnort, AirMagnet, AirDefense, AeroPeek are needed.</p>
<p>There are still a ton of additional steps however this is a good start.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff</title>
		<link>http://www.meryl.net/2004/12/15/wireless-network-hammerin/comment-page-1/#comment-1132</link>
		<dc:creator>Jeff</dc:creator>
		<pubDate>Fri, 17 Dec 2004 22:57:21 +0000</pubDate>
		<guid isPermaLink="false">http://meryl.net/new/2004/12/15/wireless-network-hammerin/#comment-1132</guid>
		<description>&lt;p&gt;Checking the firmware version of the router.  It&#039;s one of the first items I check when either installing a new router for one of my client or working on one they&#039;ve already installed themselves.  Having copies of both the new firmware, and the version currently installed in the event it needs to be rolled back, frequently solves problems and enhances functionality.&lt;/p&gt;

&lt;p&gt;Checking the location of the router is another issue for readers to investigate.  Many times people place their computer and networking equipment into small physical spaces and it causes problems with items, especially those with reflective surfaces (CD&#039;s metal object, etc..) , come between the router and wireless adapter.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Checking the firmware version of the router.  It&#8217;s one of the first items I check when either installing a new router for one of my client or working on one they&#8217;ve already installed themselves.  Having copies of both the new firmware, and the version currently installed in the event it needs to be rolled back, frequently solves problems and enhances functionality.</p>
<p>Checking the location of the router is another issue for readers to investigate.  Many times people place their computer and networking equipment into small physical spaces and it causes problems with items, especially those with reflective surfaces (CD&#8217;s metal object, etc..) , come between the router and wireless adapter.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lockergnome's Mobile Lifestyle</title>
		<link>http://www.meryl.net/2004/12/15/wireless-network-hammerin/comment-page-1/#comment-1135</link>
		<dc:creator>Lockergnome's Mobile Lifestyle</dc:creator>
		<pubDate>Wed, 15 Dec 2004 18:51:13 +0000</pubDate>
		<guid isPermaLink="false">http://meryl.net/new/2004/12/15/wireless-network-hammerin/#comment-1135</guid>
		<description>&lt;p&gt;&lt;strong&gt;Wireless Networking Hammerin&#039;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The wireless network in my house went haywire. It worked on three PCs, one had a horrible connection, and one can&#039;t connect. Between Paul and me, we spent a lot of time researching and trying to figure out the problem....&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p><strong>Wireless Networking Hammerin&#8217;</strong></p>
<p>The wireless network in my house went haywire. It worked on three PCs, one had a horrible connection, and one can&#8217;t connect. Between Paul and me, we spent a lot of time researching and trying to figure out the problem&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lockergnome's Windows Fanatics</title>
		<link>http://www.meryl.net/2004/12/15/wireless-network-hammerin/comment-page-1/#comment-1134</link>
		<dc:creator>Lockergnome's Windows Fanatics</dc:creator>
		<pubDate>Wed, 15 Dec 2004 18:48:32 +0000</pubDate>
		<guid isPermaLink="false">http://meryl.net/new/2004/12/15/wireless-network-hammerin/#comment-1134</guid>
		<description>&lt;p&gt;&lt;strong&gt;Wireless Networking Hammerin&#039;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The wireless network in my house went haywire. It worked on three PCs, one had a horrible connection, and one can&#039;t connect. Between Paul and me, we spent a lot of time researching and trying to figure out the problem....&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p><strong>Wireless Networking Hammerin&#8217;</strong></p>
<p>The wireless network in my house went haywire. It worked on three PCs, one had a horrible connection, and one can&#8217;t connect. Between Paul and me, we spent a lot of time researching and trying to figure out the problem&#8230;.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

