[Jibaku]

I'm having essentially the same problem as described in this thread.

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 bring my laptop to work because my web maintenance job occasionally requires things that the work computer is not equipped for, like graphics editing. For months I've been networking with the work computer just fine, then suddenly it stopped working.

Just before I hit this glitch I stayed in a hotel with a wireless connection. While there, I input the network password but couldn't connect, so they had me delete their router from the list and manually re-enter it. After that it worked fine. However, I ran into this issue when I got back to work.

The oddity is that I tried taking the same action to correct the problem - deleting and re-entering it - but it made no difference whatsoever. Even though the computer can automatically detect the router and I have the correct password, it just sits on "acquiring network password" infinitely or "limited to no connectivity" just as described above. This has been a persistent problem for weeks now.

My laptop is a Dell Vostro running WinXp. The work computer is a Gateway running Vista.

[Jibaku]

I take the lack of response to mean that there is no new information on this type of error. I was hoping that since it is so common someone may have discovered the most likely solution.

[Wanderer2]

Odds are you are not putting in the correct encryption key [wep/wpa/wpa2] when you are connecting to your work wireless connection.

There are many reasons for the "aquiring network address" of which most are related to passwords or physical connection requirements.

[Jibaku]

If the encryption key is the same as the network key, then it's correct. As I said, I was connected without issue for months before hitting this glitch. Therefore I assume it's something minor, but that isn't it.