To troubleshoot limited or no connectivity issue, try these:
1. Obtain and install the most recent version of the wireless network adapter driver and/or wireless router firmware..
2. Re-configure NIC speed.
3. Install Microsoft wireless update
4. check the wireless security settings or windows security software settings.
These links may help too.
Microsoft update
Troubleshooting limited or no connectivity
"This connection has limited or no connectivity. " ... check this page, Sent packets only on a wireless computer and Limited or no connection ...
http://www.chicagotech.net/troublesh...nnectivity.htm
NIC
Limited connectivity with ...
Solved: Limited connectivity with Vista notebook ... A135-S4427 Satellite notebook that was just released with Vista Home Premium, ...
http://www.chicagotech.net/netforums...opic.php?t=246
Security
Limited or no connectivity because ...
Emptied my temporary folder. Purged my recycle bin and restarted. Upon restart my wireless connection said limited or no connectivity to the internet. ...
http://www.chicagotech.net/netforums...b4cda3f33cccd9
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
"ddamico" <> wrote in message news:2E1D6C1D-0924-4A11-8983-...
Greetings,
Does anyone know the best way to track what is causing a wireless device to
drop from SSID or go to the Limited or no connectivity state? We have a few
different types of devices, Wyse thin client with Cisco a,b,g cards, and
Lenovo laptops that use the Intel pro wireless. We are seeing that they will
have 100% Signal Strength, Excellent Signal Quality and running at 54.0 Mbps
but they disconnect and then get the 169.254.x.x address. We either have to
repair the connection or restart. We have the latest drivers from Lenovo and
all the latest Microsoft patches. I read that we can enable logging within
Windows Xp but the log looks a little confusing. Any ideas how to narrow down
if it's the client or if it's something with the access point and beyond? I’m
responsible for the desktop side and the network group keeps telling us it’s
the client and we need to figure out what to do next. We also have the
settings on the client set for no power management and we have tried setting
the roaming aggressiveness to high.
Wireless Properties:
Network Authentication - WPA
Data encryption - AES
EAP type - Protected EAP (PEAP)
Validate sever certificate
Enable fast connect
Secured password (EAP-MSCHAP v2)