<?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: Acquiring Network Address</title>
	<atom:link href="http://www.tdaxp.com/archive/2005/02/05/acquiring-network-address.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.tdaxp.com/archive/2005/02/05/acquiring-network-address.html</link>
	<description>All of us against the machine</description>
	<lastBuildDate>Fri, 19 Mar 2010 18:20:16 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: dhanudp</title>
		<link>http://www.tdaxp.com/archive/2005/02/05/acquiring-network-address.html/comment-page-6#comment-348029</link>
		<dc:creator>dhanudp</dc:creator>
		<pubDate>Thu, 04 Mar 2010 03:59:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.tdaxp.com/archive/2005/02/05/acquiring-network-address.html#comment-348029</guid>
		<description>startting the &quot;DHCP client&quot; service worked for me.
wallaaa........ thanks for the advices... :)</description>
		<content:encoded><![CDATA[<p>startting the &#8220;DHCP client&#8221; service worked for me.<br />
wallaaa&#8230;&#8230;.. thanks for the advices&#8230; <img src='http://www.tdaxp.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Gunden</title>
		<link>http://www.tdaxp.com/archive/2005/02/05/acquiring-network-address.html/comment-page-6#comment-345366</link>
		<dc:creator>James Gunden</dc:creator>
		<pubDate>Sun, 21 Feb 2010 05:43:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.tdaxp.com/archive/2005/02/05/acquiring-network-address.html#comment-345366</guid>
		<description>I suffered this problem too, tried many things in the site.  Had a good connection for a month with new wi-fi, then all at once got the dreaded message.  Solution for me, actually came from another board - From Rick at Techspot.com:
___
Sounds like your TCP/IP might be damaged in Windows.

To fix this, repairing your Winsock might work. You can do so by opening the command shell (Start &gt; Run &gt; cmd.exe) and type netsh winsock reset and restart your computer. This command only works in Windows XP with service pack 2 installed.

Alternatively, you can use a program such as WinsockXP http://www.snapfiles.com/get/winsockxpfix.html, which makes the process fool-proof.
___
I used the command, didn&#039;t download anything and it worked.  I also have XP with service pack 3.  Thanks to Rick (message was posted September of 2006) and good luck to all!</description>
		<content:encoded><![CDATA[<p>I suffered this problem too, tried many things in the site.  Had a good connection for a month with new wi-fi, then all at once got the dreaded message.  Solution for me, actually came from another board &#8211; From Rick at Techspot.com:<br />
___<br />
Sounds like your TCP/IP might be damaged in Windows.</p>
<p>To fix this, repairing your Winsock might work. You can do so by opening the command shell (Start &gt; Run &gt; cmd.exe) and type netsh winsock reset and restart your computer. This command only works in Windows XP with service pack 2 installed.</p>
<p>Alternatively, you can use a program such as WinsockXP <a href="http://www.snapfiles.com/get/winsockxpfix.html" rel="nofollow">http://www.snapfiles.com/get/winsockxpfix.html</a>, which makes the process fool-proof.<br />
___<br />
I used the command, didn&#8217;t download anything and it worked.  I also have XP with service pack 3.  Thanks to Rick (message was posted September of 2006) and good luck to all!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Liverbird</title>
		<link>http://www.tdaxp.com/archive/2005/02/05/acquiring-network-address.html/comment-page-6#comment-326983</link>
		<dc:creator>Liverbird</dc:creator>
		<pubDate>Tue, 17 Nov 2009 22:34:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.tdaxp.com/archive/2005/02/05/acquiring-network-address.html#comment-326983</guid>
		<description>Most of the time deleting the &quot;wireless profile&quot; and starting over will fix this issue, 
Article here shows how to delete wireless profiles in windows xp or vista:
http://mgmcc.forumotion.net/networking-tutorials-f17/removing-an-existing-wireless-profile-t109.htm

Other than that its likely DHCP is stopped/disabled and so should be started and set its startup type to Automatic.
To do that:
control panel/administrive tools/services/locate and click once on DHCP Client, use the panel on the left to start the service, double click the entry to change the startup type, save the changes made.</description>
		<content:encoded><![CDATA[<p>Most of the time deleting the &#8220;wireless profile&#8221; and starting over will fix this issue,<br />
Article here shows how to delete wireless profiles in windows xp or vista:<br />
<a href="http://mgmcc.forumotion.net/networking-tutorials-f17/removing-an-existing-wireless-profile-t109.htm" rel="nofollow">http://mgmcc.forumotion.net/networking-tutorials-f17/removing-an-existing-wireless-profile-t109.htm</a></p>
<p>Other than that its likely DHCP is stopped/disabled and so should be started and set its startup type to Automatic.<br />
To do that:<br />
control panel/administrive tools/services/locate and click once on DHCP Client, use the panel on the left to start the service, double click the entry to change the startup type, save the changes made.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: George</title>
		<link>http://www.tdaxp.com/archive/2005/02/05/acquiring-network-address.html/comment-page-6#comment-322853</link>
		<dc:creator>George</dc:creator>
		<pubDate>Fri, 30 Oct 2009 22:34:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.tdaxp.com/archive/2005/02/05/acquiring-network-address.html#comment-322853</guid>
		<description>Many thanks Chris (7th from top)
After weeks of trying other suggestions, I ran services.msc, wireless connections and found DHCp was disabled, I enabled it and set it to automatic and all was well. (I had previously set WAP password to 6 digits and 4 letters after an expert had told me that 8 digits was not enough even though my router said 8 to 64 characters) 
George</description>
		<content:encoded><![CDATA[<p>Many thanks Chris (7th from top)<br />
After weeks of trying other suggestions, I ran services.msc, wireless connections and found DHCp was disabled, I enabled it and set it to automatic and all was well. (I had previously set WAP password to 6 digits and 4 letters after an expert had told me that 8 digits was not enough even though my router said 8 to 64 characters)<br />
George</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: reinstall tcp-ip</title>
		<link>http://www.tdaxp.com/archive/2005/02/05/acquiring-network-address.html/comment-page-6#comment-315026</link>
		<dc:creator>reinstall tcp-ip</dc:creator>
		<pubDate>Tue, 29 Sep 2009 14:56:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.tdaxp.com/archive/2005/02/05/acquiring-network-address.html#comment-315026</guid>
		<description>Start-settings-network connections= double click network connections- click properties-click Microsoft TGP-IP-click install</description>
		<content:encoded><![CDATA[<p>Start-settings-network connections= double click network connections- click properties-click Microsoft TGP-IP-click install</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Big Homer</title>
		<link>http://www.tdaxp.com/archive/2005/02/05/acquiring-network-address.html/comment-page-6#comment-300621</link>
		<dc:creator>Big Homer</dc:creator>
		<pubDate>Fri, 14 Aug 2009 05:17:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.tdaxp.com/archive/2005/02/05/acquiring-network-address.html#comment-300621</guid>
		<description>To clarify: I changed the Wireless Router setting to TKIP</description>
		<content:encoded><![CDATA[<p>To clarify: I changed the Wireless Router setting to TKIP</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Big Homer</title>
		<link>http://www.tdaxp.com/archive/2005/02/05/acquiring-network-address.html/comment-page-6#comment-300620</link>
		<dc:creator>Big Homer</dc:creator>
		<pubDate>Fri, 14 Aug 2009 05:16:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.tdaxp.com/archive/2005/02/05/acquiring-network-address.html#comment-300620</guid>
		<description>I tried everything here to get a client&#039;s laptop to connect.  Had the same &#039;Acquiring Network Address&#039; message (0.0.0.0 IP).  

Solution was to change the WPA cipher type from AES to TKIP.  I guess the internal NIC is too old to use AES (have the latest driver) even though it is an option in the NIC settings.

DOH!</description>
		<content:encoded><![CDATA[<p>I tried everything here to get a client&#8217;s laptop to connect.  Had the same &#8216;Acquiring Network Address&#8217; message (0.0.0.0 IP).  </p>
<p>Solution was to change the WPA cipher type from AES to TKIP.  I guess the internal NIC is too old to use AES (have the latest driver) even though it is an option in the NIC settings.</p>
<p>DOH!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: paul griffiths</title>
		<link>http://www.tdaxp.com/archive/2005/02/05/acquiring-network-address.html/comment-page-6#comment-296074</link>
		<dc:creator>paul griffiths</dc:creator>
		<pubDate>Sun, 02 Aug 2009 11:22:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.tdaxp.com/archive/2005/02/05/acquiring-network-address.html#comment-296074</guid>
		<description>turning off tcp/ip has worked for me</description>
		<content:encoded><![CDATA[<p>turning off tcp/ip has worked for me</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Transman</title>
		<link>http://www.tdaxp.com/archive/2005/02/05/acquiring-network-address.html/comment-page-6#comment-289463</link>
		<dc:creator>Transman</dc:creator>
		<pubDate>Tue, 07 Jul 2009 04:04:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.tdaxp.com/archive/2005/02/05/acquiring-network-address.html#comment-289463</guid>
		<description>Martin&#039;s solution worked for me, I found the ASD services were not running. The links to Microsoft fixed the problem. I had to re-install hidden files from the XP disc. Thanks for the web links Martin!</description>
		<content:encoded><![CDATA[<p>Martin&#8217;s solution worked for me, I found the ASD services were not running. The links to Microsoft fixed the problem. I had to re-install hidden files from the XP disc. Thanks for the web links Martin!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mangal Mistry</title>
		<link>http://www.tdaxp.com/archive/2005/02/05/acquiring-network-address.html/comment-page-6#comment-286289</link>
		<dc:creator>Mangal Mistry</dc:creator>
		<pubDate>Thu, 25 Jun 2009 13:14:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.tdaxp.com/archive/2005/02/05/acquiring-network-address.html#comment-286289</guid>
		<description>My setup is Windows xp, Livebox - 57F8 supplied by Orange. I experienced the same problem as most people here. I had a Desktop &amp; a Acer Aspire Laptop. Desktop was permanently connected via Local Area Cable. Laptop, I used via Wireless connection. Everything worked fine for years. I never actually powered up or used the desktop for months - in fact I can&#039;t remember using it last. Everything was fine, until I dismantled and threw away the desktop. Just to check, I connected my laptop to the Livebox router via cable and all was fine for a whole day, but next day my Wireless Connection failed.  Came up with same error as most people here: “Acquiring network address”. Then that would fail. I tried all sorts of solutions suggested on this forum. With some it would connect for a minute or two then fail. Finally I resolved the problem in the following way: Do the following: 
1) Start, Connect To.., Show all connection, Right click on &quot;Local Area Connection, Properties, Advanced (tab). Here make sure th two boxes in &quot;Internet Connections Sharing&quot; are ticked. If not, ten tick them. Click on OK.

2) In a word document, type your WAP key. You can obtain this from you router configuration document - e.g.  4EBBD043AE1442BFCBA216FA14
(Don&#039;t worry - this is not my genuine WAP key)
Make sure it is all in CAPITALS and there are no gaps.

3) Again do this.
Start, Connect to, Show all connections.
This time right click on &quot;Wireless Network Connections&quot;, Properties, Wireles Networks (tab), Livebox - 57F8 (Automatic), Properties.
Now copy &amp; paste the WAP key from your word document, to here in &quot;Network Key&quot; and &quot;Confirm network key&quot; areas. Click on OK.

This worked for me. I hope it works for you too. Good luck.</description>
		<content:encoded><![CDATA[<p>My setup is Windows xp, Livebox &#8211; 57F8 supplied by Orange. I experienced the same problem as most people here. I had a Desktop &amp; a Acer Aspire Laptop. Desktop was permanently connected via Local Area Cable. Laptop, I used via Wireless connection. Everything worked fine for years. I never actually powered up or used the desktop for months &#8211; in fact I can&#8217;t remember using it last. Everything was fine, until I dismantled and threw away the desktop. Just to check, I connected my laptop to the Livebox router via cable and all was fine for a whole day, but next day my Wireless Connection failed.  Came up with same error as most people here: “Acquiring network address”. Then that would fail. I tried all sorts of solutions suggested on this forum. With some it would connect for a minute or two then fail. Finally I resolved the problem in the following way: Do the following:<br />
1) Start, Connect To.., Show all connection, Right click on &#8220;Local Area Connection, Properties, Advanced (tab). Here make sure th two boxes in &#8220;Internet Connections Sharing&#8221; are ticked. If not, ten tick them. Click on OK.</p>
<p>2) In a word document, type your WAP key. You can obtain this from you router configuration document &#8211; e.g.  4EBBD043AE1442BFCBA216FA14<br />
(Don&#8217;t worry &#8211; this is not my genuine WAP key)<br />
Make sure it is all in CAPITALS and there are no gaps.</p>
<p>3) Again do this.<br />
Start, Connect to, Show all connections.<br />
This time right click on &#8220;Wireless Network Connections&#8221;, Properties, Wireles Networks (tab), Livebox &#8211; 57F8 (Automatic), Properties.<br />
Now copy &amp; paste the WAP key from your word document, to here in &#8220;Network Key&#8221; and &#8220;Confirm network key&#8221; areas. Click on OK.</p>
<p>This worked for me. I hope it works for you too. Good luck.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->