Acquiring Network Address
by tdaxp ~ February 5th, 2005
My computer wouldn’t connect to the home network. It sees it just find, but hangs on “acquiring network address.” An hour of jiggering with various solutions, and nothing’s working. I reset the router, mess with the DHCP, restart miscellani, all to no effect.
Ultimately, in desperation I ran “Network Setup Wizard,” and it asked to restart. I clicked yes. Before it restarts it immediately connects to the network. This after an hour of work. All this for a machine that had previously been working on the same network weeks ago.
Windows XP is a very nice operating system, and Microsoft makes good products. As I tell my class, they make pretty good products that are pretty easy to use at a pretty good price. They are not the best in anything, but they are pretty good in everything.
But there’s still so far to go. Almost identical menus are strewn all across the Windows interface: some through control panels, some through the status bar, some through both, some through the help system.
February 26th, 2005 at 12:00 am
I had the same problem. Here's what I did: open up 'My Network Places' and find your network adapter (it's the one that is your Local Area Connection. Go to properties and disable your TCP/IP connection. Do not disable the TCP/IP Version 6 connection. There is apparently a conflict with the two; either that, or the registry commands for Version 6 differ from those for the normal TCP/IP. It's still somewhat of a mystery why this works - but it does. Let me know if this works for you.
March 1st, 2005 at 12:00 am
GT
Thanks for the tip! For me the solution was just re-running “Network Setup Wizard,” but maybe NSW did what you suggested behind-the-scenes.
July 1st, 2005 at 12:00 am
Disable TCP/IP? are you crazy…what kind of advise is that to give to the world, plz think before you say something like that.
The real answer is to set netbios to Enable NetBIOS over TCP/IP in het TCP/IP settings (advanced, wins tab).
Most people don't even have IPV6 installed in their windows…and i doubt cheap wifi ap's have it enabled by defaut.
July 3rd, 2005 at 12:00 am
Before giving advice, a few facts really should have been given. What were the AP's IP and netmask and what were the individual PC's IP, netmask and gateway? If you don't know that, you're very likely to guess wrong.
August 24th, 2005 at 12:00 am
I am having a similar problem.
My own username hangs on Acquiring network address and does not move past this stage; however the other two usernames on this computer can access the wireless network fine.
I am using XP Pro SP2 with a 3Com ADSL wireless router and 3Com USB wireless adapter in the PC
August 24th, 2005 at 12:00 am
I also have the same problem on with a completely different set-up (a Dell Inspiron 6000 with the UNL wireless network in my office). No luck on figuring out how to fix it, yet.
In my case other people were getting the same waiting-for-network error on other computers (macs, etc), so I don't know.
August 25th, 2005 at 12:00 am
TM Lutas is so right - give us more info!
Are you using a wireless AP? Did you configure WEP/WPA or some such?
Wired? Switch or hub? Speed set or autosense?
I can think of way too many reasons for this to happen - but that has also allowed me to live pretty comfortably for a number of years…
Kind of reminds me of calls from the help desk that start, 'the whole network is down…' (roll eyes - probably got someone who can't print because they are out of toner…)
August 25th, 2005 at 12:00 am
Stuart, TM,
Indeed.
The original purpose of this post was to save me some trouble, as before I posted it the top google results resulted in the same answer, but after 30 minutes of trying to piece together disparate messageboard comments.
I have no knowledge of UNL's “tsunami” network, but so many people experienced problems simultaneously (an actually small number for such a tall building — http://www.tdaxp.com/archive/2005/06/06/new_office.html) — because the offices are for humanities, not scientists) that I imagine it was something real.
Fortunately, my life in the dorm lounge (http://www.tdaxp.com/archive/2005/08/24/a-piechart-of-tdaxp-s-week-in-the-dorm.html, http://www.tdaxp.com/archive/2005/08/25/more-improbable-awesomeness-from-unl.html, etc), that I don't think about my office too much
August 25th, 2005 at 12:00 am
Just asking for basic context and info - there is too much information that is inferred. Is this accurate so far:
1) You are using a wireless access point in a college dorm which doesn't allow you to connect.
2) You are using Windows XP (sp2?) and using the built in Windows management utility.
3) You have never been able to connect (other than a short 'burst' during a setup procedure)
4) You have no instructions and are trying to 'wing it' (meaning that you are unaware of the University or Dorm procedures or config requirements)
5) It still doesn't work
Setting up wireless from your own home AP is easy and simple to troubleshoot. Connecting to an enterprise class system is a wholly different matter - issues can be non-broadcast SSID, EAP authentication and MAC tables.
August 25th, 2005 at 12:00 am
Seems like you are referring to the University's WLAN in your new office. My best advice is to log in to their network with your (new?) account from an already networked system and check out their FAQs for their IT department. It probably has a nice guide for connecting to their WLAN. (Alternatively ask at their bookstore.) [The rare 'burp' or a connect before completion sure sounds like an authentication attempt and rejection.]
August 26th, 2005 at 12:00 am
Wow — it is the blogosphere, when renowned computer experts spontaneously provide technical support!!
UNL's IS, like all university IS's, is striken by the fact that (a) most of its employees are undergrad students and (b) more of its customers are absent-minded professors. They have been less than helpful.
For now the lack of connectivity, and the fact that I need to steal someone else's ethernet cable to conect, has been keeping me from using my office as a place of work.
(Happily, the wireless works perfect in other places, so I am able to get a lot done in the lounge while with friends.)
For now, it's not serious enough to get emotionally involved with IT about. We'll see how it goes
Except for IS, though, UNL == awesome
August 26th, 2005 at 12:00 am
So you can get on their network in other areas?
In other sections of the tower?
If so, then you are probably simply in a dead spot - no good coverage.
To test this try connecting in other areas and then walking around while checking signal strength.
If you are using a wireless card then an option could be an external antenna.
September 11th, 2005 at 12:00 am
I had the same problem accessing my secured system with my wireless untill I decided to re-set the WPA-PSK
Network Key for both computers. I must have had an error in one of the entries because I have had no further problems with access since. Remember to set the Data Encryption to TKIP.
September 14th, 2005 at 12:00 am
dude…. acquiring network address is basicaly translated to an ip address 0.0.0.0, if a winxp does not have the sp2 it will just say invalid ip and the ip is 0.0.0.0 here is the procedure to correct this
click on start, run, services.msc
look for DHCP client…. if it sess acquiring network address that means that the dhcp client is DISABLED OR STOPTED… highlight the DHCP client and on the left side you will see “START” the service, click on it and then it will say “STOP, RESTART” then double click on the service and on the startup type select automatic, apply
THAT IS THAT!!!! this shit works…
by the way.. also chk the tcp/ip properties, make sure that we have all to automatic
September 16th, 2005 at 12:00 am
TavoLaco,
Thanks for the comment, and I hope it saves some of the people who find this page from google, but no luck for me
On my laptop it was running but still “acquiring network address” …. *sigh*
September 17th, 2005 at 12:00 am
on your laptop… do you use wireless connection or normal ethernet cable… also i forgot to mention to change the linkspeed and duplex on the advance properties of the network card or the wireless adapter, many times it works by selecting 10 half duplex i mean come on no isp has 10 mbps (i may wrong but…..)
also try to clone the MAC address if possible
let me know if it works, hope it does
TavoLoco Verizon online Tech support Level3
September 19th, 2005 at 12:00 am
TavoLoco,
In my office I can use the ethernet cable just fine. It is the wireless that gives me trouble.
In my dorm I can use both without a synch (but while both wireless networks connect to the time wired network, my dorm has a different wireless net than my office).
I am familiar with the concept of MAC cloning, but how do you wish me to do that? Clone my ethernet card's address to my wireless card?
Thanks!!
September 19th, 2005 at 12:00 am
Dan,
Cloning is used on access points and bridges to proxy MAC addresses - it won't apply to your situation.
On your laptop can you determine which SSIDs (wireless networks) are available? If there are some - do they show 'protected' (often a closed padlock appears)? You can't access a protected network without the proper credentials (WEP key or digital certificate or RADIUS account). From earlier notes it sounds like you either aren't in range (no signal) or don't have the credentials to complete a connection. I don't advise 'hacking' the AP since that might be considered illegal.
September 19th, 2005 at 12:00 am
Stuart,
The 'tsunami' network doesn't have credentials of its own (it hooks into the wider UNL network, but I can hook up to that through another wireless network just fine). The signal strength shows 'very good.'
For now I can use a cat5 cable in my office, so it's not a problem. If it gets annoying enough I'll just contact IT Services and badger people. Or say to Professor X that it's preventing me from doing Y, and get him to badger IT Services for me
September 20th, 2005 at 12:00 am
ok, if it's a wireless network and it's saying Acquiring network address… like the gentelmen Stuart Berman says, it's probably the SSID's or the WEP keys… but… are you using the software that came with the card to control the connection or letting windows configure the conection…. any way, if you want to do it the easy way just let windows control the connection if for some reason the “wireless connections” tab does not apear on the properties, go to start, run, services.msc and start the Windows Zero Configuration service…. also… some times the wireless channel may not be too compatible for example wireless B or G normaly they use channel 6, normaly i setup all wireless to channell 11 for better compatibility it there is a way to configure the channell maybe you can connect with the wireless and making sure that the WEP keys (if any) are both the same, and also try to configure the infrastructure to see if its an access point or an ad-hoc, because some wireless connections are pretty complex and they all have to do with the security the WEP/WPA keys the channell the SSID… etc etc… all those details if ther are configure properly the connections should work fine.. but any way i home this information is use full and also it helps to know the brand of the wireless adapter on the laptop because i'm very familiar with westell, linksys, belkin, dlink, trend and i may know a fiew things depending on the brand to make the connection work
TavoLoco L3 tech
September 20th, 2005 at 12:00 am
sorry for the spelling…. not bad for a guy living in mexico right?
September 22nd, 2005 at 12:00 am
TavoLoco,
Yes, your spelling and grammer are perfect — certainly better than mine!
Still no luck, but I think the problem here is pretty universal — no one seems to be able to connect to it. IT Services at universities seem to be universally incompetence and unconcerned. I'm not sure anything I do can make a difference when up aganinst that.
At least I have my cat5 cable…
September 23rd, 2005 at 12:00 am
damm…….if only i can be there so i can gather information about the wireless signal.. so i can find out to see it's infrastructure, ssid, wep/wpa keys, the signal strength, encryption methots, loopback frequencies… etc etc. because i have tools in my laptop (hacker tools you know….) so i cam be able to force some kind of connection but i always say that becaue i live in mexico and i cannot be where the REAL action is… here in verizon dsl tech support over 97% of the wireless connections are no match for me, the other 3% are eather very STUPID customers or the wireless adapter and/or router is not working at all or the customer is in a cave LOL!
and yes… there is a verizon tech support here in Tijuana mexico and level 3 techs can kiss my ass!!!!!
home there are other issues so i can share the knowledge….
September 25th, 2005 at 12:00 am
TavoLoco
LOL — good to hear that tech support is the same the whole world over!
Perhaps Aaron can ad his experience from the other side of the customer-ISP war?
Thank you very, very much for all of your time & effort. I appreciate it very much, and I am sorry that my limited skills prevented me from using your wisdom & exerience to their fullest. Thank you.
September 26th, 2005 at 12:00 am
Hi Guys, here is how I fixed my. My problem was my 2 desktops, and 2 laptops all do the “acquiring network address” crap… it works just weeks before but don't work no more. My 2 Desktops was on LAN to LinkSys Router, and the 2 lappies are on Wireless to the same router.
After hours of trying, I read what previous posting mentioned about DHCP stuff not working correctly, I looked into it, sure enough, some how, on my Router Configuration Page (where you setup the router) the IP of my router's DHCP server got changed. My router is located at 1**.1**.1.1 (IP Address) and DHCP was at 1**.1**.1.100, I changed the DHCP IP to what the router is located (1**.1**.1.1) and everything works like a charm now… =) Just for inspirations…
September 29th, 2005 at 12:00 am
hello… i'm back… according to linksys the default gate way ip is 192.168.1.1 (it's a free world, i put the ip address so what!!) for example… some routed modems (westell 2200, 6100) use the same gateway ip address, normaly if we connect a router to a modem and they are using the same gate way ip 192.168.1.1 it is recommended to change the ip eather from the modem or the router that way we can accesss both the modem and the router at the same time because some times if the gateway ip is the same the internet access is not working…. this does not happen with belkin of netgear because (for example) belkin uses 192.138.2.1 and netgear or dlink uses 192.168.0.1 but linksys uses 192.168.1.1 that is why with other routers it's easy but with linksys we have to change the gateway ip form .1.1 to .2.1 or .0.1 or any numer.1 and just for kiks my belkin router i change it to 1.1.1.1 and it still works because 192.168 those two numers are fcc regulated numbers something like that…. any way….. if we use a linksys with a routed modem we need to change the gateway ip so that the internet can work good
seeya soon with more tips
September 29th, 2005 at 12:00 am
oohhh by the way… please chk out my mini website i just started it yesterday….. it's not a fancy website with flast animations bull shit…it's a tech tips website with screen shots updated every day or weekly (whenever i got time), since i just start yesterday i only have 2 links but let me know or sugest any tips and information to put there so that my knowledge can be shared to the workd and hopely resolve many issues out there…. ok
http://geocities.com/tech_tips1
next time i'll put wireless bullshit tips too
September 30th, 2005 at 12:00 am
TacoLoco,
Nice site!!!
Everyone: visit TavoLoco's site at http://geocities.com/tech_tips1
TL, have you considered writing it in blog form? blogspirit (http://www.blogspirit.com) is free, has less annoying ads than geocities, and some neat community features available for free. “Live bookmarks” (RSS feeds) and other automatic features would also make it easier for everyone to keep updated on your newest tips and tricks
October 1st, 2005 at 12:00 am
i'm still working on my mini website……..
seeya soon!
October 2nd, 2005 at 12:00 am
This has already been posted before but I'd just like to mention it because it worked for me.
I was also stalling at “Acquiring Network Address” using a WEP key. I solved it by switching to WPA-PSK and setting a Pre-shared key on the router and adapater.
It seems like the WZC has problems with WEP keys, so if the router + adapter support WPA-PSK (Which is apparently more secure) go for it!
October 2nd, 2005 at 12:00 am
I am having a similar problem. I have recently purchased a Wireless PCI adapter for a Windows XP pc and my adapter cannot acquire a network address. I have tried manually inputing IP, subnet, mask, and default gateway but then it just didn't display anything, still getting a connection but when i opened firefox it wouldn't read anything. Any advice?
October 2nd, 2005 at 12:00 am
Usually, this points out a timeout issue with the wireless settings on the driver.
1. If you are at the point of actually “acquiring network address”, this really means the wireless transaction has happened.
a. Mac Address AUTH
b. Key exchanged
c. associated/forwarding
2. If you call someone who has access to the event logs on your wireless bridge/access point, they can ascertain if this is correct. In any event WINDOWS thinks so, and it is probably correct.
3. The PC or Notebook probably is using WZC (Windows Zero Configuration) for wireless. A number of Intel embedded wireless cards (Centrino chipsets) usually have outdated drivers, so go to your PC manufacturer and update the ones that came with your model. If you bought the wireless card separately, update the drivers from the wireless card manufacturer.
4. Especially IF you wireless card manufacturer has a wireless card management program, it is much better to use that than WZC. So if you have that, use it instead. Windows WILL NOT display multiple MAC ADDRESSES for antennas on a microcell WLAN, so Windows picks one. If multiple signals are close to you, WINDOWS will drift between the two. Your MFR's wireless management utility will resolve this.
5. If this is a notebook, go into the driver details through Device Manager
START>RUN>devmgmt.msc>[ENTER]
Expand network adapters, double-click your wireless card.
Click your advanced tab. Change any power related settings to MAX and not auto. UNCHECK auto on preamble length. Change it to LONG and try to connect, if not working change it to short (LONG should work). If there is a channel setting, leave it at AUTO.
If this were me, I'd uncheck all the auto settings (except channel) and leave them all at their highest levels, and I'd try to do this with the management (i.e. Intel Pro Wireless program if I have Centrino inside) instead of with Windows.
It sounds like a preamble length duration issue OR roaming stickiness. It's only an IP lease issue if everyone else is having the same problem. You are authenticating to the wireless array, which means your connection from the wireless array to the DHCP server is not communicating to your PC because of a timing issue brought on by a configuration in your driver settings. I've seen this a million times.
October 4th, 2005 at 12:00 am
yes….
we cannot manualy put the ip's on the tcp/ip properties because it will show a false connection, it will say connected but no luck at all
if we get aquiring network address it's basicaly an ip adderss of 0.0.0.0
i mentioned these steps earlier on this forum OR, since i recently updated my mini website there are the steps to try to correct the ip 0.0.0.0 or in your case aquiring network address
the site is http://geocities.com/tech_tips1
and select the first topic (only 3 for now)
and let me know if it worked for you ok
my mini website is updated dayly or when i got time
good luck
October 7th, 2005 at 12:00 am
You need to make sure the Service “Dhcp Client” is running, and make sure it is on Automatic startup, so when you boot, it will automatically start the service, giving you DHCP goodness.
Control Panel> Admin Tools> Comp. Management> Services
October 9th, 2005 at 12:00 am
the easyest way is Start, Run, services.msc, double click on DHCP client select startup type to automatic click apply then ok, that's it
October 12th, 2005 at 12:00 am
I have the same problem in my dorms. My powerbook g4, and my roomates powerbooks are able to connect to the network and internet, but my PC running Windows XP pro cannot.
At first the computer could connect to the internet, but one morning, I started it up, and it was “Acquiring newtwork Address”, with a statement of Invalid IP address and a 0.0.0.0 address and 0.0.0.0 subnet mask. I've tried going into the service.msc, but the DCHP was running and was already set on automatic. Even restarting it did not work.
The hardest part about this problem is that I cannot understand or find an explanation for my computer to start doing this all of a sudden. If anybody could provide more possible fixes that would be great.
October 12th, 2005 at 12:00 am
I am extremely, extremely happy for all the help I've received with my networking problem at UNL. Thank you. The interim solution: I stole a cat 5 cable.
October 13th, 2005 at 12:00 am
When this comment is listed in the comments bar to the right, it stops just short of the number 5. So it looks like your solution to network problems was to steal someone's pet.
October 14th, 2005 at 12:00 am
I have the same problem as Nick did. My dell laptop was able to connect to my home wireless network via Netgear 814 router before. All of a sudden one day, it kept aquiring network address and finally said limited or no connection. I reset the router and re-created the SSID, but it still did not work. It would work though if I left the wireless network unprotected (disable WEP encryption). Can someone tell me what to do? Thanks.
October 16th, 2005 at 12:00 am
Dan,
Amazing how much activity is on this thread.
Since you state that your office wireless LAN doesn't require credentials (no WEP, etc) and since you say you work elsewhere on campus then the problem is in the configuration on that particular access point (also others in the office vicinity are failing as well). It is probably an esoteric setting on the AP (anything from preamble length to enabled custom extensions used by manufacturers like Cisco which are incompatible with other cards).
Doclee - difficult to believe /something/ did not change. Perhaps an automatic firmware update to the access point (my AP is set to this). Or perhaps after you patched (auto update?) your laptop? One of the problems I often see with WEP keys is the use of incompatible configurations (such as ASCII vs Hex keys; WEP keys vs WPA-PSK passphrases; 64 bit vs 128 bit encryption; as well as enabling other attributes such as EAP and 802.1x authentication).
Some basic tips:
1) Check to see if there is a newer firmware update available for your Netgear AP.
2) Check with Dell to see if there is an update for the WLAN driver for your laptop and OS.
3) Check to see if you have updates for your OS (Windows XP SP2 has the only decent drivers for the latest WLAN features within the Microsoft family)
4) Are you using Windows to manage your WiFi connection - or are you using a third party application (technically called a WLAN supplicant)? With XP SP2 I find the Windows driver to be best. Years ago I would always use the custom application like Atheros, Cisco or Avaya client…
October 16th, 2005 at 12:00 am
Stuart,
Agreed! I am so happy that so many people have contributed!
I have to agree that it's something esoteric. I'm relatively competent at it (I have an MA in CompSci), and checked through the standard issues. Other people report the same or very similar problems, though Apples work without a problem.
I want to thank everyone for their help. Thank you. Please, feel free to offer ideas to people who might find this page and try to solve their own problems, but I think “esoteric” wraps it up for me.
Thanks again!!!!!!
Dan
October 19th, 2005 at 12:00 am
I'm having the same problem. I have a new laptop with the Atheros wireless adapter built in and using XP2. I'm also managing my connection with the Atheros Client Utility. I'm set up with a WPA Passphrase, Infrastructure, and Short & Long Preamble. I'm running a Belkin F5D 7230-4 router. I finally got the desktop and laptop seeing each other and sharing files. Several days ago I turned the laptop on after not running it for 1-1/2 weeks and I cannot get an IP address. The desktop is getting an address just fine. The laptop just says it's acquiring an address. It's getting excellent signal strength, but no IP address. Under service.msc the DCHP is running and set to automatic.
October 19th, 2005 at 12:00 am
I am having a similar problem.
Router was working fine, stopped working. I reset to factory, re-configured and my laptop waorks fine with wireless USB.
My desktop however doesn't. Just getting 'Acquiring Network Address' then Limited or No COnnectivity.
I have no WEP activated. Is this the DHCP problem?
October 23rd, 2005 at 12:00 am
oooops!! the site is http://geocities.com/tech_tips1/main.htm
October 23rd, 2005 at 12:00 am
hello there….. remember me?? guess not… any way since i started my mini website a lot of people are getting connected here is my mini website http://geocities.com/tech_tips/main.htm home it works for you, there are a few tips to correct the most common connection issues
home it works… good luck
October 28th, 2005 at 12:00 am
Hi, I just found this site… and I've tried all the suggestions with no luck. I'm REALLY stuck here!
I've got XP SP2 with all the updates.
I've tried both a USB DLink wifi dongle (DWL-G122) and a DLink PCMCIA card (DWL-650+) all with the latest drivers. Other people around here can connect to the wireless network but I can't…
DHCP is active…
The wireless network config settings mirror those of working PCs…
WZC is running… I've also tried the Dlink applications that came with the two wifi cards.
It continually shows “Aquiring IP address” with the current address of 0.0.0.0
It also appears to disconnect and then reconnect ever few seconds. When in the network connection page, having highlighted the adapter, the IP address comes up (0.0.0.0) along with the info on the site name and signal strength. A few seconds later (about 5-10) the details disapear and it states “not connected”. It then reconnects and away we go again. It acts this way on both network adapters.
The machine is a Panasonic Toughbook, PIII-800
The DHCP works, because when I plug into the hard-wired network it picks up and address and lets me spend hours online searching for solutions to this infuriating problem!
Any help would be greatly appreciated!!!!
Thanks
Darcy
October 31st, 2005 at 12:00 am
I'm also a member of the not-so-exclusive club of 'limited or no connectivity' with IP of 0.0.0.0. I have at home 2 laptops and two desktops. One laptop and one desktop (both wireless) connect fine to my Netgear ADSL wireless router and are instantly assigned addresses. The other laptop (wireless) and the other desktop (ethernet connected) refuse to acquire an IP address no matter what I try. All systems SP2, wireless security is WEP 64bit.
Is there any way to trace the DHCP conversation?
November 2nd, 2005 at 12:00 am
Hi there - I have found a fix to the problem and it is MAC Address filtering.
The router filters out any MAC addresses (Unique machine ID’s) that are not saved in a special list of “Allowed Machines”. This is really for use with large networks for security. You can disable MAC Address filtering in the router setup or if you HAVE to keep it - you can do “ipconfig /all” in DOS to see your machines unique Mac address and then add it to the list of allowed users.
Disabling this has fixed my problems and enabled my machines to “Acquire Network Addresses!” Hope this helps someone else!
November 8th, 2005 at 12:00 am
Nevermind. I figured out the answer to my own question: http://www-jerry.oit.duke.edu/pc/xp_dhcp_client_wont_start.html
November 8th, 2005 at 12:00 am
Tavoloco: What if I try starting the DHCP client, but get an error, indicating all the dependencies are not available? Any ideas?
I'm having a problem “aquiring network address” too, and all the other suggestions have failed. If I can get my DHCP client working, that may solve my problems.
Thanks!
November 12th, 2005 at 12:00 am
goto administrative Tools>Services then make sure your DHCP client is running!!
November 12th, 2005 at 12:00 am
My final solution ended up being childish: registering my connection against with UNL. I'd done it already, and because of that I was able to connect to the internet wireless at one location — but for some reason the second time enabled it campus-wide.
I want to thank everyone for this thread, and I hope it keeps going. A lot of people find this page looking for help — let's keep this page as useful as possible for all those who need the help!
November 12th, 2005 at 12:00 am
Hi,
I am back. I posted on Oct. 14 regarding “aquiring network address” problem with my laptop: it worked for a few weeks, then all of a sudden, no matter how hard I tried, it just did not work anymore. Finally, I figured out what my problem was (not sure if it applies to your case). I think what happened was that one day, my connection dropped, then I tried to sign it again, but unfortunately, with a wrong security key, and acidentally, I let the laptop to remember this wrong key. I reset the router and generated a new key, this time, I mistook the “Passphrase” for the key. Later, I realized that the passphrase was just a hint and the real key was what the setup page generated based on the passphrase. I therefore enter the correct key, and bingo, everything worked.
doclee
November 12th, 2005 at 12:00 am
Another Possible Solution
I finally got the Acquiring Network Address to go away and get connected. I tried most of the solutions in the above posts. Including, enabling Netbios over TCP/IP, changing power settings and preamble settings, made sure DHCP Client was set to Auto in services.msc, made sure MAC filtering was disabled, ran the Wireless Wizard (this step, you will find out, took away hours of my short life), made sure I didn’t have any Norton DeathWare, but it was just not able to acquire a network address. I restarted the router (Linksys WRT54G), restarted the computer, restarted my wireless card (Atheros AR5004G), restarted the cable modem but no luck. I updated my router firmware. There were no driver updates for my wireless card.
This is strictly a Windows XP problem from what people have contributed in this forum. The Apple PowerBooks don't have this problem. My Tivo which runs Linux didn't have a problem connecting to the router. (I am using WEP just because Tivo only supports WEP and not WPA. I was able to CONNECT though WPA). Despite trying all the technical adjustments from the suggestions contributed from others, I persisted by doing a combination no brainer things thinking there was probably a quirk in Windows. I'm not sure if all the things I did were even part of the solution but I will give all the details.
1. Powered off the router for 20 seconds.
2. Ran Wireless Network Setup Wizard on my laptop
Chose Add new computers to my SSID network
Chose Setup Network Manually
Chose Print Settings
When a Notepad file opened, it gave me the network settings with some obscure WEP key that was not mine. I copied the WEP key.
3. Tried double clicking on my SSID in Choose My Network and pasted the obscure WEP key I copied. Well, obviously it didn't work because this is not the WEP key I entered into the router.
4. So then, I had to retype my own WEP key back in with the confirmation and then I tried reconnecting and then it CONNECTED in like 5 seconds.
5. Subsequently, I tried using the “Wizard” again, without copying and pasting the obscure WEP key, and I tried connecting into my SSID and got the Acquiring Network Address CRAP again. Again, I retyped in my own WEP key and it connected without a problem.
6. This leads me to conclude the “Wizard” is changing the WEP key and screwing us over and wasting hours and days of our time because people at Microsoft are lame. Have you ever heard Bill Gates speak without using the word “innovate”? He hasn’t innovated anything. He’s only strong armed great companies with his lawyers, stole technologies, destroyed any innovative companies and bought the good ones. What a jackass. Apple - now that's a company that innovates.
7. Of course, your setup is different than mine and there may be some other quirk that Windows has “installed” for you. Good luck.
November 15th, 2005 at 12:00 am
I tried “dyna's” advice here:
Friday, July 1, 2005
“The real answer is to set netbios to Enable NetBIOS over TCP/IP in het TCP/IP settings (advanced, wins tab).
Most people don't even have IPV6 installed in their windows…and i doubt cheap wifi ap's have it enabled by defaut.”
It worked for me…
I hope you get your running soon.
jp
November 21st, 2005 at 12:00 am
i had the same problem with my hp laptop aquiring network address over wireless by a linksys, found that windows firewall started itself, and since i am running trend securtiy sweet i disabled windows firewall again and it found the address imediately.
November 26th, 2005 at 12:00 am
Hi guys- I've been having the same problems with my laptop ever since I switched over to satellite internet ( I moved to an area with no other alternatives). Prior to this, with cable, I have never experienced this 'acquiring network connection' problem. I am wondering if this isp change has anything to do with it since my network settings haven't changed other than connecting to a different modem. Also, the problem seems to occur erratically- sometimes from the moment of boot-up or else later in the day. Also, the signal strength from the satellite is all over the board - running speed tests one right after the other will give me dramatically diferent readings. My complaints to Direcway fall on deaf ears. I have also been able to get the problem to go away by rebooting my router and/ or the modem- I guess I am confused as to whether the problem lies with my router or their modem. I am no expert- if what I have read here makes sense to me- it sounds like the problem is with my equipment. Could one of you pros let me know if my conclusion is correct or could it be caused by Direcway's equipment?I have instituted the fixes sugested here and hopefully these will help. Also, TavoLoco- is your site still up? I am unable to reach it by the posted URL and would love to read what tips you have there. Thanks for any help you can give me.
November 26th, 2005 at 12:00 am
Just a footnote to my last post- after rebooting my laptop today with the new settings (having left it off for about 4 hours)- I was back to the same old connection problem. After messing around with the settings and stuff, I found the only solution was to reboot my router and then suddenly it was working again. Also, I forgot to mention that my wife's laptop (which is wireless too but not running sp2 which I am) failed to get a connection also until I rebooted the router. Could this be a symptom of a failing router or could it be locking up from some input from the satellite modem? Other than buying a new router I don't know how to take this to the next level. Help!!!
November 27th, 2005 at 12:00 am
I had the exact problem on my Belkin wireless Pre-N router.
No problems for months but then suddenly would not log in
even though signal strenth was excellent. “aquiring network address” would not go away.
My solution: just downloaded a FIRMWARE update for the router and everything works fine now.
December 2nd, 2005 at 12:00 am
Acquiring network address is basicaly translated to an ip address 0.0.0.0, here is the procedure to correct this:
click on start, run, enter 'services.msc'
look for DHCP client….
if it says acquiring network address that means that the dhcp client is DISABLED OR STOPTED… highlight the DHCP client and on the left side you will see “START” the service, click on it and then it will say “STOP, RESTART” then double click on the service and on the startup type select automatic, apply
Symptom
DHCP Client Service may not start automatically. When you attempt to start the Service manually, the following error may be displayed:
Error: Could not start the DHCP Client Service on local computer
Error 1068: The dependency service or group failed to start.
Resolution
The DHCP Client Service in Windows XP, depends on these three components:
* AFD
* NetBios over Tcpip
* TCP/IP Protocol Driver
If one of the above drivers fail to start, then the DHCP Client Service may not start.
Step I - Make sure that the three driver files are present
Open Windows Explorer and navigate to %Windir%System32Drivers folder. Make sure that the following files are present in the folder:
* afd.sys
* tcpip.sys
* netbt.sys
If one or more of the above driver files are missing, extract them from the Windows XP CD-ROM or from the ServicePackFilesi386 folder, whichever is the latest version.
Step II - Verify the number of Dependencies
From other sources in the Web, I've found that some versions of Norton Antivirus (NAV) adds an entry to the DHCP Service Dependencies, and removing NAV does not remove the appropriate value from the DHCP Dependencies.
To quickly determine the Dependency services for DHCP Client Service, type the following command in Start, Run dialog:
CMD /K SC QC DHCP
Verify the output. It should be exactly as below:
[SC] GetServiceConfig SUCCESS
SERVICE_NAME: dhcp
TYPE : 20 WIN32_SHARE_PROCESS
START_TYPE : 2 AUTO_START
ERROR_CONTROL : 1 NORMAL
BINARY_PATH_NAME : C:WINDOWSsystem32svchost.exe -k netsvcs
LOAD_ORDER_GROUP : TDI
TAG : 0
DISPLAY_NAME : DHCP Client
DEPENDENCIES : Tcpip
: Afd
: NetBT
SERVICE_START_NAME : LocalSystem
If additional entries are listed under DEPENDENCIES…
If any other additional drivers or Services are mentioned in the DEPENDENCIES section, you need to remove them via the registry. Follow these steps:
* Click Start, Run and type Regedit.exe
* Navigate to the following branch:
* Backup the branch to a REG file
HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Services Dhcp
* Double-click DependOnService MULTI_SZ value and set it's data as follows:
Tcpip
Afd
NetBT
* Close Regedit.exe
Step III - Verify that the Dependency Service / components are running
Next step is to verify that the three dependency components are running. As the three components are actually the Kernel Drivers (Driver Service), you need to manage then via the Device Manager. Follow these steps:
* Click Start, Run and type DEVMGMT.MSC
* In the View menu, click Show hidden devices
* Double-click Non-Plug and Play drivers section
* Double-click the entry -
AFD Networking Support Environment, and
click the Driver tab
* Set the Startup type to System.
* Start the service. Note down the error message if any.
* Similarly start the two other drivers namely:
* TCP/IP Protocol Driver
* NetBios over Tcpip
* Close Device Manager and restart Windows.
December 5th, 2005 at 12:00 am
I have a domain and i want to add a pc with XP sp2. I´ve to put this pc to automaticaly recieve ip from server. So saw this message : “acquiring network address”. I want to disable this, to receive ip from server.
December 11th, 2005 at 12:00 am
I finally resolved the 'aquiring network address issue.' This was an issue with the TCP settings holding onto an incorrect router IP. I resolved my issue by hard coding my IP settings. Wha La…
I tried setting netbios over TCPIP but that didn't work.
Does anyone know how I can get dhcp to work properly?
December 16th, 2005 at 12:00 am
I just had this 'acquiring network address' problem for a couple of hours with the Atheros Client Utility.
I eventually solved it simply by re-entering the WPA passphrase in the Atheros profile configuration, even though it still showed a passphrase in there (and the only passphrase I ever put in there was the correct one).
December 19th, 2005 at 12:00 am
“The real answer is to set netbios to Enable NetBIOS over TCP/IP in het TCP/IP settings (advanced, wins tab).
Got it to work with this workaround at work
Will test it tonight at home
December 20th, 2005 at 12:00 am
Just another guy that surfed into here through Google. I wanted to say thanks to everyone that helped. TavoLoco's solution of running services.msc and setting DHCP client to “automatic” worked for me. I have no ideal how it got disabled in the first place, but this isn't my computer. So for those of you who are not on a wireless network and are stuck on “acquiring network address” this might be your first thing to try.
December 27th, 2005 at 12:00 am
A big thanks to this forum for helping me resolve my “acquiring” issue. ran the services.msc, clicked as above and everything is working GREAT! Thanks again everyone!
January 7th, 2006 at 12:00 am
I was having the same problem with the “acquiring network address” message. I finally realize I was using the wrong password for the router. Double check that, just a suggestion.
January 11th, 2006 at 12:00 am
What a great thread….find it quickly will hopefully save me weeks of mind-numbing google-clicking. Hope it works. Our problem is a bit different in that the desktop machine doesn't work wirelessly OR via CAT5 - just that well-documented “acquiring network address” message. I'm going to start running through these items and see if anything works.
January 16th, 2006 at 12:00 am
OMG! 3 1/2 hours on the phone with linksys to no resolution. 3 secs on this page and dyna's solution worked THANK YOU!@#!@# ENABLE NETBIOS OVER TCP/IP! THANK U !@#!@#!@#!@#!@#
January 27th, 2006 at 12:00 am
Paul, Many thanks! My afd.sys file had a size of 0KB instead of 136KB. I copied the file from another computer and I am now back online.
January 28th, 2006 at 12:00 am
i got the acquiring network adress problem solved by enabling NetBios in wireless connection (on my pc and laptop) and most importantly on my adsl connection
with that solved, having pc and laptop wirelessly connected i now face another problem, both are invisible to each other in my network places and sharing adsl connection doesnt work (i cant surf over the internet on my laptop)
so whats the point of having them wirelessly connected if i cant do anything… blody windowsxp..
i have windows xp sp2 (on pc and laptop), i use ratlink utility to connect my 2 asus wl-167g usb adapters in ad-hoc (tried using asus utility and windows own drivers but no go).
P.S.
stumbled on this thread using google
January 29th, 2006 at 12:00 am
Regarding the enabling of DCHP, This actually sorted my own wifi problem out, Thanks to Tweak XP messing it up, Thanks TavoLoco, good to see someone knows how to use windows ;D
February 18th, 2006 at 12:00 am
Interesting article:
I had similar problem with Linksys G Wirless Router and spent more than a day for this frustrating issue that “acquiring network address”. .. Every thing was working normally and all of sudden it stopped.. My problem was wrong password (key) make sure you guys use the correct network name (SSID) and password… I changed my channel to 11 from 6, it is working although I am not sure it is good or bad..
February 22nd, 2006 at 12:00 am
==========================
“dude…. acquiring network address is basicaly translated to an ip address 0.0.0.0, if a winxp does not have the sp2 it will just say invalid ip and the ip is 0.0.0.0 here is the procedure to correct this
click on start, run, services.msc
look for DHCP client…. if it sess acquiring network address that means that the dhcp client is DISABLED OR STOPTED… highlight the DHCP client and on the left side you will see “START” the service, click on it and then it will say “STOP, RESTART” then double click on the service and on the startup type select automatic, apply
THAT IS THAT!!!! this shit works…
by the way.. also chk the tcp/ip properties, make sure that we have all to automatic”
=============================
THAT WORKED PERFECTLY FOR ME!!!!!
February 22nd, 2006 at 12:00 am
I am having a similar problem just like everyone else here. I have a brand new Toshiba Satellite laptop. I can connect if it is wired but if I go wireless I just get “aquiring address”. My signal is great, I have double checked my pwd key. I changed some settings in tcp/ip, advanced, wins, enable netbios over tcp/ip. The dhcp services are running correctly. I even have 2 other laptops on the network running wirelessly and they are working just fine. All of the laptops are WinXP SP2. I also noticed that my speed is bouncing around from 11mbps to 54 mbps. I really need some help, I been googling up info all day on this and have probly wasted 10 hours on this POS. Any ideas?
Thanks
February 27th, 2006 at 12:00 am
I had a similar issue with a new Linksys Router (WRT 54GS) and a new toshiba Laptop. After reading the comments here I upgraded my Router firmware from ver 2.07 to ver 4.70.6 many new features and security improvements. Selected WPA personal on router and WPA TKIP on Laptop. Entered key and all problems solved. I used a non standard address and shut off brodcast of the ssid. It immediatly connected and acquired an IP address. Also now has greatly improved overall preformance
Hope this helps someone
February 28th, 2006 at 12:00 am
I fixed my problem, I changed the router back to the basic settings so that there was no security or password key. I then deleted the wireless settings that my laptop had tryiied connecting to. Then I was able to connect without any problems once this was done. But this is not a safe way to network with other computers so I then recreated the security settings on the router to wpa-psk and created a password 15 characters long. I then was able to connect to my wireless network. Don't know why this worked but it did.
March 3rd, 2006 at 12:00 am
I have a Belkin Pre-N router and have a Belkin Pre-N card in my desktop and have had this issue for months although the Intel card in my laptop connects instantly.
Finally fixed the problem by changing the channel in the router, now the Pre-N card connects instantly just like the laptop.
March 6th, 2006 at 12:00 am
I've gone through all of these suggestions to no avail.
My situation is weird. I live in a hotel during the week on the job, and they proved free wireless internet. They have like 8 connections depending on what part of the hotel you are on. I have been able to access it with no problem, then all of a sudden, it stopped working. At work, my laptop connects no problem, but when I get to the hotel, all I get is acqurining network address. What is weird is that I have been able to connect for the past few weeks NO problem to whatever signal happened to be strongest.
What can I do??
TIA!
March 16th, 2006 at 12:00 am
Similar problem with Dlink WAP. It worked for a couple weeks then quit with 2 laptops. What I discovered was when they connected and were stuck in acquiring mode if I went into the “View Available Wireless Networks” and did a disconnect/reconnect they went right in without a problem. That is not a good way to fix the problem on a daily basis but it does allow a fix short term till I can figure out the problem.
March 20th, 2006 at 12:00 am
'acquiring network address' problem: first, turn off windows firewall. disable or exit out of any anti-virus app. click on wireless icon. view wireless network. is your network appearing? highlight and disconnect. do u now have option to connect? if so, connect. if not, turn wireless switch on laptop to off. then to on. should see option to 'connect.' hit 'connect.' type in network key twice. it searches for available networks and then connects to your home network. use internet connection, or (advised), turn back on windows firewall and open anti-virus app, then use net. though before using net, i prefer to reboot. wireless connection should come right back on.
March 20th, 2006 at 12:00 am
Also, one thing to keep in mind, is that when this fails, a lot of times it simply means that the network failed to assign an IP address to your computer. This can be because your MAC address has been put on a filter list. In public domains, this can be caused by using up too much bandwidth. So always check the network by making sure your MAC address is not on a block filter, or if needed, is on the accepted MAC address list.
THis has caused problems for me in the past.
March 20th, 2006 at 12:00 am
Glad I ran into this blog but unfortunately nothing seemed to solve my problem. I have an intel pro 2200BG network card and was connecting to a comtrend +536 router with Windows XP SP2. Was having trouble connecting for some time until it occurred to me to change the channel of the router. It was on 11 and I changed it to 6. From then on everything ran fine. Then I decided to secure my network to prevent others from getting it. I setup the router to use WPA-PSK but had trouble connecting from my laptop. Windows XP would try to connect for 2 minutes or so and then eventually say it was connected with limited or no connectivity. I didn't get an ip address from the router or anything and I couldn't browse the web. Every now and then after trying to connect it wpud connect and then start working from then on however if I restarted my computer it would go back to having trouble again. I tried the various things that people listed here and I even downloaded and installed the Intel ProSet/Wireless tools from intel but nothing worked. So it dawned on me that since my earlier problem was solved by changing the channel that maybe I could try that again. So I changed the channel from 6 to 1 this time and guess what.. worked like a charm. Restarted my computer several times to make sure it worked and it still does. I can connect and my network is secured. Figured I'd make a note for others out there who might run into the same problem. Sure is a pain in the ass when this stuff goes awry and just doesn't work. Good luck!
March 26th, 2006 at 12:00 am
Hi there, I have a wireless network, but not good access for downstairs, so I got an access point.
My two laptops can locate the access point, but when trying to acquire access to network, it can't.
I don't know why this is happening and help is very much required at this stage.
Thanks
March 27th, 2006 at 12:00 am
I had the exact same problems…I ran the wireless network wizard, and fixed.
March 28th, 2006 at 12:00 am
Hi all. I upgraded the firmware on my D-Link DI-524 to 3.20. I then added WPA2 support to my Windows XP Home Edition Laptop, which was running SP2. After that, when I try to connect via either WPA/WPA-PSK/WPA2/WPA-PSK (both TKIP and AES) the connection sequence seems to halt at the “Acquiring network address” stage.
What's weird is that I've found a way around it. I can plug into my Ethernet port and connect that way. At which point the wireless card does acquire the address. Note that each card has its own address. Once it's working this way I can unplug from my Ethernet and just use the wireless.
Still, this is only a workaround and I don't know why the problem is occurring. I used to use WPA-PSK fine until I upgraded the firmware and added WPA2 support. If anyone has any ideas I'd appreciate it.
Thanks.
March 30th, 2006 at 12:00 am
It's not just a WinXP problem. My home network is Win98, one machine with an ethernet connection and one with a Belkin wireless USB adapter. Router is Addon GWAR3000. Everything worked perfectly up to 2 weeks ago, with WPA-PSK security and MAC address list filtering. Then the WLAN stopped working; the wireless-connected machine had somehow got the wrong IP address and was unable to collect a new one by DHCP. Ultimately I found that turning off encryption allowed me to get and IP address and get back online. However if I try to put WPA back on, it won't work - can't log in. Bizarrely, I can however continue using it with WEP encryption switched on.
I suspect some setting in the router has been changed (by an incoming cosmic ray, perhaps) but I am damned if I know what.
March 30th, 2006 at 12:00 am
I've had this problem for a few days now. I had a laptop working perfectly and then one day it just stopped working after I moved the modem into another room. The laptop is connected to a Wireless-G Linksys and it keeps saying “Aquiring network address”. Any help?
March 30th, 2006 at 12:00 am
I had the same symptom and spent over 2 hours trying everything that seemed reasonable. Using the Network Setup Wizard fixed it in a flash. BTW, I had just this week gotten a Comcast Cable Internet connection (after some “issues” with THAT installation). And my very able wife today tried to set up the wireless router I'd gotten with a Toshiba laptop. Awful frustrating for both of us to not have it work (esp after having had ZERO problem “borrowing” a nextdoor neighbor's wireless connection since Christmas!). Anyway, using our connected desktop to Google the phrase “acquiring network address” got me to this blog — and your marvelously simple and direct advice. Thank you, thank you, thank you!
March 30th, 2006 at 12:00 am
I want to thank everyone for making the tdaxp blog part of a community help program. Thank you.
Kurt, that's how I'm connected right now.
I have broadband access, but for moving my laptop about you can't beat wireless. I remember the first day I held a functioning laptop — I even remember the first day I used telnet. Computer network technology is a marvelous — and increasingly human — thing.
April 3rd, 2006 at 12:00 am
I've have a PC running XP connected (ethernet) to a D-link ADSL modem/router, and the Asus motherboard came with a wifi card. I then recently purchased a notebook with wireless built-in… so I thought, rather than replace the current modem/router, which is working fine, with a wireless version, I'd set up the PC's wireless connection in “soft ap mode” and bridge the ethernet/wireless connections to allow the notebook internet access.
All was fine until recently got the “acquiring network address” problem, which brought me here. After lots of pulling hair out though, I believe I've got it fixed… “IP Broadcast” packets were being filtered in the router's “Layer 2 Filtering” options. Allowing these through seems to have fixed the problem - makes sense I suppose since this is how DHCP communicates?
Anyway, thought I'd post this in case it's useful & helps resolves others' problems, as I know how frustrating this little problem is!
April 4th, 2006 at 12:00 am
I have a new HP Notebook that I'd like to use at work. When I try to find the internet it asks me to make sure my wireless switch is on. How do I find the wireless switch. I've looked everywhere that I know about? Thanks in advance. Snoozin
April 10th, 2006 at 12:00 am
I am having the same problem with my Acer centrino laptop. It accesses the network, but displays “acquiring network address”.
Now, I have two desktops and a printer wired to the router which is setup as DHCP. They have no problems getting an address. It's only the wireless notebook which has the problem.
I have another notebook which has no problem getting an address assigned to it, but it's using a wifi card and its own access software istead of WZC.
My solution was to assign an ip address manually, but that's the easy way out.
April 12th, 2006 at 12:00 am
If you have a WAG54GS Linksys ADSL modem router Access Point, then I suggest you push the RESET (with a unbent paper clip) located behind the unit , holding it down for five seconds. This resets the WAG54GS to factory defaults and you will have to re-enter all your ADSL user id and password data again, as you did when you first setup the WAG54GS, but it will sort out the DHCP acquiring network address problem.
I realised my laptop DHCP client was fine when it immediately acquired another previously functional access point in a separate location.
Good luck
April 13th, 2006 at 12:00 am
This is my setup and problem.
I have a Dell XPS M140 laptop with the Intel Proset 2200BG, Linksys WRT54G. I have WPA2 enabled and Mac address filtering. I only have the “B” portion enabled seeing as on a home connection even cable you would be lucky to get 4-6 mbps download even though it says it is connected at 11 mbps. Anyway there have been multiple times even though it says I am connected the connectivity is lost. Proset is managing the wireless card, I have read that the Intel 2200BG has problems. I have yet to see if I have the updated driver, does anyone have any suggestions as to what I can do to make sure the connection isnt lost and maybe speed up the connection. After running multiple speed tests at testmy.net it states I am only connecting at about 56% of ISP's norm. Will disabling PSP on wireless card fix these issues? I dont have the time to spend on properly troubleshooting the issue since I already work 12-14 hrs a day. I have spent a few hrs already trying to resolve this, any professional advice would be helpful. I have the current driver for AP and I can connect it just drops and I am not getting my full speed. Thank you in advance.
April 13th, 2006 at 12:00 am
Savino said:
“I am having the same problem with my Acer centrino laptop. It accesses the network, but displays “acquiring network address”. Now, I have two desktops and a printer wired to the router which is setup as DHCP. They have no problems getting an address. It's only the wireless notebook which has the problem. I have another notebook which has no problem getting an address assigned to it, but it's using a wifi card and its own access software istead of WZC. My solution was to assign an ip address manually, but that's the easy way out.”
Actually it's not easy for me. If I assign a fixed IP address to my (Belkin) wireless adapter, it can connect to the (Addon) router but the router won't let it connect to the Internet.
April 16th, 2006 at 12:00 am
Hi,
I have an intel proset wireless 2200BG installed on my dell inspiron 6000.
i also have a linksys wrt54g router beside me.
my problem is not like the usual ones i've read here.
initially i had no problems, signal is good, and the rate is relatively stable/constant. but when i shut my computer and rebooted, i can no longer detect the wireless network or any other wireless networks for that matter. i thought there was a glitch with the router but the thing is, my brother and mom are both able to see and connect through it.
after reading through a lot of post, (and after a lot of installing and uninstalling the driver) i still can't get through. i tried managing it both from microsoft client or from intel proset, but still with no luck. Till i read somewhere that i have to restart my wireless zero configuration service. True enough, after 1 whole week without conection, i was able to see the network again (and signal i get is still good). Unfortunately, the same incident happened, when i closed my laptop and rebooted the next day, i can no longer see the wireless network (lest connect to it). It only says “no wireless networks were found in range”. To think that the router is right beside my laptop. i tried all the suggestions here but still to no avail…
hope someone can enlighten me…
thanks.
btw: my laptop's running on winxp pro with sp2.
April 26th, 2006 at 12:00 am
My Dell Inspirion6000 Laptop is experiencing the Acquiring Network Adress issue. Its IP Adress is 0.0.0.0. WHY!!! PLEASE HELP. More details:
This is my work computer. Sometimes it gives me this problem, sometimes it doesnt. For example, it worked all day yestereday, but today it is “Acquiring Network Adress”, and the day before yesterday it was not working either. It is connected directly vie ethernet to a switch, and I have checked to make sure those services are running, and automatic. I connect that same ethernet cable to the desktop beside the laptop and it works just fine. Somebody please help. Thanks.
April 26th, 2006 at 12:00 am
I forgot to mention that it works at home every single time. No problems there whatsoever, i connect via ethernet.. and bingo im in. Just not at work.
May 2nd, 2006 at 12:00 am
Thanks for the blog.
After having a perfectly good wireless connection for ages, one day my connection decided to die. Hanging on “Acquiring network adress”. The thing is I had just been clearing my computer of ad ware, viruses etc….
What fixed it for me was to re-install my wireless network drivers (in this case Intel). So for those who have tried everything else, try re-install your network drivers. might help.
Thanks
May 6th, 2006 at 12:00 am
Just thought Id say… I had the same problem and this Blog help me fix it.
Ive got 2 3com usb connections to a 3com wireless router. One connection worked the other did not … “acquiring network address” [rpblem even though both were configured the same.
I fixed the non-working one by enabling “netbios over tcp/ip” as suggested above, then I had to re-enter the wpa key in my router, then I re-did the key in my network adaptor.
Unfortunately the other adaptor stopped working. I did the same to that one (enable netbios and then re-did the wpa key) and now both of them work
June 28th, 2006 at 12:00 am
I have had this problem thrice, and every time the cause and solution were different (lost three days of my life). This time when the I kept getting the message “Acquiring Network Address”, I had to go to http://192.168.1.1 (I use WRT54G wireless router), clicked wireless tab, and then wireless security tab. Somehow (only god knows how) my WPA Shared Key had been reset. Anyway, I got the new key, Opend My Computer on my laptop (the one that couldn't find the Network Address), open Nework Connections, right-clicked Wireless Network Connection for properties, clicked Wireless Networks tab, clicked on my wireless network name and properties, and finally entered the reset WPA Shared Key in the Network Key section. I'm back on line!!
July 16th, 2006 at 12:00 am
I too have a dell inspiron 6000 that is stuck on 'acquiring network address'.
After trying many of the mentioned solutions on here it suddenly started working, but only for about a minute. Then it disconnected, then reconnected… etc etc. When it is connected i cant browse the internet (but this might be because its not connected long enough for it to find a page!).
Basically, the network connection is constantly detected, but connected on and off!
Does anyone have any further suggestions?
I've tried the DHCP start/restart suggestion but it still wont connect constantly.
Any help would be muchly appreciated
Thanks!
July 18th, 2006 at 12:00 am
I've been connecting purrfectly fine wireless to a Netgear router for about a year, and then all of a sudden I started getting the Aquiring Network address problem. Nothing has been changed, on router or laptop. But around the same time I did introduce another wireless router into the same vicinity that I was previously connecting to in another office. The two routers have WPA-PSK security however each have a different key and SSID, in one case SSID is broadcasted the other is not. I got frustrated with the problem so I then found this blog board to find out how to fix the problem. The extra router is now gone but I think I started to get the acquring network problem straight after I took the other router away. Anyway after trying everything I could think of including the couple of extra things from this board, I hadn't yet looked at, it still didn't work. In fact nothing seemed to be out of place through all of this, it was a case of redoing and rechecking all the settings and I still was getting the network acquring problem. And a little while before writing XP was using the Intel Proset software to manage the wireless card, so I decided to switch back to Windows Management (I have already done this a few times) then buggered if I know why but it is now connecting without any problems.
Anyway the problem seemed to kick off due to the combination of the two Access Point's and then one leaving. There does appear to be some sort of bug in XP (SP2)..
July 25th, 2006 at 12:00 am
i have a simular problem, I just bought a new laptop and have been setting up the wireless network for it. my home has has an intergrated system of CAT 5 and wireless networking from a linksyes router. Anyway i installed a belkin wireless router downstairs so could extend the range of my wireless. My downstairs Desktop works fine with the LAN line plugged into it, but once i run it into the belkin router and back to the desktop there is limited or no connectivity. It cants renew the IP address when i renew it for awhile it just says aquiring network address but nothing happens. My laptop cant pick up any signal from the downstairs router, and to mention this same thing occurs when i plug the the cat 5 cable into my notebook. im basically trying to use the second router as a range extender for my current network but it just doesnt seem to be happening. Any advice?
July 27th, 2006 at 12:00 am
I have a brand-new Dell XPS running the latest Windows XP with SP2. This “Acquiring Network Address” bug hasn't been fixe. I read through most of this blog and tried a bunch of the things suggested, including:
Disabling TCP/IP
Enable NetBios over TCP/IP
Running services.msc to re-start my DHCP (it had not stopped, but I restarted it anyway)
None of these things worked.
But before I started trying to manually change the IP address for the DHCP to agree with the IP address of the router (how do you do this?), I tried SteveO's wonderfully elegant suggestion.
I just plugged straight into the Ethernet port on the back of my router and (without re-booting) the internet connection started working fine. Then I unplugged the ethernet cable and (again without re-booting) the wireless worked perfectly. I don't know how it worked or whether the wireless card has acquired the correct IP address somehow. But this is a fix I can live with.
Just like whenever anything weird happens you just re-boot and somehow magically the weirdness disappears. I agree with Lee's opinion of Bill Gates. MS Pig is destroying innovation in the computer industry. Not only that, we are all forced to live with a permanent reduction in efficiency having to continually deal with this crappy software and all these work-arounds.
They should have busted the Microsoft monopoly up. Bill Gates is worse than John D. Rockefeller!
August 14th, 2006 at 12:00 am
Same message - Acquiring network address. On running services.msc Dhcp services will not run on my machine. Error message is 03 System cannot find the path specified.
Any help from anyone?
September 3rd, 2006 at 12:00 am
I had this…but I didnt read all the posts here because I found if you right click on the wireless icon in the tray there is an option 'Repair'. I clicked this and it did some stuff like stopping the wireless connection AND wireless card and then restarting them all.
It fixed it!
All the best
September 3rd, 2006 at 12:00 am
hi there, i was frustrated, for this problem, but i just thought i should share as I got to fix this problem.
Just try changing your SSID channel to 6 and that could work. as It works for me.. you can try 11 if it was originaly 6. good luck
September 20th, 2006 at 12:00 am
Hey TavoLoco,
Thanks for the info… It worked for me. When I turned on my PC all of the administrative tools got disables. I don't know I someone did it or just an error in the software. Anyway, I tried to enabled some which I know is needed for network connections but I still got ACQUIRING NETWORK ADDRESS. I've enabled DHCP client and it worked! Thanks!
Gotta go… I have to continue on my thesis LOL..
=)
dude…. acquiring network address is basicaly translated to an ip address 0.0.0.0, if a winxp does not have the sp2 it will just say invalid ip and the ip is 0.0.0.0 here is the procedure to correct this
click on start, run, services.msc
look for DHCP client…. if it sess acquiring network address that means that the dhcp client is DISABLED OR STOPTED… highlight the DHCP client and on the left side you will see “START” the service, click on it and then it will say “STOP, RESTART” then double click on the service and on the startup type select automatic, apply
THAT IS THAT!!!! this shit works…
by the way.. also chk the tcp/ip properties, make sure that we have all to automatic
Posted by: TavoLoco | Wednesday, September 14, 2005
September 28th, 2006 at 12:00 am
I know im abit late to the party but I was having the same problem and this page rates so hoghly on google that i tryed it… I was reading for a while trying everything nothing worked… As silly as this sounds when i got to lees post on November 12 2005, i just tryed exactly what he did and this might sound stupid but it worked… so try it you might have luck as well… PS My mack has never had a problem but my room mate and my windows xp laptop stopped working at the same time!! stupid Windows MAC RULE!
October 2nd, 2006 at 12:00 am
For all the people who tried all the steps suggested by people, but didn't work (like me):
After trying everything here, I had the bright idea to re-install my integrated wireless cards drivers again using the driver recovery cd that came with the laptop.
It worked! The solution was as simple as that, yet I had spent hours trying to find the solution while it sat right under my nose.
October 3rd, 2006 at 12:00 am
Hi Everyone,
I went through the same kind of problem “Acquiring Network Address” in my Dell Inspiron 1300 laptop with “Dell (US) WLAN card”. Tried many solutions suggested here and they did not work. However, finally tried a combination of something suggested here and some on my own and the combination worked. Here is the sequence:
1. Down loaded the driver for this card from Dell.com using my wired LAN
2. On control panel, through Add/remove programs, removed the driver for the wireless LAN card
3. Rebooted the system (just to be sure)
4. Installed the new driver
5. Rebooted the system
6. Double clicked on the wireless “status bars” icon. (This is the most important different step so far different from all the other things I tried earlier, including re-installing the drivers). It asked me whether it could be the default setup wizard. I said yes. Then asked for the WEP key. Gave my key and went through the process. Boom, the connectivity worked.
You could try clicking on the “status bars” icon without even re-installing the driver and it might work.
This makes me believe that the Windows Wireless Setup Wizard is screwed up.
Hope this procedure helps everyone who has the problem here.
With regards,
—–Balan
October 4th, 2006 at 12:00 am
[i]Windows XP is a very nice operating system, and Microsoft makes good products. As I tell my class, they make pretty good products that are pretty easy to use at a pretty good price. They are not the best in anything, but they are pretty good in everything.[/i]
What brand of crack are you on?
October 4th, 2006 at 12:00 am
“What brand of crack are you on?”
The kind that lets me boot up a computer and simply install commonly used after software applications, unlike Mac, Linux, etc.
PS: Balan, Rew_Klip, Mikitukka, Pai Abu, et al: Thanks for keeping this technical help forum going!
October 5th, 2006 at 12:00 am
I have a Zonet ZEW2500P wireless adapter and it initially worked for about a month, but then overnight it went into “limited or no connectivity.” In trying to re-establish the connection I am told that “the network has not assigned an address.” The modem can always view available connections within range, but it will hang on “acquiring network address” and then fail to connect and provide a notice that “this connection has limited or no connectivity.” I have tried re-installing drivers, using windows service, using the software that came with. The one thing I have yet to try is starting up the DHCP through services.msc. I know DHCP is listed as enabled in the wireless settings so I doubt that is the problem but I will give that a try tonight and hopefully that will work because I am running out of things to try.
Nice forum, thanks for the making it available.
October 7th, 2006 at 12:00 am
Having a problem with my computer acquiring an ip address- I am using netgear wireless nic card and it just sits on “acquiring an ip address”. I tried connecting the computer directly to the modem and that still does not work. I also took the computer into my work and it still does not acquire an ip address - Any suggestions?
October 12th, 2006 at 12:00 am
I have the same enigmatic problem “aquiring network address” rather ironic as it will do anything but.
I have had a go at all the possible solutions outlined above to no avail.
I would rather not overite or re-instal windows, I have even tryed the Winsockfix prog that cleans up the reg.
If it try to start the DHCP service it gives me error 1068
If I had hair it would have been pulled out by now.
any clues would be greatly received.