hey, i had this problem running XP home edition, i am now on XP pro on my macbook and same problem, first i couldnt connect at all but then i figured it was because i had DHCP process disabled so it wouldnt get an IP from the DHCP server... thats fixed now i get an IP and all the network information... running ipconfig/all shows that i'm on the network properly, the internet and network works just fine... its just that windows never realizes that its connected the icon shows connecting, double clicking on it shows
status: acquiring network address

if i click on properties, then just click ok without making a change then it switches to status connected although nothings changed
ive googled this and havnt really found a solution, its not that bad because internet works.. it's just annoying as hell


suggestions?
thanks


EDIT*** it also does it with wired connections, same thing, if i go to properties then "ok" it's fixed temporarily

tried clicking on "repair connection" even though everything is alright? or maybe ipconfig /release, and then ipconfig /renew.

Linksys router?

I just had this issue with mine and my dell laptop(w/ intel proset wireless software). I had to run the Linksys easy link advisor and actually add the laptop even though I had been connected before. As soon as I did that all was good.

Snugg.. his connection is fine. He has disabled a Windows Service.

Kage, besides disabling DHCP Client service (which you now turned back on), what other services have you disabled? I am pretty sure you were doing some tweaking, so all you have to do is revert back some settings.

ive reverted back to default services and no dice.... i did notice a few things tho
1) it didnt do it today when i connected to a unprotected network
2) it has nothing to do with my router it does it on every connection, at home or at work or at school
however if the info helps you, my wireless has 3 access points, one directly in my firewall (pfsense), a dlink upstairs and a linksys downstairs (its a really big house haha 1 AP doesnt cover the whole thing)

OHH ... turns out NLA service was not starting, now that i started it, it seems to work great,
services guide (http://www.overclockersclub.com/guides/windows_xp_services/3.htm) says its not needed unless using ICS, well it seems my computer doesn't realize that it is indeed connected whenever ti connects to a secure network. im going to test this out on some other networks (like my school network) tomorrow to make sure that it is actually fixed by starting that service, but it seems to be working fine at home

I see you found it. My 2 cents is I always try have Windows handle the wireless. Each vendor will try to add a layer to handle it but Windows often does it better. This may not have anything to do with what is going on here but generally valid.

i always let windows handle it as well... lots of vendors include their own little programs (like the intel one that comes with a lot of dells)... i hate them