<?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: &#8220;aquiring Network Address&#8221;</title>
	<atom:link href="http://www.wifisoftwares.com/answers/aquiring-network-address/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.wifisoftwares.com/answers/aquiring-network-address/</link>
	<description>Wireless software...and hardware tools</description>
	<lastBuildDate>Sat, 06 Mar 2010 12:49:49 +0100</lastBuildDate>
	
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: LeFirm</title>
		<link>http://www.wifisoftwares.com/answers/aquiring-network-address/comment-page-1/#comment-2391</link>
		<dc:creator>LeFirm</dc:creator>
		<pubDate>Sun, 04 Oct 2009 03:04:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.wifisoftwares.com/?p=914#comment-2391</guid>
		<description>I had the same exact problem.  The fix for me is that my router Dlink 625 has securoty mode WEP and WPA that my Dell 1390 wireless card simply could connect to.  Once I removed the security mode i.e set it to NONE the 1390 Dell wireless card was able to connect successfully.  Took me about 4 hours to figure that out.</description>
		<content:encoded><![CDATA[<p>I had the same exact problem.  The fix for me is that my router Dlink 625 has securoty mode WEP and WPA that my Dell 1390 wireless card simply could connect to.  Once I removed the security mode i.e set it to NONE the 1390 Dell wireless card was able to connect successfully.  Took me about 4 hours to figure that out.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: b</title>
		<link>http://www.wifisoftwares.com/answers/aquiring-network-address/comment-page-1/#comment-1739</link>
		<dc:creator>b</dc:creator>
		<pubDate>Thu, 17 Sep 2009 16:19:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.wifisoftwares.com/?p=914#comment-1739</guid>
		<description>Hopefully the ideas by the other people worked, if not you could try releasing and renewing your ip address. Here are the steps to doing this:
-Go to your start menu and choose &quot;run&quot;
-a black box will pop up, type &quot;cmd&quot; (no quotes) and press enter
-type &quot;ipconfig&quot; and press enter, this will display your current ip address
-next type &quot;ipconfig /release&quot; and press enter, this will release the ip address associated with your computer
-finally type &quot;ipconfig /renew&quot; and press enter, to obtain a new ip address
-then try connecting again, good luck!
Its odd that it would give you that message about the media being disconnected, that usually only comes up when you have a loose or bad wire. Try making sure all of the wires are properly connected to your laptop, router, modem, etc. Also are you using a wireless card or does your laptop come with wireless internet?</description>
		<content:encoded><![CDATA[<p>Hopefully the ideas by the other people worked, if not you could try releasing and renewing your ip address. Here are the steps to doing this:<br />
-Go to your start menu and choose &#8220;run&#8221;<br />
-a black box will pop up, type &#8220;cmd&#8221; (no quotes) and press enter<br />
-type &#8220;ipconfig&#8221; and press enter, this will display your current ip address<br />
-next type &#8220;ipconfig /release&#8221; and press enter, this will release the ip address associated with your computer<br />
-finally type &#8220;ipconfig /renew&#8221; and press enter, to obtain a new ip address<br />
-then try connecting again, good luck!<br />
Its odd that it would give you that message about the media being disconnected, that usually only comes up when you have a loose or bad wire. Try making sure all of the wires are properly connected to your laptop, router, modem, etc. Also are you using a wireless card or does your laptop come with wireless internet?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: NickofTy</title>
		<link>http://www.wifisoftwares.com/answers/aquiring-network-address/comment-page-1/#comment-1738</link>
		<dc:creator>NickofTy</dc:creator>
		<pubDate>Thu, 17 Sep 2009 15:38:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.wifisoftwares.com/?p=914#comment-1738</guid>
		<description>This is just a shot in the dark...
Do you have any/enough DHCP users specified?
I have 10 users (addresses) allowed on my Linksys.</description>
		<content:encoded><![CDATA[<p>This is just a shot in the dark&#8230;<br />
Do you have any/enough DHCP users specified?<br />
I have 10 users (addresses) allowed on my Linksys.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sarah</title>
		<link>http://www.wifisoftwares.com/answers/aquiring-network-address/comment-page-1/#comment-1737</link>
		<dc:creator>Sarah</dc:creator>
		<pubDate>Thu, 17 Sep 2009 15:11:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.wifisoftwares.com/?p=914#comment-1737</guid>
		<description>click on repair.... sometimes, it gets stuck on requiring ip adress but other than that, that should work</description>
		<content:encoded><![CDATA[<p>click on repair&#8230;. sometimes, it gets stuck on requiring ip adress but other than that, that should work</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: blazncac</title>
		<link>http://www.wifisoftwares.com/answers/aquiring-network-address/comment-page-1/#comment-1736</link>
		<dc:creator>blazncac</dc:creator>
		<pubDate>Thu, 17 Sep 2009 15:00:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.wifisoftwares.com/?p=914#comment-1736</guid>
		<description>Ok the most likely thing is your computer isn&#039;t detecting proxy settings so just go to IE and then click on tools then Internet Options then connections then LAN Settings and then check off Automatically Detect Settings  Hopefully this will fix your problem and make sure you entered the right WEP Key</description>
		<content:encoded><![CDATA[<p>Ok the most likely thing is your computer isn&#8217;t detecting proxy settings so just go to IE and then click on tools then Internet Options then connections then LAN Settings and then check off Automatically Detect Settings  Hopefully this will fix your problem and make sure you entered the right WEP Key</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SwimsALo</title>
		<link>http://www.wifisoftwares.com/answers/aquiring-network-address/comment-page-1/#comment-1735</link>
		<dc:creator>SwimsALo</dc:creator>
		<pubDate>Thu, 17 Sep 2009 14:56:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.wifisoftwares.com/?p=914#comment-1735</guid>
		<description>It&#039;s likely a couple of things:
1. You have the password (or encryption key) entered wrong. Make sure you have it exactly correct on your computer. If it is your own home network, make sure that you have distinguished between alpha-numeric and hex on your wireless router/AP if you are using WEP.
2.  You are using the wrong encryption. Make sure that if your router is WEP, your computer is using WEP and not WPA, and vice-versa. If you are using WPA, make sure you have it set for PSK (pre-shared key) and not enterprise key.
3. If it is on your home network, your wireless device (i.e. the linksys router or Apple Airport)  may have gotten &quot;stuck.&quot;    Unplug it and plug it back in.
Your wireless NIC still might connect to the wireless network at a physical level and show &quot;connected&quot; even if the encryption is not correct.    If you are at work and you are still not getting an IP address, it could be an issue with too many people being on that particular access point, or with the DHCP server (the thing that gives out IP addresses), or with the wireless controller (the thing that controls all the access points).  If you are at work, it&#039;s probably better for you to contact your IT group since they can evaluate the problem and know the setup better than anyone on Yahoo! answers will.
Also it makes sense that you would be able to get an IP address from the wired connection and not the wireless as typically companies put their wireless networks in different subnets than the wired ones.</description>
		<content:encoded><![CDATA[<p>It&#8217;s likely a couple of things:<br />
1. You have the password (or encryption key) entered wrong. Make sure you have it exactly correct on your computer. If it is your own home network, make sure that you have distinguished between alpha-numeric and hex on your wireless router/AP if you are using WEP.<br />
2.  You are using the wrong encryption. Make sure that if your router is WEP, your computer is using WEP and not WPA, and vice-versa. If you are using WPA, make sure you have it set for PSK (pre-shared key) and not enterprise key.<br />
3. If it is on your home network, your wireless device (i.e. the linksys router or Apple Airport)  may have gotten &#8220;stuck.&#8221;    Unplug it and plug it back in.<br />
Your wireless NIC still might connect to the wireless network at a physical level and show &#8220;connected&#8221; even if the encryption is not correct.    If you are at work and you are still not getting an IP address, it could be an issue with too many people being on that particular access point, or with the DHCP server (the thing that gives out IP addresses), or with the wireless controller (the thing that controls all the access points).  If you are at work, it&#8217;s probably better for you to contact your IT group since they can evaluate the problem and know the setup better than anyone on Yahoo! answers will.<br />
Also it makes sense that you would be able to get an IP address from the wired connection and not the wireless as typically companies put their wireless networks in different subnets than the wired ones.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
