Mr. Gowifi. Everything on the router is ok, and the wireless can see it, but the same message continues. SSID is identified, firewall is off, just in case, I've changed the wep several times, but nothing.
Another clue, please!!!
Mario
Quote:
Originally Posted by gowifi
Hi there
This can often be an issue with security encryption. There may be a wrong key entered or the client adaptor does not support the encryption used.
To try and solve this first change the SSID on your AP so your laptop will be forced to create a new profile. Then set security to basic WEP 64bit and try to connect again. Update the wireless adaptors drivers.
If you have any third party Firewalls, try and temporarily disable them to make sure they aren't blocking it.
Good luck
Dale
.
My main PC went online - no problem. My laptop would not connect; Wifey's PC would not connect. All three connected OK two days ago. Wifey's PC would connect to our Pinnacle TV streamer, so I knew her equipment was good.
I started poking through my router settings and found that DynamicDNS was disabled. Re-enabled DDNS and all's well. Still can't figure how DDNS became disabled.
.
I wanted to post a big THANK YOU to gowifi. His advice early in this thread was correct, even though the fix seems a bit illogical. As a database administrator, I use computers all the time, but this one stumped me. My wife's laptop stopped connecting wirelessly, but would still work with a wired connection. She swears she didn't install any new software. She's not a superuser; she doesn't do any tweaking; she mainly just surfs the net and uses email. My laptop still worked fine connected to the same wireless router. I had WPA Personal security. I verified that the passcode was still the same, re-entered the passcode in my wife's profile, still didn't help. Tried removing the wireless entry from her device manager and letting it re-discover... no help. After working with her laptop for 4 hours, I gave up and figured her internal radio must be fried. Went out and bought a new Linksys WPC100 card, installed it, but had the same problem! It was hanging at "Acquiring Network Address". I hard-coded a valid IP address, but still could not get a network connetion. All this time, my laptop was connected fine. Finally read this post. Changed the SSID and disabled security. The wife's laptop connected! Added WPA Personal security back, tried reconnecting the wife's laptop with the WPA passcode, hung at "Acquiring Network Address" again. So I changed to WEP security, and it connects again! Why in the heck would WPA Personal security just randomly stop working on her laptop when she didn't even change any network settings? I'm glad it works with WEP, but am extremely curious about the WPA issue.
I have had WPA headaches, too. Maker of the NIC is not keeping the driver up to date. switch to a Linksys card, put in the latest driver, all is well. the driver was as up to date as I could get, but not as up to date as it could be.
I work with computers all the time, and have been getting stuck with this message a lot. Bumbling through like everyone else. I found a solution today and have a theory on how it happens. I believe it happens when the data structure that is passed to set up the network is damaged it simply stops working and gives you the message “ Acquiring Network Address” Which actually that is what is is trying to do.
How or why for us I don't think matters much. This is a solution that I had come up with when I had three laptop computers on the network and a identical laptop that was on the other day working and today not working.
I found and deleted the network place off the computer. The computer then recognized it as a location I could sign into. I selected it and had to enter the network key. And it came up the first time.
Don't know if it will solve all the problems that I have read about. But it certainly worked for me.
Good luck
Frank
Frank's theory worked for me. I had an old Dell Latitude D600 laptop which used to connect to the wireless network at my home. This laptop was in dis-use since Nov 2007 b'cos I got a new HP laptop. I had some problems with that HP laptop. So, I dusted off this old pal and tried to connect but all it did was "Acquiring Network Address" I put the key again with no luck. But, Frank's idea of removing my wireless network forced my laptop to recognize that network again. I had to put the key again and lo the laptop connected in a flash. Thanks Frank and other members of this forum....
I have had the same problem: I have an older D-Link wireless router (DI-524), and my wireless worked (and works) great with my 5-year old Gateway laptop. I just bought a new Samsung netbook, but I can't consistently connect.
The signal strength is excellent and good, but I get the same error messages ("acquiring network address").
I have tried resetting the cable modem, the wireless router, setting the IP address manually, updating drivers, removing the network from the new laptop and reinstalling it, disconnecting the firewall.
Sometimes, it will work for a few minutes, but then it stops again. But my old laptop (which doesn't get as strong of a signal) can find the addresses fine.
Could this be caused by an older router? If not, any other suggestions?
A very basic but effective solution to 'acquiring network address' hangups.....
Having looked deep into all the possible solutions for this very common problem, I found this simple remedy to be effective for most of the times I've encountered the dreaded 'acquiring network address ' syndrome with XP OS's : In the Start/Network Connections/Wireless Network Connection/View Wireless Connections window, try refreshing the network list......
and see what happens....
Last edited by ComputersSometimesLie; 06-27-2009 at 01:05 PM..
Reason: typestyle hard to read
STATIC IP ADDRESS,manually config your wifi adapter to a static fixed ip address, you WILL NO LONGER HAVE "ACQUIRING NETWORK ADDRESS" PROBLEM!!
Search on google for manually config wifi adater for a static ip address, or read one of my posts on here on that subject.
Let me know if it works, always works for me even with alfa 500 mw usb adapter!
i know this thread is old, but please someone please help me!!!!
ok my main computer was having problems so my dad disconnected the hard drive and went to fix it. the guy said it was a virus and cleared it. the guy changed our windows vista to windows xp. everything including the the internet was working fine. but i wanted to change our windows back to vista. i used a vista transformation pack but then a day later i deleted it. then i went to search online to find another program but i was dissatisfied so i deleted that too. but after i deleted that, the internet suddenly didnt work. the internet connection said 'acquiring network address.'
on my brother's laptop (the one i used to reply this post) it said 'acquiring network address' for few seconds and then it worked (the internet). on my main computer, i also checked the connection status and it said this:
Address Type: Invalid IP Address
IP Address: 0.0.0.0
i also tried repairing the connection but it said this: 'Windows could not finish repairing the problem because the following action cannot be completed: Renewing your IP address'
I wanted to post a big THANK YOU to gowifi. His advice early in this thread was correct, even though the fix seems a bit illogical. As a database administrator, I use computers all the time, but this one stumped me. My wife's laptop stopped connecting wirelessly, but would still work with a wired connection. She swears she didn't install any new software. She's not a superuser; she doesn't do any tweaking; she mainly just surfs the net and uses email. My laptop still worked fine connected to the same wireless router. I had WPA Personal security. I verified that the passcode was still the same, re-entered the passcode in my wife's profile, still didn't help. Tried removing the wireless entry from her device manager and letting it re-discover... no help. After working with her laptop for 4 hours, I gave up and figured her internal radio must be fried. Went out and bought a new Linksys WPC100 card, installed it, but had the same problem! It was hanging at "Acquiring Network Address". I hard-coded a valid IP address, but still could not get a network connetion. All this time, my laptop was connected fine. Finally read this post. Changed the SSID and disabled security. The wife's laptop connected! Added WPA Personal security back, tried reconnecting the wife's laptop with the WPA passcode, hung at "Acquiring Network Address" again. So I changed to WEP security, and it connects again! Why in the heck would WPA Personal security just randomly stop working on her laptop when she didn't even change any network settings? I'm glad it works with WEP, but am extremely curious about the WPA issue.
I also (finally) reached WiFi nirvana by following these instructions, particularly Wadecole's detailed breakdown above. Good stuff!
I had upgraded my Asus laptop's internal card to use a Gigabyte GN-WI03N (mini) PCI WLAN (wireless-N) card to take advantage of my new Wireless-N TrendNet TEW-633GR router. Created a SSID and used the strongest security available (WPA2), connected using Gigabyte's Wireless manager on the laptop (not the stock Windows manager) and all was well. Stopped working after about a week of flawless operation (endless 'acquiring network address'). Eventually came across this post and tried recreating same SSID with no security and managed to connect to the router straight away. Will try WEP security next as advised in the posts as I don't want to leave the network open to all and sundry...
Just thought I would reinforce the good advice (for me at least).
Good luck,
Bruce
Update a couple of hours later: Hah! of course WEP isn't compatible with the wireless-N standard so I can either have a fast open network or a secure wireless-G network. Well I suppose life would be boring if everything was perfect!
Thanks to all, and Roadhouse's solution worked for me, too! I have a linksys router and I went to the status page to find the DNS servers to type into my TCP/IP settings, and did and a run -> cmd -> ipconfig to find the IP address I could type in, 192.168.1.100, and then found the Subnet mask on the same page, and used 192.168.1.1 for the gateway.
I use Dell wireless utility to manage my settings and I've disabled Wireless Zero Configuration in Run -> Services.msc
My wireless icon used to take forever to load and then would say no connectivity and then most of the time it would connect at that point. Now it loads immediately and clears the cache as well!
I thought I'd join up to post another possible solution that worked for me. None of the above mentioned things worked, though I didn't go all the way to the end of the page so excuse me if this was already described. All I did was go into the TCP/IP settings under Properties of the network and forced it to use an IP address in the range of the router (192.168.1.4 in my case) then put in the gateway (192.168.1.1). Then for the DNS address I went to the router setup page (accessed on mine by typing 192.168.1.1 into the web browser) and found it in there and entered it into the fields. Clicked OK and all of a sudden it worked.
Hi there, just an update three years later. This problem can often happen when the security encryption key does not match or the computer wireless drivers do not support the encryption on the access point. If other computers have no problem connecting to the AP then try the following.
Delete the saved wireless profile for the SSID of the AP you are trying to connect to, this is under the properties of your wireless adaptor. When you try and connect again it will ask for the password again and make sure it is typed right.
If this does not work then update the drivers for the wireless adaptor in your computer, incase they are out of date. If it still does not work then use WPA-TKIP encryption on the AP as I have found this to be very compatible with most wireless cards.
Cheers, Dale.
Done everything in here but I still have the problem.
Background history. I have a Linksys wusb300n adapter it has been running on a desktop computer with xp-sp3. I decided to reinstall windows on a new hard drive but keep my old version on my old drive.
No problems with the reinstall of windows but after installing the adapter (driver only) I get the deadly acquiring network address problem.
I have
repaired the network connection
uninstalled the adapter and re-installed.
renamed the ssid
ipconfig'ed renew
disabled all encryption
+ more suggestions - flushing stacks, server detections on auto etc
Nothing works.
However, I put my old drive back in the computer I get flawless connection.
I have looked at everything I can think of but it all looks the same between both sets of windows.
This problem is driving me nuts.
I have looked at so many forum pages.
My wife is telling me to get out but I just cannot let go of it.....
TIA
Flyfire
i really need help. i've set up this new netgear router at home, and my computer is working perfectly but i want to use my laptop wirelessly and the laptop says "Acquiring network address". i really don't know what to do and i've looked at your replies but i still don't understand so please help me
Hi there
This can often be an issue with security encryption. There may be a wrong key entered or the client adaptor does not support the encryption used.
To try and solve this first change the SSID on your AP so your laptop will be forced to create a new profile. Then set security to basic WEP 64bit and try to connect again. Update the wireless adaptors drivers.
If you have any third party Firewalls, try and temporarily disable them to make sure they aren't blocking it.
Good luck
Dale
i really need help. i've set up this new netgear router at home, and my computer is working perfectly but i want to use my laptop wirelessly and the laptop says "Acquiring network address". i really don't know what to do and i've looked at your replies but i still don't understand so please help me
reply ASAP
THANK YOU SO MUCH!!!!!
i really don't understand these technical stuff,,, so confusing but plz help me!!!!
Hello
I know there's another post with an almost identical title, but it seems to
be heading off into different territory, so...
I'm running 3 HP laptops - 2 using Vista, the third running XP. Also
connected to my wireless network are three Apple Airport Express, and a PS3.
I'm running a Belkin N1 Vision router.
I have enabled security (WPA2) and all devices can successfully connect to
my network. The issue is that the laptop running XP intermittently drops the
connection and in the Wireless Network Connection window continually is
'Acquiring Network Address'. I then have to re-connect manually but even then that doesn't fix the problem. The frustrating thing here is that all other
devices do not have this problem, and I know that this can happen to the
laptop running XP regardless of it's location in my home and proximity to the
router. Yes, I have 5.8ghz cordless phones also but they don't seem to impact my network with the Vista laptops never experiencing the same issue as the laptop running XP. They are all different models of laptop and yes the one running XP is the oldest of the three (about two years old). The XP laptop is up to date with the latest XP service pack.
As I write this the XP laptop has been connected and has remained connected for around 45 minutes without issue. But chances are that won't be the case some time from now and I'll be back where I was.
I recently bought 2 acer netbooks. The same model just 2 different colors. The pink jumped into the network with no problems. The blue on the other hand kept giving me the "aquiring network address" status. After searching forums for hours I came upon a blog that fixed my problem easily.
Run the Network Setup Wizard. I named the network the same as what I had setup my router with. If this made a difference, I don't know. Restarted the netbook when I was prompted to, and Vuala! Accepted the network right away, and has had no problems since.
Here's my situation. I just got that AT&T u-verse internet, phone, and TV package thing last week. I had everything working when it got set up, but I've decided to reinstall everything on my computer becasue it had been a minute, plus I had XP as my only OS, and I'm really more of a Linux guy, plus I got a shiny new windows 7 ultimate.
My wifi router is is a 2WIRE 3800hgv-b
My wifi card is a netopia 3d reach USB card.
So I've got Windows 7, Windows xp pro, and Ubuntu all on one machine, just installed them fresh today. Ubuntu, of course works flawlessly with my wifi, it took a minute for 7 to start working, and a little configuration, but I got it up no problem really. XP however seems to be a little slow... I get that always pleasant acquiring network address message. Thing is, just yesterday I had it working before I decided to start fresh, and I'm using the drivers that I just got from AT&T. I also downloaded the drivers from the site, but they are the same versions as the ones on the disk, but they didn't work anyways. I tried resetting the SSID and the wep key, and yet XP is still not working. I installed that wonderful XP black, and it works perfectly there, but I would rather use my actual XP-pro since it's legal and all, plus it works better with my graphics card. Why in the world won't XP make it work, and every other OS on the freaking planet has no problem... It just makes me feel like going to full linux lol. Any help would be appreciated.
We have been having the same problems with my wife's work laptop (running WinXP).
The WiFi card was seeing the network, getting through the password validation thing Ok but was then hanging after that. We were able to get the machine to connect using a wired connection.
We have solved the problem by deleting the saved WiFi key and deliberately entering an incorrect one and then re-entering the correct WiFi key.
Everything then worked perfectly!
Having read previous posts I suspect it is something to do with the encryption stuff and re-entering the key we reset the authentication information.
Hi there
This can often be an issue with security encryption. There may be a wrong key entered or the client adaptor does not support the encryption used.
To try and solve this first change the SSID on your AP so your laptop will be forced to create a new profile. Then set security to basic WEP 64bit and try to connect again. Update the wireless adaptors drivers.
If you have any third party Firewalls, try and temporarily disable them to make sure they aren't blocking it.
Good luck
Dale
I'm not good with computers, so if you can help me please explain it to me as simple as possible.
I have a dell lap top and a net gear wire less router. My brother in-law hooked everything up for me months ago and everything was working fine. Recently I can not get my lap top to connect to my wireless router. It recognizes the router but it will not let me connect to it. When i try to repair the problem its says that it can not renew the IP address.
Can I enter in an IP address?
One suggestion that i got from a friend was to uninstall the router and then reinstall it. I really don't want to do that because we had a hard time installing it in the first place. Does anyone have any other suggestions?
Lisa
Hello, I am having trouble with my linksys router. I have 3 devices that connect to it wirelessly. When jus tone of these devices is on, they will connect fine (only one at a time). When more than one comes on, the second one that comes on sits at 'aquiring network address', its like the router wont let the other devices connect. I have not changed any setting on the router other than WPA protection. The 3 devices are a PS3, and two laptops running Vista. Again, they all connect fine when no other device is on. Any suggestions?
I am running a Dell Inspiron 700M with Windows XP. I have been connected to my apartment's internet through a LAN cable for about a month with no problems. Yesterday I left my computer for about 10 minutes, and came back to find that it was disconnected. I tried disabling and reenabling the icon in network connections, and also tried restarting. I've also run AdAware, Spybot, and HijackThis, and come up with nothing out of the ordinary. Basically, when I enable it, it goes to "acquiring network address," and then gets stuck there for a couple minutes. Finally, it switches to "limited or no connectivity" with an error triangle icon. I've tried plugging my laptop in to my roommates' jacks, and they work fine. Unfortunately, none of them have laptops, so I can't try plugging them into my jack. But I've concluded that the problem seems to be with my computer.I've done some Google searches, and from those results, I've tried disabling TCP-IP (even though I didn't have two TCP-IPs, I thought it was still worth a try; it didn't work though, so I put it back), using Winsockxpfix, using Dell's Driver Reset Tool, etc. I found this post here <http://forums.techguy.org/history/t-395689.html> which seems to be the same problem, but even though I went to the link that was given, I couldn't really get a clear idea of what I was supposed to do to fix it (I thought that Winsockxpfix would do it, but it didn't).
Nothing ! 
Frank's theory worked for me 
I put the key again with no luck. But, Frank's idea of removing my wireless network forced my laptop to recognize that network again. I had to put the key again and lo the laptop connected in a flash. Thanks Frank and other members of this forum.... 
A very basic but effective solution to 'acquiring network address' hangups..... 
i also have the same problem 
"Acquiring network address" problem 
Linear Mode
