Hi all -
I'm hoping somebody out there has some thoughts on this. I have a dell D410 that belongs to our COO, well due to lots of issues, I rebuilt it from scratch, installed xp sp2, all the dell drivers etc and tried to connect to our internal wireless network. It won't connect, it won't even pull an IP address, just says limited or no connectivity.
So, I brought in another ap, and hooked it up (not to the network initially) the laptop connected just fine pulled and ip and could get to the configuration page of the ap.
Enabled wpa security on the ap (just like our inhouse ap) and still could connect and get to the configuration page.
Put the new AP on the network, can't get out of house on it, dropping 60-80% of the packets - ok so maybe that is our network configuration.
So, I took the laptop to a nice neutral place, a starbucks and tried to connect to their network. It would pull and ip (oddly it pulled a 172.xx.xx.xx ip) and I couldn't not surf. not sure what I did (tried way to much in the 1.5 hours I was there) and ony once did I actually pull the correct ip for their network (about half way thru all the testing) and never could repeat.
I have installed the KB884020 patch, fixed the registry, tried repairing the tcpip stack and now I'm out of ideas.
I am able to connect to a rogue ap that is unsecured near our building and surf the web off it - so I'm just confused about what is going on. I've even deleted all wireless configurations and let it find them again and I can connect to the one rogue ap again (and access the internet) but still not on the internal office one or the second one I brought in.
Free Guide: Managing storage for virtual environments
Complete a brief survey to get a complimentary 70-page whitepaper featuring the best methods and solutions for your virtual environment, as well as hypervisor-specific management advice from TechTarget experts. Don’t miss out on this exclusive content!
No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.
Your password has been sent to:email@example.com
To follow this tag...
Thanks! We'll email you when relevant content is added and updated.
Share this item with your network: