Not able to aquire address if using WPA/TKIP...works with WEP or none

Hi all. I have no idea what is going on with my system, so I thought someone out there might have figured out a fix.

I have an old Linksys WRK54G (note WRK) wireless router with the latest albeit a couple years old firmware from Linksys (1.55.02).

I have an ASUS W3000 with an Intel Pro-Wireless 2915ABG card; driver version is 9.0.4.39.

I am not able to connect when I use WPA/TKIP. My laptop sits there with the windows status window saying "acquiring network address" and my Intel PROSet/Wireless Wifi Connection Utility v 12.0.4.0 window saying "Authentication process to connect to the network has not been started." It sits there until a timeout and get the 169.xxx.xxx.x private address. Doh.

If I use WEP or no encryption, I am able to connect without a problem.

Oh, I am using Kaspersky Internet Security. Doesn't make a difference if I turn it off or not.

My wife's Dell laptop is able to connect no matter what the settings are.

Anyone else having this connection problem??

Thanks for any help.

 

Hi jmarble

Try uninstalling and reinstalling the software that came w/ your wifi, if any. Otherwise, make sure you have the latest drivers. Even with older hardware, new drivers may be available. Linksys tech support would suggest the same thing, after they asked you what system you had including OS, even if you'd already posted it (as you did here) If nothing else works, make sure that a surge hasn't managed somehow to reset your encryption. My system was hit by a power surge that did that. All that was needed was a re input of the password in the linksys utility. Try using your wireless zero configuration if all else fails. This is another thing that linksys is likely to suggest if you ask them what you should do. Beyond these ideas, I wouldn't know. I hope some of that helps

 

Hi jmarble,
I have exactly the same problem:cry:cry
I have recently connected a brand new Buffalo router to me Dell Desk top which replaces my 6 year old Linksys router, and the problem exists with both the old and the new!!!
I can connect to the internet with encryption on using my brand new laptop, however I can only connect to the internet with my 3 year old HP laptop when the encryption is switched off.
I have searched many forums and tried many things....all to no avail.
I am running Windows XP on all 3 machines.

If anyone can help successfully resolve this I will be very grateful indeed.

fcs

 

I feel your pain. I have pretty much tried everything I know what to do. I hope someone has an idea of what to do out there.

I am attaching a screen shot to help folks out.

 

jmarble, my screen image is just as the visual you posted. We are not having much luck with responses.

Next I am going to check if my Windows OS is genuine. I had a 'system crash' recently whilst on hols and a local vendor got it all going again by doing a re-install.

Subsequently I was able to surf the web at wireless zones. It was only when I got home that I found the problem with encrypted wireless connections.

Will post more later.

 

Affirmative, the new installation of Windows XP is genuine. and I am able to download Microsoft updates.

I have fiddled around a bit more but still without success.

There must be someone out there who can help solve what would appear to be a 'fairly simple' problem!

 

You can try this:

1) Uninstall the Connection utility
2) Manually trying to connect instead of looking for the SSID broadcast.
3) Update the firmware for the router. If it's an old router, their code might be wonky for WPA. Linksys also has a fairly large support forum so most likey if you're still stuck, someone there should be able to help you.

 

Thanks for the post olestros. I have tried suggestion 1. I will try suggestion 2 tonight when no one else is using the internet in the house. I have looked everywhere; there are no firmware updates for my Linksys router and from other posts I have learned that I can't flash it either. Oh well. I am thinking of getting a new router. I don't feel secure checking my accounts with only WEP security.

 

I encountered a similar issue today with an acquaintance's Dell Latitude D610, running Windows XP Pro SP2. The laptop contains an Intel Pro-Wireless 2915ABG card, with the latest drivers and WiFi utility from Intel's website. My router is an Airlink AR670W. I tried a few things and managed to resolve it in the end. Here are some of the things that may have contributed:

1. Install update KB893357 (provides support for Wi-Fi Protected Access 2).
2. Let Windows manage the WiFi connections instead of using the Intel PROSet/Wireless Wifi Connection Utility.

I hope this info is of some use to someone out there.

 

Hold on jmarble,
That exactly what I did and it did not solve the problem
I had a Linksys router for the past 6 years. Very robust and strong signal. I thought that age may may be the problem so bought a new Buffalo Nfinity WZR2-G300N, but i still have the problem.

Think I will try the suggestion by metababble, (Install update KB893357, if it is not already installed) but I have tried his 2nd suggestion without success

 

There is a ton of stuff here.
I have ploughed through a lot of it today....but still no successconfused

http://www.tdaxp.com/archive/2005/02/05/acquiring-network-address.html

 

Weeeeeell If you're looking to buy a new router, and you're willing to brick your current one, you can try various different open source firmwares. These are usually *better* than vendor ones but there is some risk involved as they can brick a router and they're a bit tricky to unbrick. The follow are a few I'd reccomend looking into especially if you have a WRT series.

DD-WRT -- www.dd-wrt.com

Tomato/MLPPP - http://fixppp.org

Tomato is especially good if you're being traffic shaped / throttled on your ISP side.

 

I have been too busy to try any of the suggestions yet. I hope to get to it this weekend sometime. I will keep you posted if something ends up working.

 

Thanks,
Likewise. I have been too busy to sort it so far but determined to do it this week even if it means a 're-install'....but first I will try a number of options still available to me.

It seems like a simple problem particularly as we can connect without encryption, so you would thing the solution would be simple and obvious, but as the link I posted earlier shows, this is a very common problem, and 'one size' solution does not fit all!!

 

Hi jmarble.
Did you solve the problem. I am still living with it. This thread seems to have gone dead.
I am amazed that a solution is not out there wanting to be posted

 

From the weakest to the strongest, Wireless security capacity is.
No Security
MAC______(Band Aid if nothing else is available).
WEP64____(Easy, to "Break" by knowledgeable people).
WEP128___(A little Harder, but "Hackable" too).
WPA-PSK__(Very Hard to Break).
WPA-AES__(Not functionally Breakable)
WPA2____ (Not functionally Breakable).

Note 1: WPA-AES the the current entry level rendition of WPA2.

Note 2: If you use WinXP and did not updated it you would have to download the WPA2 patch from Microsoft. http://support.microsoft.com/kb/893357

The documentation of your Wireless devices (Wireless Router, and Wireless Computer's Card) should state the type of security that is available with your Wireless hardware.

All devices MUST be set to the same security level using the same pass phrase.

Therefore the security must be set according what ever is the best possible of one of the Wireless devices.
I.e. even if most of your system might be capable to be configured to the max. with
WPA2, but one device is only capable to be configured to max . of WEP, to whole system must be configured to WEP.

If you need more good security and one device (like a Wireless card that can do WEP only) is holding better security for the whole Network, replace the device with a better one.

Setting Wireless Security - http://www.ezlan.net/Wireless_Security.html

The Core differences between WEP, WPA, and WPA2 - http://www.ezlan.net/wpa_wep.html
.

 

Fizzychickensoup, sorry I haven't posted lately. I haven't figured out my problem yet but haven't had the time to fix it either. If I do figure it out, I will let you know. Good luck.

 

Just to let you know I spent 9 hours yesterday trying to fix the problem....and sadly I failed. Today I took the laptop to the computer shop for a full re-install:cry:cry:cry

 

At last the problem has been resolved, but it took a full re-format/re-install to do it.

When my lap-top crashed in Phuket back in Aug, I was just about to go to Koh Samui, so I had Windows XP reinstalled there. I now know that he used a 'bootleg version, and used 'muBlinder' software to allow MS updates to take place.,
Everything worked well until I got home and found that I could not get internet access with an encrypted signal. I tried everything I could think of without success.

I then thought I would do a full reinstall myself with my original Genuine software. However Windows detected that the current version was newer, and would not allow me to install the older version. I tried a few permutations including reformatting the C drive, and I was unable to even perform that task. It was at that point (9 hours later) that I gave up.

My parting shot is that if you have 'bootleg' Windows software you may only be able to surf with an un-encrypted signal!

Bill Gates is one Crafty Fox!:-D

 

Wow...quiet the ordeal. I am glad that it is working for you now. To be honest I haven't had the time to mess around with it. Next weekend will be computer time. I am pretty sure my Windows XP is genuine so that should be the cause of problems. I hope I can also figure it out.

 

I had this problem on a clients computer.. I sat there for a while thinking it was the computers fault.. where it was the wireless access point causing it.. All I ended up doing was destroying the encryption on the Acess Point and re-enabling the WPA-PSK key. I had a working network again and no problems since.

Try doing that and see if it fixes it.

 

As my very first post stated, one laptop works fine but the other does not therefore this latest proposed solution did not work either. Until I did a full reinstall that is:rolleyes

 

I've had it work on one but not the other before too... I've done that and it fixed it... not sure yet what causes it though.